Feature Requests

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.

Description: The feature request proposes the ability to copy, move, or swap actions between two widgets within Loopy Pro. This would greatly streamline workflow, especially when working with complex setups. Currently, there is no efficient way to transfer actions between widgets without manually recreating them. Problem: When setting up multiple widgets, it can be tedious to replicate or transfer actions, especially in scenarios where similar actions need to be applied across multiple widgets. The lack of a copy, move, or swap function leads to redundant manual work. Proposed Solution: Introduce a feature to easily copy, move, or swap actions between two widgets. This could be implemented with a "Pin" function that allows the user to mark a widget, then switch to another widget and choose to copy, move, or swap the actions. Additionally, the feature should support replacing existing actions when moving actions from one widget to another. Benefits: Saves time when managing complex action setups. Reduces the need for manual copying and configuration of actions. Improves workflow efficiency by allowing users to quickly duplicate or transfer action sets. This summary was automatically generated by ChatGPT-4 on 2025-05-07.

Description: Users want the ability to create custom effect chains in Loopy Pro, consisting of AUv3 and built-in effects, which can be saved and recalled as presets. This feature should include the ability to split signals based on frequency, volume, stereo (LR) or dual-split, and apply distinct effects to each split path, with the option to merge the processed signals back at the end. Problem: Currently, Loopy Pro only allows routing an audio signal directly to the next plugin, without flexible signal splitting or parallel processing. This limitation prevents more advanced audio setups, like multi-band processing or complex effect routing, which are common in multi-FX setups like Axe Fx III. Proposed Solution: Implement a modular grid system to route audio signals dynamically, similar to multi-FX processors. Allow users to split audio based on specific parameters (frequency, volume, stereo channels). Enable combining processed split signals at the end of the chain. Save and recall these custom effect chains as presets. Make it possible to integrate channel strip savings for easier project management. Benefits: Greatly enhanced audio processing flexibility. Efficient setup for advanced sound design and multi-effects. Simplifies workflow by allowing preset recall for complex signal chains. Facilitates creative sound manipulation during live performances. This summary was automatically generated by ChatGPT-4 on 2025-05-07.

Description: Enable saving and recalling entire channel strips (including all plugins and optionally widgets) as presets. This allows fast loading of complex FX/instrument chains across different projects. Problem: Rebuilding plugin chains and settings for each project or channel type (input, color, bus, master) is time-consuming, especially in live setups or when consistent tone is needed across songs. Proposed Solution: – Add a feature to save a full channel (strip) as a reusable preset – Optionally include bound widgets and layout elements – Allow importing/exporting channel strip presets – Add "recall channel preset" and "save channel preset" actions – Allow presets for: – input channels – color channels – bus channels – master channel – Optional: grey out unloaded channels to free up RAM/CPU – Optional: preload (but inactive) channel strips for fast switching – Optional: include full widget configuration (position, behavior, etc.) – Add tags or labels to organize channel strip types (e.g. “Guitar FX”, “Vocal Bus”) Benefits: – Save time during project setup – Allows modular, reusable channel configurations – Supports consistent tone in live and studio workflows – Ideal for musicians switching instruments/effects between songs – Reduces CPU/memory load by offloading unused channels – Encourages structured and repeatable setups This summary was automatically generated by ChatGPT-4 on April 30, 2025.

Description This feature request proposes the implementation of flexible groove quantization options for MIDI recording in Loopy Pro. The goal is to provide users with advanced tools to adjust the timing and feel of MIDI recordings, enhancing musical expression and aligning with various rhythmic styles. Problems Rigid Quantization : Currently, Loopy Pro offers basic quantization settings that may not accommodate the nuanced timing required for different musical genres or personal playing styles. Limited Groove Customization : Users lack the ability to apply swing, shuffle, or custom groove templates to MIDI recordings, restricting creative possibilities. Inconsistent Timing Feel : Without flexible groove quantization, achieving a humanized or genre-specific rhythmic feel requires manual adjustments, which can be time-consuming and imprecise. Proposed Solution Advanced Quantization Options : Introduce a range of quantization settings, including swing percentages, shuffle rhythms, and customizable groove templates. Real-Time Groove Application : Allow users to apply and adjust groove settings in real-time during MIDI recording and playback. Groove Template Library : Provide a library of preset groove templates representing various musical styles (e.g., funk, jazz, hip-hop) and allow users to create and save custom templates. Visual Feedback : Implement visual indicators within the MIDI editor to display the applied groove adjustments, aiding in precise editing and alignment. Benefits Enhanced Musical Expression : Flexible groove quantization enables users to infuse their MIDI recordings with desired rhythmic feels, enhancing the musicality of their productions. Streamlined Workflow : Real-time groove application and visual feedback simplify the process of achieving the intended timing, reducing the need for manual corrections. Creative Versatility : A comprehensive set of groove options allows users to experiment with different rhythmic styles, fostering creativity and innovation in their music. This summary was automatically generated by ChatGPT-4 on 2025-05-08.

