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

@Malcolm Jacobson wrote:

Hi Frits,

@Zynewave wrote:

Scanning of each plugin produces the various device mapping, device definition, preset and parameter objects. To be able to skip rescanning plugins in case of a crash, then it’s necessary to save the project template file after each scanned plugin.

Why does the plugin database need to be part of the POD file, and therefore part of the template?

Reaper scans for new plugins each time you start it up (by default, but it can be configured to only scan on command) and writes the list of plugins to an ini file in an Application Data folder. You can then create as many Project files (equivalent to Podium projects) as you want without having to rescan the plugin database.

Is there some architectural reason the database can’t be separated from the POD file?

The main reason that the plugin definitions (or database) are included in the project file, is to allow customization of the plugin setups for different projects. You may have different plugin setups that you have organized for mastering, mixing, surround, classical, rock, and so on. Another use could be to have one setup that is organized into folders for plugin vendors, and another into folders for plugin type. You save these different setups in project templates. With the use of the “Load device setup” from the project template menu you can even switch between the plugin setups while working on the project.

I agree that the vast majority of users won’t bother with organizing different plugin setups, and will only ever need one setup. That’s why I’m currently making some changes for 2.28 that will support a global plugin database. The plugin setup is still included in the project, but the management of the plugin setup is now much easier. I hope to have a preview ready later this week.