You can also see it in the mixer, where plugins can still be opened and are not greyed out.

I have a problem with VEPro 7.2.1516, where disabling channels will only disable VST2 plugins, but VST3 plugins will stay active.

Anyone else encountering the same thing or is it on my end?

[Please delete, I'm an idiot :(]

Originally Posted by: Paul

Hi Stig, 

To quote our developers: "Everything is possible."

I have added your wish to the wishlist.

Best,
Paul

Yes please, wake on midi would be an absolute game changer for big templates!

And while you're at it, please also consider this: it would be fantastic if enabling an instrument would also automatically activate all the tracks that are part of it's signal path.

As an example: in my VEPro template I have every mic routed to it's own output, so the signal path could go something like this: 

1. Kontakt Instance with Cinematic Studio Strings Violins

2. 3 Auxes: Close, Main, Room (these are the 3 mics of the CSS Violins)

3. 3 Busses: Close, Main, Room (this is where all mics from Violins to Basses are bussed together)

4. These 3 busses then get output to Cubase.

Since I have everything premixed with EQ within VEPro, these microphone auxes and busses also have to be deactivated to save on resources.

My dream would be this: you select "CSS Violins 1 - Legato" and start playing. In VEPro, the Kontakt instance gets activated, and with that also the mic auxes and busses (so everything in the complete signalpath), including the EQ's on those auxes and busses.

That way you could have a giant, premixed template, that doesn't take up any resources whatsoever, and all you have to do is start playing patches for things to 'wake up'.

I hope this is somewhat understandable. :)

Originally Posted by: Paul

Hi lucor, 

You have a few options regarding RAM optimization, but with the Synchron Strings, the preload size should only be HALF the usual Preload Size of 16384 Samples => which is 8192 Samples. This way you will get a great and reliable performance (this always also depends on your arrangement, the more you stream, the more performance you need there). Might well be that a lower setting with the Standard Library is possible, and we're also working on more optimized options there. 

With our other "stereo-only" libraries, you can lower the Preload Size to 1536 Samples (so you could load 10 times more samples using only 1/10th of the RAM you'd usually need). This will work until you overdo it with insane TUTTI chords 

There are also options like "Activate on MIDI Activity", which loads all presets without samples and only loads samples when the articulation is triggered once. 

Best, 
Paul

Hey Paul, thanks for the quick answer. So how much RAM would it take, for example, to load all articulations of the 1st Violins with a buffer of 8192? Have you run any tests yet?

And the "Activate on MIDI Activity" is similiar to Kontakt's purge function, I guess? If an SSD can keep up with loading all these samples in real time, that would also be an awesome way of reducing RAM usage.

I'm on the fence of getting my first VSL instrument in Synchron Strings, I'm seriously blown away at the moment!

My only problem is, that I'm pretty intimidated by the scale of this whole library with my measly 32gb of RAM. Somebody told me however, that if run from an SSD you could load the whole Syncron Percussion with only 2.5gb of RAM if the buffer is at 1526. Is something similar possible with the Strings?