Reply To: FR: plugin cache/database – speed up project creation

@thcilnnahoj wrote:

Hmm, what about people who work with multiple templates… maybe the “import database” button could become a sort of dropdown menu to select a template.
Sure, you can use the ‘old’ way to create a project from a template, but it’d be nice to have them all available like this.

If you have saved your own project templates, then there will be a dropdown menu button. I think most users will never use the project template feature, so I’m trying to figure out a transparent way to handle a global plugin database, without worrying the user about templates.

– How does it work for plug-ins that have since been removed – does the “update database” function clean them out automatically?

Yes, I think they should be cleaned out.

– Does the update function go by filename only, or will it create additional mappings for plug-ins that are already present, but the user may have created custom mappings for?

No, it will skip any plugin whose dll is already referenced in a mapping in the database. Otherwise it would need to rescan all plugins anyway, and then there won’t be much time saved with the update option.

– If the option for importing surround mappings is removed, you’ll have to delete them from the very first plug-in database yourself, no? I hope they won’t reappear, should you use the “update database” function.
Though I guess there’s no need for concern since this change in 2.27: “Using any of the import plugin commands will only create surround mappings for the plugin if there already are other surround mappings in the project.”?

I’m considering moving the stereo and surround options up on the page as general options, and not just plugin related. The options also decide if surround mappings should be created for audio ins/outs and busses.

– Is this going to change anything concerning audio and MIDI device setups, or will the database somehow only story plug-in (and external instrument/effect) mappings?

No, the project template menu will work as always. It’s only the auto-generated “plugin database” template which will be used to extract VST plugin definitions only.