198,199 users have contributed to 43,103 threads and 258,734 posts.
In the past 24 hours, we have 2 new thread(s), 5 new post(s) and 63 new user(s).
Hi
I'm about to build the ultimate template for Cubase (;-). Now I wonder if it's smart to combine VSL trumpets og BB trumpets in the same VEPro6 instance? The Pro is that it allows me to create a bus for ALL trumpets, the cons is that I will combine a dry library with a wet.
All good ideas are welcome.
I could enlarge the project with the Hollywood Orchestra Trumpets, and SAM, but I think it would take forever right?
It depends on how you work. If you like to keep all you wnat to use during programming loaded, it would be not very smart to combine RAM+CPU resource heavy Kontakt + Play Libraries with VSL even if you do not intend to work with Synchron- libraries. Cubase does save .bak-Files regular automatically while you work. If you have a considerable Part of any Play or Kontakt Orchestra-library loaded beside a full VSL-Orchestra you end up waiting half the time you work the long time it takes to save your Cubaseproject bak-file. And do not think your Hardware would be more powerful and will do that much better than mine, (since it is not;😉)
Perhaps it is less tiresome for your Hardware and you if you just load a few seperate specific patches you think you might need to suplement VSL, but this is nothing I would plan for a general template to start working.
With 64GB you can work with nearly the whole Pre-Synchron-VSL-Superpackage in one smart enough if all comes from SSD's But combination with Kontakt or/and Play Libraries in a "template" is more likely makes things much more tedious than helpful.
Hi
Thanks for your reply. I think I will group my libraries together by manufacture instead. So all VSL together and nothing else.