Multi-Output Mixer Profiles and Bus-Specific Mixer Views
under review
AJ Kerezy
Part 1 (ChatGPT version) – see Part 2 and 3 in comments
Description:
Introduce a flexible, multi-output mixer system that lets users define multiple named hardware outputs at the project level (e.g. "Main", "Headphones", "Stage Monitors") and switch the mixer view between them. Each output would have its own independent mix using the same channels, and there would also be mixer views focused on individual audio buses, showing only the channels that feed those buses. Additionally, provide an optional routing matrix view (similar to AUM) for a clear overview of all audio and MIDI routings.
Problem:
Loopy currently exposes a single mixer view that effectively represents one output mix, even though many users are working with interfaces that have multiple physical outputs. While it is technically possible to create different mixes for different outputs using prefader sends and additional widgets, in practice this is:
- Tedious and error-prone, relying on tiny send dials and complex routing that can feel like a "Rube Goldberg" setup.
- Difficult to read and adjust on a small touchscreen (especially on iPhone), where send controls are small and can be hard to manipulate precisely.
- Lacking a global overview: users cannot quickly see how their channels are routed to each output or bus in one place.
- Hard to maintain in larger projects, because small incremental changes to sends and routing are easy to lose track of without a dedicated overview or per-output mixer.
As a result, common live use cases—such as having different balances for FOH, headphones, and stage monitors, or carefully controlling levels into buses like "DRUMS" or "FX"—are possible but much more complex than they need to be.
Proposed Solution:
- Project-level output configuration
- In the project settings, allow users to:
- Specify how many audio outputs they want to use.
- Map each output to one or more hardware interface channels.
- Assign each output a mandatory name (e.g. "Main", "Cans", "Stage L/R").
- This output profile becomes the basis for all mixer and routing views in the project.
- Switchable mixer views per output
- For each defined output, Loopy automatically provides a corresponding mixer view:
- The same set of channels (loops, buses, inputs, etc.) is shown in each view.
- Fader positions, mutes, and related mixer parameters are stored per output.
- The last channel strip on the right could display the name of the current output mix (e.g. "Main", "Headphones").
- Users can switch mixers via:
- Actions (e.g. buttons on the canvas, MIDI bindings).
- UI controls in the mixer itself (e.g. a dropdown or tabs).
- When switching between outputs, the user sees:
- For example, a blue group fader at -14 dB in the "Main" mix.
- The same fader at -3 dB in the "Headphones" mix.
- Fader positions change to reflect the selected output profile.
- Bus-focused mixer views
- Provide an additional mixer mode where the user selects a specific audio bus and sees only:
- Channels (inputs, loops, other buses) that are routed to that bus.
- Example: For a "DRUMS" bus, the mixer would show only:
- 2 MIDI audio sources,
- 3 input audio sources,
- 1 other audiobus that feed into "DRUMS".
- This makes adjusting bus send levels dramatically easier than tweaking small send dials scattered across many channels.
ultracello
Part 3 (ChatGPT version)
- Design collaboration
- Engage closely with the users who proposed the feature during design and testing, to ensure the mixer and matrix workflows match real-world multi-output use cases and avoid unnecessary complexity.
Benefits:
- Greatly simplified multi-output setups:Users can easily maintain different mixes for FOH, headphones, in-ears, or stage monitors without building elaborate send-based workarounds.
- Touch-friendly control:Fader-based control per output and per bus replaces the current reliance on tiny send dials, which are difficult on small screens.
- Clear routing overview:The matrix view provides a single place to understand and verify routing, reducing mistakes and debugging time in complex sessions.
- Scales with interface size:Works for simple 2-out interfaces as well as for large multi-output rigs, making Loopy more DAW-like in terms of routing flexibility.
- Less widget clutter:Users can rely on mixer views and the matrix instead of creating additional custom widgets just to make send adjustments manageable.
Examples:
- A user with a 4-output interface:
- Defines "Main", "Headphones", and "Stage" in project settings and maps them to the appropriate hardware channels.
- Switches the mixer via actions to quickly adjust the balance for each destination, with clearly separated fader states per output.
- A drummer-focused bus:
- Creates a "DRUMS" bus receiving multiple MIDI and audio sources.
- Uses a bus-specific mixer view to fine-tune the drum balance and overall bus level, without digging through numerous channels and tiny send controls.
- Complex live rig:
- Uses the routing matrix to verify at a glance which channels feed FOH, which feed in-ears, and how each bus is wired.
- Adjusts mixes on the fly from a single iPad without needing a “PhD in Loopy routing” for every change.
This summary was automatically generated by GPT-5.1 Thinking on 2025-11-19
.ultracello
Part 2 (ChatGPT version)
- Routing matrix view (Audio & MIDI)
- Add an optional matrix-style routing page, similar to AUM:
- Rows: all audio channels (inputs, loops, buses, etc.).
- Columns: all defined output channels and/or buses.
- Cells: on/off or level indicators showing which channel is routed where.
- Potential variants:
- A matrix per project output (showing all channels routed to that output).
- A matrix per bus (showing all sends into that bus).
- Separate matrix views for audio and MIDI routing.
- This view serves as a “sanity check” for complex projects.
- Scope limitations
- Plugin instances and settings remain global, not per-output:
- If a reverb on a bus has a 40% wet/dry mix, that setting does not change when switching mixers.
- The feature focuses on routing and mixer balances, not per-output plugin variations.
ultracello
marked this post as
under review
ultracello
Original Post, Part 3
RATIONALE: By jumping through careful, tedious and Rube Goldberg-like UI design, a user can adjust the mix between outputs in the current software, and the mix to audiobuses. But it bout' like to take a PhD. This MIXER switching approach, and the Matrix approach explained below - is so easy my 8 year old nephew can do it.
BY - redesigning and revamping a "SWITCHABLE" mixer between the audio outputs supported by the audio interface, and (a must here) set up by the user for the project.... a simple action lets users ADJUST FADERS without trying to tweak tiny little dials on the screen; and without creating (yet even more) widgets to control the sends.
ALSO.... it would be bodacious if, like AUM, there was a screen that showed the Matrix. No, not Neo or Morpheus - a matrix showing ALL the audio channels on the left, and all the outputs (set up by the user at the beginning of the project) on the top - and which are routed to which. A single routing view. Maybe even an audio matrix and a MIDI matrix would be so wonderful. This should also have viewing or switching options; like a Matrix for each of the audio outputs set up in the project profile, and a Matrix view for each audiobus that has sends going to it. This is a simplistic sanity check..... here's all my audio routings.
The software IS AMAZING for sure....but one "challenge" is that you need a lot of functionality in a very, very, very, small screen space. The "SENDS" dials are somewhat typical on sound boards but sort of challenging to work with on the iPad UI (I can not even imagine it on the iPhone)..... ESPECIALLY if you rename audio bus channels. A "switchable" MIXER design can help here.
PLEASE...... don't go off and "run with it" on your own, work with the folks who have suggested the feature to help make it the best it can be.
ultracello
Original Post, Part 2
ADDITIONALLY: In addition to the mixer view per output channel; allow users to have a mixer view per audio bus channel - showing ONLY the channels routed to that audiobus. So if I have created an auidobus channel for (labeled) "DRUMS", and I have 2 MIDI audiosource and 3 input auido source and 1 other audiobus channel routed to this "DRUMS" audiobus - then when I switch (via actions ) to this MIXER VIEW - I will see only those channels routed to this audiobus. This will make adjusting audio signals sent to audiobuses - 4,320% EASIER than it is now..... where if I using the prefader routing to send audio to an audiobus, I have to adjust little tiny sender dials, that you need a microscope to see. SO - there are 2 major flavors of the mixer; one flavor is be able to switch the mixer to the output channels defined in the project setup; and the other is to be able to switch or see in the mixer a selected audiobus and all of its inputs.
OUT OF SCOPE: Plugin settings per output channel. The plugins in any channel (of any type) are there and the settings in the plugins do not change between mixers. So if I have a reverb plugin on audiobus A, and the wet/dry mix on the reverb is 40%, then this is the wet/dry mix regardless of the output channel.
ultracello
Original Post, Part 1
Allow users at the project level to set up the number of audio outputs they need, to align with their audio interface. Many, but not all, may have 2 outputs, one for the main and one output for the headphones or stage monitors. Some users with bigger audio interfaces and setup will have more. The user MUST give each output a name; and identify which audio interface channels the output aligns to. FYI - this is standard in most DAWs.
FOR EACH predefined audio output, as described above; the current audio mixer display is replicated and can be selected. So I can switch, via an action, and see the same set of faders, but at at the end the last audio channel changes. Of course as I switch between the mixers (one for each defined output), I would visually see and control the faders for that mix. E.g. - if for "main" output the blue color group fader was about -14db, and if for the "headphone" output the same blue color group fader was about say -3db - then I would see the fader set at those positions when I switched between the mixers. The last audio channel on the right - will display the name of the output channel the user defined up front in the project.