Description: Loopy Pro users would like the ability to create multiple timeline regions within the sequencer, allowing for more flexible arrangements and looping possibilities. Problem: Currently, the sequencer only allows for one continuous timeline looping region. This limitation makes it challenging for users who want to set up more dynamic and flexible arrangements, especially during live performances or when experimenting with song structures. Proposed Solution: Implement the ability to define multiple timeline regions that can loop independently or in sequence. These regions should be customizable, with options for setting different loop lengths and behaviors. Additionally, an arrangement widget that functions like a master timeline would allow for quick restructuring during performances. Benefits: Enhanced flexibility for live looping and performance. Ability to experiment with different song structures without stopping playback. Improved workflow for users who want to set up looping regions with minimal interaction during performance. This summary was automatically generated by ChatGPT-4 on 2025-05-07.

Description This feature request proposes enhancing Loopy Pro's audio routing capabilities by allowing buses to be assigned as destinations and enabling buses to send their output to multiple destinations, including other buses. This would facilitate more complex and flexible routing configurations, such as creating monitoring buses with effects like reverb or delay that are applied across multiple channels. Proposed Solution Bus as Destination : Enable buses to be selected as destinations for audio sources, similar to how colors or outputs are currently assigned. Multiple Destinations for Buses : Allow a single bus to route its output to multiple destinations, including other buses, colors, or outputs. Dynamic Routing : Implement actions or controls that allow users to dynamically change bus destinations during live performances or within a project setup. Monitoring Enhancements : Provide options to monitor through buses, enabling users to hear the combined effects applied to multiple channels in real-time. Problem Limited Routing Flexibility : Currently, buses in Loopy Pro can only send their output to the main output, restricting the ability to create complex routing scenarios. Monitoring Challenges : Users cannot monitor the combined effects of multiple channels through a single bus, making it difficult to set up cohesive monitoring environments. Workflow Limitations : The inability to route buses to other destinations limits creative possibilities and complicates setups that require shared effects processing or parallel routing paths. Benefits Enhanced Creative Control : Users can design intricate audio processing chains, such as parallel effects or subgroup processing, improving the overall sound design capabilities. Improved Monitoring : Facilitates the creation of dedicated monitoring buses with specific effects, aiding performers in hearing exactly what they need during live sessions. Streamlined Workflow : Reduces the need for workarounds or external routing solutions, allowing for a more integrated and efficient project setup within Loopy Pro. This summary was automatically generated by ChatGPT-4 on 2025-05-07.

Description: Provide an Action Inspector with optional Graph View to show every action attached to a selected object (widget, clip, track, mixer channel, AUv3, page, project), including triggers, conditions, follow actions, targets, and cross-references . Enable quick navigation, test-fire, and safe refactoring. Problem: In complex sessions it’s hard to know what a control will do or why something fires . Actions may live on multiple widgets, clips, or page events, making troubleshooting slow (duplicates, circular triggers, wrong targets) and risky during shows. Proposed Solution: Inspector (List View): - Consolidated list of all actions bound to the selected object grouped by Trigger (On Press/Release, On Value Change, On Load/Unload, Clip Start/End, Follow Action, MIDI/OSC, etc.). - Shows conditions , quantize/late-press guard , ramp settings , targets , and scope (this page/project). - Inline controls: enable/disable, reorder, edit, jump to target , duplicate , move to… . Graph View (Dependencies): - Node graph of sources → actions → targets , highlighting inbound (who triggers this) and outbound (what this triggers). - Detects loops , shows cycle guards , and flags missing/invalid targets . Cross-References (“Where Used”) - Searchable index of every place this object is referenced (other widgets, scenes, follow actions, variables, OSC/MIDI maps). - One-click navigation and batch disable. Live Monitor & Test: - Event log (timestamped) for the selected object; optional record while performing . - Test-fire sandbox (respecting quantize) with undo; “simulate at next bar/beat.” Filters & Safety: - Filter by trigger type, page, color group, or action category (transport, mixer, OSC/MIDI, AUv3). - Read-only mode to prevent edits during shows; compare changes (diff) before applying. Refactor Tools: - Promote to Preset/Bundle , Extract to Page Action , Replace Target(s) , Convert duplicates → shared macro . - Bulk enable/disable , rename referenced objects , auto-relink by tag/color. Actions & Variables: - Actions: Open Action Inspector , Show Graph , Where Used , Test-Fire , Enable/Disable All on Object , Move Actions to … , Export Action Bundle . - Vars: object.actionCount , object.triggerCount , object.hasLoops , object.references . Benefits: Instant clarity : see everything tied to a control or clip in one place. Faster debugging and safer shows (catch loops, duplicates, bad targets). Confident refactoring with navigation, batch ops, and undo. Reusable setups via export/presets. Examples: Select a Record button: Inspector shows Press/Release actions, quantize, a follow action that arms the next clip, and an OSC cue; Graph reveals a hidden text widget also triggers the same macro. A clip won’t stop cleanly: Where Used shows a scene action re-starting it at End; disable that rule in one tap. Before tour, record a Live Monitor during rehearsal; fix two late-press guards and convert three duplicate ramps into a shared macro. This summary was automatically generated by GPT-5.1 Thinking on 2025-11-24. Original Post: Abilty To See ALL ACTIONS Tied to an Object CURRENT STATE: Troubleshooting objects /controls are nothing less than PAINFUL in LP; especially if/when more than one action interacts with them. SOLUTION: Allow a user to select ANY object /control - a widget, a fader of any kind/type, a plugin of any kind/type; and then .... allow them to get a view of ALL the actions that set or change or interact with them. Any action that changes any parameter - so the user can troubleshoot when something is going wrong.

