Save Project Modules for Reuse – Widgets, Actions, Bindings and Layouts
under review
Nick O
Description:
Allow users to save and reuse canvas elements as modular blocks – including their UI widgets, actions, bindings and layouts – to streamline plugin setups or effect chains.
Problem:
When adding a new AUv3 plugin or building a project from scratch, users often need to rebuild the same set of widgets, actions and bindings manually. This is time-consuming, error-prone, and breaks workflow consistency.
Proposed Solution:
– Save canvas areas or full pages as reusable "project modules"
– Include all widget settings, bindings, colors, layout and actions
– Add saved modules to new or existing projects (e.g. on a new page or layer)
– Ideal for prebuilt plugin controller layouts or effect chains
– Optional auto-scaling for canvas size or channel width
Benefits:
– Saves time by reusing complex setups
– Ensures consistent UI and behavior across projects
– Great for building custom plugin templates
– Helps live performers and advanced users maintain modular workflows
This summary was automatically generated by ChatGPT-4 on April 30, 2025.
Z
Zachary Judd
Great Idea- I came to the roadmap to suggest this exact thing. Being able to have a page in your LP template for acoustic guitar, for example, that could be saved separately with all the widgets, mappings, radio buttons for effect presets, etc… and then when a particular project needs acoustic guitar just be able to load in the whole page. Mega bonus points to the devs if the modules could be saved IN CONJUNCTION with the matching channel strip containing the effects chain.
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
marked this post as
under review