suges.
sugesCould you implement a global setting that either pertains to the whole program, or perhaps just the current project, in which you can click a checkbox and Podium will remember the current state of all softsynths and soft effects used? I know that would lead to bigger .pod files but truth told, I don’t really care, I do pro work and most projects have vocals and instrument recordings done in 96 kHz/24-bit, so I’m used to massive project sizes…a few extra kilobytes in the .pod file to hold the settings means nothing and is worth not having the extra hassle.
Thanks!
Suges
duncanparsonserrr… doesn’t that already happen? especially if you use a library preset? I used to think that I had to reset every plug with each load, until Frits pointed out that when a preset is selected, press the ‘New’ button above the preset list, then ensure that ‘sync’ is highlighted and the plug’s state is saved…
or do you mean something else?
Frits… I have noticed a bug with this actually… whilst the data is saved, the name of the original preset that the ‘sync’ed one is based on gets forgotton. If you use say 3 instances of a plug, each with a library preset based on a different preset; then save all changes, quit and reload – all the library presets for that plug in the project now have the same name.. (I think they all go to either the first library preset name, or the name of the first preset in the plug, not worked out which it is yet..)
DSP
ZynewaveFor the time being, the way to do it is to assign library presets to the tracks. An option to save the states of all plugins does not mix well with the preset objects used by Podium. Insert plugins only exists when monitoring is enabled for an arrangement. Even a global plugin instance may have different states/presets in different arrangements if library presets are used.
Frits… I have noticed a bug with this actually… whilst the data is saved, the name of the original preset that the ‘sync’ed one is based on gets forgotton. If you use say 3 instances of a plug, each with a library preset based on a different preset; then save all changes, quit and reload – all the library presets for that plug in the project now have the same name.. (I think they all go to either the first library preset name, or the name of the first preset in the plug, not worked out which it is yet..)
I tried this with the Vanguard demo and could not get it to fail. Need more info. What plugins are you using? Maybe you could email me a project file with the setup that fails.
sugesHmm. I GUESS I could do it that way. All I’m saying is I want the song to open the exact way it was when I closed it, without me having to make sure every VST synth I may load, I’ve pressed a Sync button and created a preset. I mean, the plugin already HAS its own presets, why do I have to make a second set?
Maybe I just don’t understand the concept properly. What is the value of me saving so-called “library presets” for my VSTi’s?
Yeah Duncan you understood what I meant, but like Frits said it doesn’t already happen unless you explicitly use library presets. Otherwise’s the plugin’s state is lost on reload.
Suges
ZynewaveI could implement a command in the arrangement editor that would check that all tracks with plugins were assigned library presets. It would then create and assign library presets to the tracks that either has no presets assigned, or are just assigned program change presets.
I mean, the plugin already HAS its own presets, why do I have to make a second set?
Compared to how other sequencers handle plugin state storage, Podium does not store extra copies in the project file, quite the contrary. Podium offers you the choice if you want to store the plugin settings (using library presets), or if you just want to select plugin supplied factory presets.
In other hosts, when you add a plugin either to a synth-rack or insert it on a track, a copy of the state of the plugin is implicitly stored in the hosts project file. In Podium I decided to separate the storage of this state data into preset objects. Some advantages to this approach are:
It allows you to create easily accessible libraries of presets within Podium without the need to store them in fxp/fxb files.
When using global plugins in several arrangements, you can assign different library banks to the plugin in each arrangement.
If you have created a preset in a plugin that you want to use on several tracks with other instances of the plugin, you just assign that library preset to the other tracks. In other hosts you would need to copy the settings from one plugin instance to the others, every time you make changes to the preset.
sugesAh. Well when you put it that way, there are some advantages.
You mention that Podium offers you to choice of using library presets or plugin-suppled factory presets (I really have to learn how to use quoting on phpbb). 99% of the time I only use factory presets. Are you saying there’s a quick way for Podium to recall those settings when you come back to the arrangement later? Because that’s what I mean, Podium is not retaining the basic settings like which patch I selected for my Minimoog plugin. I don’t care about the positions of the every little parameter and knob, I just want it to remember the patch I was on.
Sardaukarto quote. just click on on the ‘quote’ button in the top right of someones post, should do it 🙂
Zynewave@suges wrote:
You mention that Podium offers you to choice of using library presets or plugin-suppled factory presets (I really have to learn how to use quoting on phpbb). 99% of the time I only use factory presets. Are you saying there’s a quick way for Podium to recall those settings when you come back to the arrangement later? Because that’s what I mean, Podium is not retaining the basic settings like which patch I selected for my Minimoog plugin. I don’t care about the positions of the every little parameter and knob, I just want it to remember the patch I was on.
If you select/assign the factory program preset on the track with your plugin (using the preset panel), Podium will remember it. If you change the preset from within the plugin editor, Podium will not detect the change.
Some plugins implement their own internal factory preset system, which is not made available to hosts as VST programs. That may be the case with the Minimoog. For those plugins you need to use library presets to grab a copy of the internal preset.
sugesAhh okay I’m with you know. Thanks.
to quote. just click on on the ‘quote’ button in the top right of someones post, should do it
Nice, Sardaukar! Heheh.