Description: Add a configurable “New-State Feedback” system that makes UI elements light up / flash / glow when a target state changes (e.g., Armed→Recording, Empty→Has Audio, Mute→Unmute), with per-widget rules for when , how , and how long the feedback appears—optionally synced to bars/beats. Problem: On dense canvases it’s easy to miss that something actually changed—especially when actions fire quantized or off-screen. Users need a fast, unambiguous visual confirmation (brief highlight, pulse, LED) that a control or clip entered the intended state without adding extra widgets or staring at tiny labels. Proposed Solution: Triggers (per widget/clip/mixer item): - On State Enter/Exit/Change (e.g., recording , overdub , playing , muted , hasContent , armed , queued ). - Threshold Crossings (e.g., send > 0%, level > −6 dB). - Event Hooks: Follow Action finished, Scene load, Export complete, MIDI/OSC message received. - Quantize Start (None/Beat/Bar/Loop; late-press guard aware). Feedback Styles: - Flash (one-shot), Pulse (N repeats), Glow (decay), Steady LED (while in state). - Controls: color , intensity/opacity , duration (ms/beats), decay curve (linear/S-curve), outline vs. fill , icon blink . - Epilepsy-safe option (limit frequency/contrast; respect “reduce motion”). Scope & Targeting: - Apply to Buttons, Radios, Dials/Faders, Clips, Mixer Strips , and Text (underline or background blink). - Cross-page relay : optionally mirror a remote state to a local indicator. - Priority system to avoid multiple styles clashing; last-writer-wins or queue. Programming & QoL: - Inspector Feedback tab with presets (e.g., Record Confirm , Clip Armed , FX Toggled ). - Actions/Variables to trigger or query feedback: Show Feedback (style, color, dur) ; vars widget.state , clip.hasContent , feedback.active . - Theme-aware palette with auto-contrast; dark-stage brightness cap. Performance: - GPU-friendly animations; Performance-Safe mode throttles repetition; zero impact on audio thread. - Fully undoable; per-project/page defaults. Benefits: Immediate, unmistakable confirmation that an action landed. Fewer mistakes on stage; eyes off the screen sooner. Cleaner canvases—no extra “OK” lamps or duplicate widgets needed. Consistent, theme-aware signals across pages and projects. Examples: Record button does a white flash (200 ms, Bar-quantized) when recording actually begins; a steady red LED persists while recording. A Clip tile pulses green once when it transitions from Empty → Has Audio after a take. Toggling FX Bypass briefly glows cyan on the insert tile; long glow means “bypassed.” Send A knob emits a short pulse the first time it crosses >0% , confirming the bus is now active. After a Follow Action completes, a small header badge blinks to acknowledge the chain finished. This summary was automatically generated by GPT-5.1 Thinking on 2025-11-24. Original Post New State Feedback - LIGHT UP The State Feedback mechanism is LP is complicated, confusing, time consuming and detrimental to the health of the users. Seriously.... Users need a button to light up, when it is pressed REGARDLESS of anything; regardless if there is or is not a press action in the button REGARDLESS of anything; regardless if something happens or doesn't happen downstream WE JUST NEED TO BE ABLE TO LIGHT UP a button via an action (or MIDI binding action) without a PhD in software, or complications, or spending an HOUR..... trying to get something to work. MAKE IT EASY!!!

Description: Improve control settings and preset management by adding undo/redo, search, filter, and advanced sorting options for MIDI bindings, actions, OSC directions, and plugin presets. Problem: Currently, managing large sets of mappings and actions is tedious and prone to error. Deleting entries in bulk is not possible. Labels can remain even after deletion due to bugs. There's also no way to recover deleted entries or track changes without undo/redo functionality. Proposed Solution: – Add Undo/Redo buttons scoped per section (e.g., MIDI bindings, actions, OSC, plugin presets) – Make list entries deletable via swipe (e.g., after accidental import) – Fix bug where labels don’t disappear after full deletion – Add search with auto-focus – Enable filtering – Support drag & drop sorting by: • Global profiles • Project settings • MIDI bindings • Actions • OSC directions • Plugin presets • Control Settings categories – All list items should support: • Reorder • Move between categories • Copy to category • Delete • Copy/paste • Move to another profile • Move up/down • One-click top/bottom move Benefits: ✅ Massively improved efficiency when editing bindings or presets ✅ Prevents accidental loss of work ✅ Much better clarity and control over large setups ✅ Brings consistency to all control-setting areas ✅ Saves time by avoiding full rebuilds of profiles This summary was automatically generated by ChatGPT-4 on April 30, 2025.