VSL team-
So loading my samples didn't realy take too much CPU before. I just watched the ram climb and that's all there was to it. With VI Pro 2.0 it was the same deal at first. Now that I've stretched a good deal of my library each time I load samples it kills my CPU. I disabled every last time stretched cell and the load was normal again. I have since enabled only the most common stretched samples I'll use and the CPU is stressed on load again.
1- I put the time stretch cache folder on a separate hard drive and changed it to a 400GB max to give it breathing room. This is a slower drive but I plan to get a 10,000RPM drive for this single folder. I want to have many time stretched samples loaded ultimately. Is VI Pro 2.0 not really built for this?
2- I've stretched everything out already in creating these presets. So during the sample load time it isn't stretching anything anymore. During the stretching my CPU wasn't even stressed that much, just more than a simple sample load. But now that I've saved everything and I'm loading things in VE and Cubase, my CPU is at 100% until the library is loaded.
This can't be right...can it? I have a hard time thinking that MIR runs smoother than loading samples. I don't mind cause my library is loaded and I can work. But this seems to be an undesired result. I should also note that VE is now crashing frequently after these stretched samples have loaded already. Keep in mind, I'm not loading gordes of them anymore. I did at first, but now I'm only loading the a small number of stretched samples per instrument, and a larger number for just my fanfare trumpets and epic horns. It's hardly loading much more into ram than my old template now and VE is crashing all the time, and my CPU goes insane on loading. Is something wrong or should I not load more than 2 or 3 stretched samples at a time?
-Sean