kim_otcj.
andreariderellihi all,
i am a new podium user. please excuse me if this will be probably a faq.
is there a way to avoid the complete vst scanning at every new project, although been still able to use them after the project has been created unchecking the “scan and import mono/stereo VST plugins”?
i suppose a one time scanning should be sufficient, or not?
thank you in advance for your help.
regards,
andrea
thcilnnahojHi Andrea,
if you have a fixed set of plug-ins, and rarely extend or shrink your collection, then this is easy to accomplish:
On the new project creation page (Project menu -> New Project), set everything up as you would normally and check the “Save the created project as a project template” option. You can disable “Create new arrangement” if you prefer to start with an empty project each time.
Let Podium run the scan, then enter a name for your template.
Now, when you want to create a new project, go to the Project menu and choose Project Templates -> New Project -> Your Template!
You’ll only be asked to enter a project name as usual – your list of plug-ins is built from the template, without the need to re-scan.
If you do add or remove plug-ins from your setup on a regular basis, then it’s not as simple, I’m afraid. In this case you might want to voice your opinion in this thread. 😉
andreariderellihi!
you are telling me that it is better to save a project as a new template after i complete a vst scan and then start any new project with this template, aren’t you?
for me it’s ok, but it is a very strange behavior for a daw to be necessary this workaround instead to create a vst cache/db once you need at start and then to refer to it any time.
this is the very first time i see something like this.
anyway, thank you for reply!
i need it because this time i would like to start a new remix using podium (instead of other daws i am used to like adobe audition, nuendo and reaper) and i would like to be a way to learn and support podium.
regards,
andrea
ZynewaveHi Andrea,
Thanks for your feedback. It emphasizes the need to make the project template system more accessible on the create new project page, as discussed in the topic thcilnnahoj linked to.
you are telling me that it is better to save a project as a new template after i complete a vst scan and then start any new project with this template, aren’t you?
That is correct. The reason that the plugin setup is included in the project, and not in a single global database, is that it allows for having multiple plugin setups for your different types of projects. You may want to create custom plugin setups for working with surround sound, mastering, classical composition, etc.
I’m going to make some improvements to the project template system for the coming 2.28 release.
andreariderellihi zi!
since i am a podium absolute beginner user, i would like to understand if it will be possible in the near future to have a global plugin cache/db and only then the possibility to choose the customized plugins setup for each new project.
i mean: to avoid to scan vst directory every time you start a new project, but “having multiple plugin setups for your different types of projects”
thank you in advance,
andrea
Zynewave@andreariderelli wrote:
if it will be possible in the near future to have a global plugin cache/db and only then the possibility to choose the customized plugins setup for each new project.
i mean: to avoid to scan vst directory every time you start a new project, but “having multiple plugin setups for your different types of projects”
Yes, if I understand you correctly. The plugin cache/db you talk about will be stored in a project template file. I’m going to revise the way that you access this project template (i.e. plugin database) on the Create New Project page. If you only work with one plugin setup, then the result should be that you don’t need to scan for plugins every time, unless you have installed new plugins and want to update the plugin database.
ZynewaveThe upcoming Podium 2.28 will feature a new plugin database system, which will make it easier to avoid VST scanning for each new project, as well as making it easier to update the plugin setup in your older projects:
siegfriedI have many VST plugins on my PC. If I load only few plugins (instead of all of them) to my Podium project, is Podium then more stable? Or the advantage of this is “only” more control – I mean not to be lost in hundreds of plugins…
kim_otcjFor me, the template system is one of the best features of Podium. I have several different setups ready to go — for mastering, for tracking, for cleaning up live recordings, for VSTi based tracks, and a few others.
I have a couple of hundred plugins in my VST folder, and it takes a few minutes to scan them all. It would be a real pain in the neck to do that from scratch every time I launched Podium.
siegfriedkim_otcj: I think you must scan them all only once…? and then you can load that setup every time you start new project, in no time… am I correct? So my question is – If I have setup with all plugins (but I actually use in my song only few of them), are they all affecting stability of Podium?
adimatisYes, Yes, No.
😉
kim_otcj@siegfried wrote:
kim_otcj: I think you must scan them all only once…? and then you can load that setup every time you start new project, in no time… am I correct?
That’s right. If you set up your folders properly in the preferences, all your templates will be in the first pull down menu of the new project dialogue. It’s just a matter of choosing which one you want to use.
So my question is – If I have setup with all plugins (but I actually use in my song only few of them), are they all affecting stability of Podium?
In my experience (which might not count for much), scanned plugins don’t effect the stability of the system or do much of anything at all until you add them to a project.
I recently upgraded my computer, and some of my older plugins don’t like Windows 7 much (the Antress Modern plugins are particularly bad for this). So I’ve had a bit of experience with instability issues. If a plugin doesn’t want to work, I just delete it from the track where I applied it and the problem goes away. I’ve never found it necessary to delete something from the list of scanned plugins.
Most of the time, even just muting a plugin is enough to take it out of the picture and get it to stop bothering your processor.
kim_otcjThe other thing I sometimes do, when I’m starting something I haven’t got a template for, is to load up the default New Stereo Project and change it to “Don’t load plugins”.
That way I can simply scan in the plugins one by one, as and when I need them. That keeps things nice and neat.
You can do that on the main project tab, by choosing “Import Plugin” from the Devices menu.