Busses as Destination and Multiple Destinations for Busses
in progress
ultracello
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.
M
MaikR
Is this ‘in progress’ as-in ‘to be released any time soon’…? Just asking because I’m building a FX template and controller mapping, that needs flexible routing. For instance, saturation on Bus A and Delay on Bus B. Now I would like to swap the order in which the audio is routed through these busses, for that I think this destinations feature would be useful.
D
Davy
This is highly needed for serious mixing/mastering chains. But I wonder if this will actually solve the current monitoring issues in a good way. Usually people also want to monitor the master too. It would be WAY less complicated for the users to add a CUE function like most live mixers have. With the ability to crossfade between CUE and master it would be already sufficient. This would save us from setting up (even more) complicated routings.
_
_d4ydream
Would Multi-route audio fall under this feature? Not being able to 'tap/route' audio to the sidechain input of a compressor makes me sad :( In AUM, you can add a multi-route device in the FX chain to 'tap' the audio at the part of the chain and send it to the sidechain inputs of any device with multi-input support. I hope this is included in this feature request.
AJ Kerezy
_d4ydream There is another feature request for better audio signal routing as well; even WITHIN an audio bus. In that feature request I provide an image from the AxeFx III, which I had. It sets up the audio chain and plugins as a grid of something like 6 rows, and 20ish columns. You can route out audio out from one plugin, and send to up to 5 other plugins, and likewise pull signal from up to something like 6 plugins back into 1 plugin. In the attached picture the audio signal flows from L to R (it was easier visually to manage). Having said all of that; I am thinking of your 'side chain' comment as well. I think, for those plugins that support side chain it works the same.
As I see this specific feature request; it's more at the audio bus, or channel level. LP allows the INPUT channels to route to more than one audio bus, or more than one looping bus; but the audio bus channels only get routed to the main out.
Marcus Urruh
I just found out it is possible to monitor at least inputs through color channels, to hear their effects and to already hear while recording how a clip would sound later at playback. But I would need an corresponding action to use this in my current project, as my colors are not bound to specific inputs normally, and monitoring through all eight color channels effects simultaneously does not make sense. Also I would like to monitor busses and when recording other colors through colors.
At the moment in my Rainbow Garden for Elektrons project, I have to copy several effect send settings from selected input channel(s) I'm recording from to the recording destination color on my UI manually,
in order to match sound at playback.
Because of long effect tails and to be able to tweak later I rather not record my send effects in the clips.
Marcus Urruh
After reflection, I think now what could be helpful is to make the color (and also output) destinations for all mixer channels (the rectangles with the lovely little rainbow flags) variable in live situations, dynamic, switchable and even continuously controllable by dedicated action. With an additional (also actionable) monitor switch parameter, for listening through color effects chain, as it is exiting now, but for audio inputs only (and not under live control).
Who's afraid
of that feedback ghost! :-)
Maybe this is a new feature request.
So we could switch input to different colors as destination from UI and controller! And even other colors destination(s).
Hm.....
but busses with sends to other busses would allow the same??
Could mean using many busses though?
Just by making the individual destination color monitor switches universal for all channels, and the live action would just be to control a bunch of send amounts to different preset color destination/monitoring busses. That's similar to the logic I use in my project, but it's tedious to program it for every color.
Possibility for switching outputs for monitoring live from my design would also be welcome. Cue listening feature, but also on busses please!
Please consider this, Michael Tyson
Michael Tyson
Merged in a post:
Bus to Bus Sends
S
Sevin Yerlikaya
Michael Tyson
in progress
s
spirit
This sounds like it would solve my problem of not being able to send audio to izicast, AUM, or Audiobus when using Loopy stand alone. I do live streaming and want desperately to switch from my DAW to Loopy Pro, but without a way to get audio out of Loopy Pro to izicast I’m stuck.
There are other plugins I have that show up as a channel strip in Loopy Pro and require audio sent to them (I.e. samplers) that I cannot get audio into. Please add sending audio to such channel strips and buses. Thanks!
Le Grande Bouf
This nice feature is desperately needed.
ultracello
Adding: Possibility to rename busses
ultracello
Adding: Possibility to rename busses
Jack Arnold
ultracello: yes!
Load More
→