@jasensmith said:
... maybe you truely are having some serious issues but have you considered maybe changing your workflow? 1 minute to open a plugin is still too much?
Thanks for your insight in your workflow and the PC side of life. But you are missing the point. There are two things here:
- A) time to open the plugin
- B) time to load the preset/samples
This is for me not understandable. I understand you have seen a
distinction on your system between security checking and sample loading but I
don't see that from where I'm at. The VE window says " I'm scanning",
but I can't tell what it's scanning. And is it loading stuff into memory while
it says 'scanning?' Seems to me it is 'cause when the plugin window opens with
the presets, the instruments appear and are ready to play in about 1-2
seconds, like a slow screen draw.
I just happen to have a largish template for chamber orchestra, winds and
percussion with 4 instances of Vienna Ensemble loaded each with seven
instruments ( about 30 instruments so far). Those instruments are pretty fully
loaded with lots of patches (oops, I mean presets). Thirty seconds or less for
Cubase 4.5 to open. I can't really tell what's happening next after I select my
template from the menu to load but yes, there is about a 30 second pause while
all four Vienna Ensemble instances scan and load as plug ins. A group of
Kontakt instruments load in a few seconds-total time just now was all of 1.5
minutes including a pause while I looked up which file to load. At the end
Windows task manager says VE.exe has 2.91 gigabytes loaded into memory and
Cubase 4.5 has .575 gigs (575 megs) loaded. Other programs are running as well
with lesser amounts loaded into memory. I can't see that VE is scanning or
loading cause it seems to be doing both.
Suggestions. Are you using VE or VI?
I have found VE manages the memory (I have 12 gigs ) on my system much
better than Cubase 4.5. And when the sequencer is loaded with a bunch of
instances of VI you may be getting a slow down. . So,
1. Group all of your instruments together (strings, woodwinds I and II,
brass I and II and percussion) into various instances of VE and do not
use any VI instances unless you have some over riding reason (although I can't
think of one) I believe this will be a possible solution.
2. I had a terrible firewall program on my computer that almost killed my
computer. I am now using Zone Alert but that might just be the issue as both VE
and VI force a connection with the VSL server to check your license. Try
shutting off the firewall.
3. Also, may I suggest that any time VSL stuff is loaded up these days-at
least since the new 24 bit samples were published 3 years ago, that memory configurations
should have been published to upgrade as well; anything less than 8 gigabytes
of RAM these days is simply not enough. DDR 3 memory is out and on the PC side
Intel's i7 technology really rocks. Again, on my side, when VE says it is
'scanning', I'm almost 100% certain it is also saying 'Loading instruments
into memory'.
4. Try setting Logic to open as an empty shell (force it in preferences )
and then select your project. Sometimes getting the sequencer up and running
before a big memory draw is made seems to work better for me, if the memory
draw is really the issue for you which I am beginning to feel it is. As I say,
from where I sit.