No, the folder selection IS saved across the restarts. You can easily check that upon re-opening the project, just by opening ‘Preset Mangement’ with the Key Commands or using the mouse. The correct selected folder is there and then the issue is not present.
This problem happens every time a project is loaded -OR- until you open the Preset Management and then select a VST Preset from the already selected folder in Preset Management ‘Location Three’.
Yes, I already did that, hopefully, the Steinberg support will solve the issue.
To summarize, IF Key Commands for ‘Preset Previous’ OR ‘Preset Next’ are used BEFORE the ‘Preset Open/Close Browser’ - Cubase will open a totally off-side Program/Vstpreset. Despite that correct folder has been selected already.
Select a third-party plugin, NOT the M1 that you’ve chosen (the Korg collection’s devs did a good job), because this one handles the program changes and binds them to vstPresets. Select another one, so that in the inspector you can see this:
Now, you’ll notice that the shortcuts of previous/next, change the programs in the inspector.
You’ll also notice that there is no change to the selected preset of the VST.
This is because, when in the project window, Cubase uses these shortcuts to change program.
Now, if you open this VST and create some vstPreset files, you’ll notice that inside the browser, the previous/next shortcuts will change vstPresets.
This is how Steinberg decided to implement the previous/next preset commands. It is up to the VST to handle the program changes, and unfortunately not all of them do. This is why I initially commented that a program is not a vstPreset. Furthermore, note that you can create your own vstPresets, and then again, these will not appear in the inspector’s view which will continue to show whichever preset the VST attaches to the selected program.
Have a look here, if interested, the VST3 SDK supports program changes, but many VST makers simply do not implement this:
Exactly, but only when the VST implements this, such as M1. Honestly, I never understood why other manufacturers didn’t implement such a useful feature.
My opinion is that it’s something in the middle The only thing I would do differently is to assign separate buttons for programs and vstPresets, since this way, whenever a plugin is not responding to a program change, we could use the second pair of commands without the necessity to open the browser first.
Exactly. This is based on the way the VST interprets the program change.
A workaround might be to create two macros to a) open the browser, then b) choose next/previous preset and then c) close the browser again. Not sure if this could work, taking into account the time it takes for the browser to open (some ms but not 0).
I’ve already done all that, except the ‘C’ one, so there’s no Key Command for closing the Preset Browser, except using the ‘ESC’ key -OR- actually just pressing the ‘Enter’ when previewing the VSTPreset, which will automatically load the VSTPreset and then close the Preset Browser.
Great thread! Let us summarize what it is all about, as it might be of help to other users, too.
If assigning the Cubase Key Commands for 'Preset Previous’ OR ‘Preset Next’ and using them WITHOUT opening the Preset Browser first - then they are browsing & loading the VSTi Programs (…).
If assigning the Cubase Key Commands for 'Preset Previous’ OR ‘Preset Next’ and using them WITH the Preset Browser open - then they are browsing & loading the user saved .VSTPresets.
Do not confuse the Cubase function Key Commands for 'Preset Open/Close Browser’ and ‘Preset Previous’ and ‘Preset Next’ with a
‘Track Preset: Next’ / ‘Track Preset: Previous’ and ‘Track Preset: Open Browser’
The second group one DOESN’T have a dual function. It’s just the first group ( 'Preset Open/Close Browser’ and ‘Preset Previous’ and ‘Preset Next’ ) that will also work/browse for/with VSTi Factory Programs.