[thcilnnahoj]

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.

No other suggestions at this time, but some questions:

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

– 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?

– 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.”?

– 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?