Save project as "module" preset for adding to other projects.. so it contains: widget page and all associated tracks/plugins/bindings
under review
Nick O
So basically it would be very handy to save all widgets and the plugins they control as a module/preset that can be loaded and added into an existing project. If say you have a synth and some midi and audio FX all controlled by widgets, and you want to load that whole "instrument" into another project so you can mix and match "modules", that would save a lot of time compared to remaking it from scratch in the current project. I realize this can be done by loading loopy as an auv3 into loopy, but then you can't use auv3 as part of the preset/module being inserted so that's a huge downside.
This can be done by having an option to save a project as a "module" that can be inserted/loaded into a different project (by adding the saved widget pages to what's already there and by adding the associates tracks and plugins to all that's already loaded in the project)
Or alternatively it can be a self contained “module” that can be inserted into a track, kind of like loopy can be inserted into itself as an auv3, except this way it would also be able to contain 3rd party auv3’s. In effect this would allow creating and sharing modules of instrument and effect chains / racks with their own widget performance pages.
Rolf Schwitter
Saving canvas elements with kind of a binding to inputs and effects. So when you for example ad a new auv3 effect in a new project, you can choose to ad stored canvas elements (maybe on a new page). So you could choose from different canvas builds to control a plugin, all set up. Then you could maybe scale it up for a whole channel.
ultracello
under review