@herb said:

I just want to add, that the DM scan should not give any messages if nothing was changed with the installed database. The rescan button simply disappears when the scan is done.

So I would say, if you get any messages without having maipulated the database indicates that there is something going wrong on this (these) systems.

best
Herb

For 19 out of 20 times I cannot load samples (usually happens after loading and unloading a few) - I have NOT gotten any message in DM - the samples just simply do not load.

The only fix is either run DM (again usually no messages) and rescan (usually fixes the problem) OR in some cases - reboot the machine.

I have four PC slaves and have loaded Vi on three of them. This behavior has occurred on all three slaves. I am going to keep the fourth one just for GS and PE until there is a solution. [:'(]


Rob

ROb

I reinstalled the entire VI library and I am no longer having the issue. Time consuming yes, but things are running much better now.

Herb - why would a reinstall be the issue (I think I have tried this and still no change???)

Kcorbin - did you unistall everything (software and library)? Of course leave the key untouched (did you remove the key when reinstalling?)

Can you give me some details?


Rob

Rob, we can't reproduce this here, so I can't say much about it at the moment

Best would be you give your exact system and hardware configurations our programming team, this would help a lot
best is you send Golem (Chris Teuscher) a private message to get in contact

best
Herb

I did not uninstall anything. I just reinstalled the library in the same directory "over" the existing one. Didnt touch vienna instrument or the key at all.

My issue was also solved by reinstalling library on an internal hard drive. For some reason several files had gotten corrupted during the install process. I only realized the files were corrupted when I tried to copy them to another disk drive and got a data error- cyclic redundancy check.

Not sure if this is what is causing your issues but...

Best,
Jay

kcorbin - good to hear that your 'reinstall' has done it for you. Unfortunately mine is still having problems (but I didn't do a re-install of the library OVER the existing - would that be it??).

Herb - this thread's first entry has my PC specs. I don't want to write the whole thread again but if Christian would be so kind as to review this thread, he'll have a good idea of what is happening and what I have done to date.


Update on what is given above.


The problem seems to come up when I am loading and unloading, say a solo violin and THEN go to another instrument folder, say the viola.

Load that universal patch and 'most' of the sample play OK but one or two sets do not (like the F legato - the p legato plays - but the F legatos are not accessed). This scenario just happened.

For this that just happened - I Closed VST, run DM 'rescan', reload and the viola is perfect. Seems like a bug to me and not PC based (DM and 'rescan' fixes the problem).

What do you think Christian - you can send me a PM if you think that would be better. I just wanted to help others who may have this issue - but your call.

Rob

@JBacal said:

My issue was also solved by reinstalling library on an internal hard drive. For some reason several files had gotten corrupted during the install process. I only realized the files were corrupted when I tried to copy them to another disk drive and got a data error- cyclic redundancy check.

Not sure if this is what is causing your issues but...

Best,
Jay

Thanks Jay. Should I just leave the library on my 'audio drive' and re-install OVER them?

I just reproduced the problem again - for me - it is when I go from one instrument to another in the same VI. I can open up all of one instrument, vln - all is OK but when I go to VA or VC 'some' of those files are not acessed.

Let me know on the reinstall.

Just to be sure, when I re-install the dat files (done automatically one DVD at a time). I set up a 'new folder' (Vienna) on the audio drive. All the dat files go there

(that is what I have now and all our shown in the DM)


Thanks Jay.


Rob

Rob-- does the problem happen every single time you do the same sequence of events. If so, can you post the exact steps that create the problem (load this matrix then this then this). I can then test on my PC to see if the behavior is universal.

Your problem doesn't sound like a corrupt file issue. But if you really want to reinstall I would try it to a different internal hard drive just in case there is an issue with drive itself.

Best,
Jay

Hi Jay,

I don't think it is the install as well. When this happens all I have to do is close the VS and run the 'rescan' and it fixes it. For my orch template I will not be doing a lot of changing so it will not come up that often ( I am changing matrixes now just to listen to them). Plus I'll have seperate VIs opened for different patches.

Kind of a hassle to have to deal with this but there is a work around (restart and rescan).


Rob

Christian - Herb,


OK - had the same behavior on another of my PC slaves. [:'(]


Here's what fixed this on THAT machine (a present GS PC). [:)] Went to the memory config tool in GS and it was on 'use the system original configuration'.

I changed that to 'Preset #1 Windows XP default'. Loaded the VI to 1.5 - no problems (couldn't get past 1 MB before).


Here's the challenge - how do i get the ability to make the same 'tweak' as the GS's ''Preset #1 Windows XP default' on the PC that never had GS????

I bet this would fix the problem. Any ideas.

(does anyone know what is going on with GS preset #1. I wish I could just run that config tool on the 'non-GS PC')


Rob

Mattias Henningson created a memory utility for exactly this purpose. Check his website.

--Jay

...which is http://www.musikbanken.se/gigastudio/index.htm">http://www.musikbanken.se/gigastudio/index.htm The utility is available on the Memory Optimizer page.

/Mattias

Very much appreciated Mattias. I'll give this a try.


As I say above the Gigasampler - config tool preset #1 fixed the other machine and now allows that machine to fully load VSL's VI. I have done this on yet another slave I have and same behavior. If the config tool in GS is set to any other than 'preset #1' - cannot successfully FULLY load the VI. Very strange.


Rob

Maybe not that strange after all. We're trying to decrease the size of the pools in order to free memory for GS's private use. This operation may very well cause limitations for applications that needs to allocate large amounts of paged or non-paged memory.

/Mattias

Thanks so much Mattias - you have been so helpful. Today I will try to run your 'get settings' (on your utility) on the machine that is now working right with VI. I'll duplicate that setting on the PC that is still not loading up VI properly.

Rob

Mattias - very nice tool to determine settings. Here's what I found on the PC that was not loading VI properly


8/800000
8/800000


On the machine that was working properly it was set to

0/0
0/0


I then set the 'bad' PC to


0/0
0/0

WORKS PERFECT - loading to capacity!!!! [:D]


(Again - thanks Mattias for the assist)


Rob

Rob, glad to hear that you're up and running now! If anyone else reads this and wants to know... What Rob ended up with is exactly how XP is configured from the beginning.

/Mattias

I'm sure that I said this weeeeeeeeeeks ago [:(]

DG

True. And you were right! [:D]

/Mattias