Jairus
Description:
Introduce a “live-linked” master template system where projects created from a template can optionally remain linked to that template. Structural changes made to the template (layout, routing, actions, etc.) are automatically propagated to all linked projects, while each project keeps its own recordings and project-specific content.
Problem:
Currently, once a project is created from a template, it becomes a completely independent copy. This creates several issues for performers who maintain multiple projects:
  • Tedious maintenance:
    Any improvement to the setup (UI tweaks, routing optimizations, better controller mappings, new widgets, updated macros) must be manually replicated across every existing project.
  • Inconsistency over time:
    Older projects gradually diverge from newer ones; some have the “old” layout or routing, others the “new” one, making it harder to remember what behaves how.
  • Risk of breakage:
    When a user wants to improve their master setup, they may hesitate because it would require touching many projects—or risk breaking older recordings with incompatible routing or missing controls.
  • Inefficient iteration:
    Rigs evolve constantly. Without a master template link, users can’t just refine one place and trust that all performance projects inherit the improvements.
For heavy Loopy users running multiple shows/projects, this lack of “central configuration” makes their workflow more fragile and time-consuming than necessary.
Proposed Solution:
Implement a true master template system with live linkage and controlled overrides:
  • Master templates as structural source:
- A template stores all “structural” aspects:
- Layout and UI widgets
- Routing and buses
- Mixer settings
- MIDI bindings and controller mappings
- AUv3 configuration (which plugins are loaded and their parameters)
- Global actions, macros, track setups, etc.
- Projects created from this template only store project-specific data:
- Recorded loops and audio
- Clips, timeline content, other per-session material
  • Live linkage:
- When a template is updated (e.g. add a new widget, adjust routing, change MIDI mappings), all linked projects automatically inherit those structural changes.
- Projects remain playable and current without manual re-editing.
  • Control per project:
- A clear toggle such as:
- “Link to template / Unlink from template”
- Per-project override system, so a project can:
- Override specific elements (e.g. one widget layout or a particular binding) while still inheriting the rest from the template.
- A manual “Refresh from template” command:
- Pull the latest changes from the template on demand.
- Useful if automatic updating is disabled or for safety.
  • Conflict handling and transparency:
- Optional diff/merge view when applying template updates:
- Shows what will change in the project (new widgets, changed mappings, removed elements, etc.).
- Allows the user to accept or reject certain changes if overrides exist.
- Clear indication in the UI that a project is linked to a given template and how up-to-date it is.