Feature Requests

Busses as Destination and Multiple Destinations for Busses
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.
30
·
in progress
Undo/Redo, Delete, Search, Filter and Reorder for MIDI Bindings, Actions, OSC and Plugin Presets
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.
26
·
in progress
"Internally phase-locked" play groups for better verse/chorus style looping
A way to ensure that... 1) song sections will always start from the beginning even if they are different lengths, and also 2) all the loops within each song section will always stay synced with each other THE PROBLEM: PHASE-LOCK VS FREE TRADEOFF While phase-lock is great for keeping loops synced, it doesn't work for songs that have multiple sections of differing lengths because when switching sections, the new section won’t necessarily start from its beginning. For example, if the verse is 4 bars and the chorus has an 8 bar loop, switching to the chorus after one verse means that the chorus will start playing from halfway through. While turning phase-lock off (aka "free looping") solves this problem and ensures that loops always start playing from their beginning, the user can no longer start loops at any time within that section and ensure that they stay synced. This is musically limiting and introduces risk of accidentally playing loops out of sync from each other. It’s especially problematic for sections with long loops. For example, if the verse is a 12 bar non-repeating chord progression, any of the 12 bar loops that aren’t started at the beginning of the verse can’t be added until the entire 12 bar verse comes back around to the beginning or else the loops will play out of sync. PROPOSED SOLUTION: INTERNALLY PHASE-LOCKED PLAY GROUPS Play groups should have the option of being "internally phase-locked", which would mean... 1) Whenever the play group is inactive (meaning none of its clips is currently playing or recording)... -All of the clips' playheads wait at the beginning and don't move -This is "non-phase-locked" aka "free" behavior 2) Whenever the play group becomes active (meaning any of its clips starts playing or recording)... -All the playheads of this play group start moving from the beginning (including for clips that aren't currently playing) and they all continue moving as long as any clip in that play group is still playing -This is essentially "phase-locked" behavior except for one important difference: rather than the playheads being synchronized from when the transport became active, they are instead synchronized from when the play group became active BENEFITS: NO MORE PHASE-LOCK VS FREE TRADEOFF Users no longer have to choose between the following benefits- they can have them all! -Song sections can be any length -Song sections will always start from the beginning -Loops within a song section can be started and stopped at any time, not just at the cycle boundary -Loops within a song section will always stay synced to each other While "Internal phase-lock" is probably most useful for mutually exclusive playgroups that "play and stop independently" (as in the verse/chorus use case described above), it could also be useful for “one at a time” play groups. For example, a “one at a time” play group might be made up of variations of a musical part (e.g. bass line variations) to be switched between but not played at the same time. Internally phase-locking this group would ensure smooth, synced switching even mid-loop. Note: “internal phase-lock” is not applicable to "all at once" play groups because by definition, they always start playing together so they can’t get out of sync
0
Rename Busses and Add Optional Descriptive Notes per Bus
Description: Allow users to rename audio busses and optionally add visible notes or hints describing their function or purpose. Problem: Currently, busses in Loopy Pro are automatically named with letters (A, B, C...) upon creation, and users are unable to rename them. This makes it difficult to organize and recall bus functions, especially in complex projects with many busses. The default visual representation is also hard to distinguish from color groups, making the UI harder to parse quickly. Proposed Solution: – Allow users to rename busses at any time – Display the name prominently (e.g. at the top of the bus or next to the letter) – Optional: restore default letter-based name (e.g., "A") if custom label is deleted – Add support for a “hint” or “notes” field for each bus (shown e.g. on hover or toggle) – Consider visual improvements to further differentiate busses from color groups – Optional: provide a UI dialog showing an overview of a bus’s routing and settings, including name, balance, etc. Benefits: – Greatly improves clarity in complex routing setups – Reduces need for external “cheat sheets” – Helps identify and manage up to 24+ busses more efficiently – Enhances UI and UX, especially for live performance or sound design – Makes Loopy Pro more scalable and user-friendly for professional workflows This summary was automatically generated by ChatGPT-4 on April 30, 2025.
13
·
planned
Channel Strip Presets – Save and Recall Full Channel Plugin Configurations
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.
12
·
planned
Load More