I miss the option of being able to take a kind of “snapshot” of a plugin. I don’t want VST Live to save the entire plug-in for me, but only the currently set host values of the plug-in. I would find it practical to be able to save these (separately definable) in the layer as well as in the automatio…

Combine… the question is too simple, there are further thoughts… What if using shared instances? What if using global instances? Maybe there are methods that can help you find the best methods for your needs

Hm, as far as I can see, these presets do not only save the host information or state - the whole plugin gets saved including its ‘states’. Means no RAM can be saved at all here?! Could you tell me where on the hard drive the presets are being saved? For some reason I find them again in VST Live w…

[image] UdoBehm: the whole plugin gets saved What is that supposed to mean? Please, one more time: a plugin is instanciated, that is, we load the dll and ask it to open. What that means is up to the plugin. We then ask for its state (a block of memory) which is entirely opaque, we have no i…

I’m talking of Komplete Kontrol that has Kontakt instruments inside, that use so much RAM if not purged (but then they might not work as reliable anymore for live performance)… As far as I understand comparable software like Cantabile Performer, it is possible to only save the plugin parameters (se…

[image] UdoBehm: Could you tell me where on the hard drive the presets are being saved? For some reason I find them again in VST Live when I open a new project, but I don’t find them on the hard drive. Could you please answer me this question?

[image] UdoBehm: [image] UdoBehm: Could you tell me where on the hard drive the presets are being saved? For some reason I find them again in VST Live when I open a new project, but I don’t find them on the hard drive. Could you please answer me this question? Local : C:\Users\UserName…

Thanks. The last path isn’t working… May I know why these presets aren’t being saved in the users folder? Is the globals path for presets that are used for the global’s part only? Or why do you distinguish them? Also I don’t understand why I cannot rename or delete them in VST Live, nor see them…

[image] UdoBehm: VST Live loads up only the song with its parts that is currently opened if preload is deactivated Not true. VST Live always keeps everything once activated, preload just enforces that all is preloaded in the first place. It is important that Songs switch rapidly. We do have …

Already upgraded to the maximum of 16 GBs… Means it doesn’t load the whole parts inside a song once I open any of its parts?

[image] UdoBehm: Means it doesn’t load the whole parts inside a song once I open any of its parts? No. All Parts are inactive until selected (or preloaded via p"File/Preload (Parts)"). And it keeps its assets thereafter until removed.

Snapshots of the host values of a plug-in

VST Live

Spork March 3, 2025, 1:21pm 15

Local : C:\Users\UserName\Documents\VST3 Presets
Global : C:\Users\UserName\AppData\Roaming\VST3 Presets

See you
Michael.

Adding layers, sounds from the Media Bay to a MIDI track