Skip to main content

Saving and recalling devices with presets

Posted

Sorry if this has already been answered (I did do a quick search).

 

I was wondering how to save a private plugin as a device with embedded preset (in my case a Kontakt multi instance).

This what I am trying: Within the Private plugin menu, I use the Port options 'save preset' menu command. This saves the private plugin + device description as a shared rack device with embedded [p] plugin description.

 

This is all great, but unless I keep the new shared rack device fully loaded into one of the memory ports, I lose the embedded plugin when I restart Synfire. All I want to do is save the device with the embedded plugin, so I can recall it later as and when needed for a project. But I don't want to automatically load the full preset into a port whenever I start Synfire for any project, as this will eat up my RAM and take time to load.

 

Is it possible to save device/preset combos without having it load into a port?

 

Hope this makes sense. Grateful for your reply.


Sat, 2012-08-25 - 15:19 Permalink

Now that you bring this up, I should note that this is still a little buggy and the next update 1.6 will include an improvement for plug-in presets that exactly handles this case ;-)

Presets will go to their own directory on disk, no longer being saved with the rack. That is, no matter which rack you load, your presets will be available for recall in an arrangement. There will also be an option to delete presets.

Note that you can only save 1 preset per device. Or in other words, the device is a description of the plug-in's contents (sounds, channels, etc). 

Sat, 2012-09-01 - 13:54 Permalink

Just trying out the new feature in 1.6.

I've got identical VST plugin setups on my desktop and laptop. The folder structure is exactly the same on both machines. In my case; G:\MUSICPROJECTS\VstPlugins\32bit\ maps to the same plugins on both machines.

 

However, the presets saved on the laptop don't bring up the plugin and contents when opened on the desktop. Bit surprised about this? Would be good to understand how this works. I'm thinking Synfire saves the machine name with the presets?

Sat, 2012-09-01 - 18:31 Permalink

Thanks, but I do. Identical contents for the Synfire folders on both computers. The device descriptions show up in the list (with their [Preset] suffix), and the plugins show up in the VST plugins list. But loading the device description with embedded preset into the shared rack does not load up the corresponding plugin.

Sat, 2012-09-01 - 18:46 Permalink

uhm.
i could be wrong but,
i think now we are here

(https://users.cognitone.com/content/vst-path)

i know report was not so good for explain the problem
just because of my English...

there is something missing-or-wrong about vst plugin path
SFP needs exact same plugin directories for the open old projects properly..
IMO this is a little bit dangerous for the future of SFP projects
...
but i hope now it will make sense with Ruchir's problem.

Sat, 2012-09-01 - 23:17 Permalink

Good point, but I'm only using 32 bit. The 64 bit engine isnt running when I use either machine.

Sun, 2012-09-02 - 10:53 Permalink

The drive letter, directory and filename of the plug-in need to be exactly identical. It could even be case sensitive. Check if your directories are named identical and rename them if necessary.

Fri, 2012-09-07 - 21:35 Permalink

Thanks again. Got round to testing this today brieflly. Partial success.
Culprit was the Vst plugins folder, named VSTPlugins on one pc, and VstPlugins on the other. Two device presets are now loading their VSTis, but one still has trouble, but I am sure it is something similar. Will report back.