FR: Linear sub-rack routing (per rack)

Official support for: mutools.com
Post Reply New Topic
RELATED
PRODUCTS

Post

When this option would be switched on, whenever you added a new sub-rack it would rewire it to the end of the chain. So the wiring would look like this:

Main rack's rack slots -> Sub rack 1 -> Sub rack 2 -> Audio Output
*Adds a rack*
Main rack's rack slots -> Sub rack 1 -> Sub rack 2 -> Sub rack 3 -> Audio Output
*Rearranges Sub rack 3 with Sub rack 2*
Main rack's rack slots -> Sub rack 1 -> Sub rack 3 -> Sub rack 2 -> Audio Output

The wiring is analogous to the order of the sub-racks.

Now that we can make rack devices it would allow us a great bitwig-like workflow. You could make a bunch of mini-devices, insert a synth in the main rack and stack a bunch of processing FX in the sub racks while being exposed to all controls without having to open and manage several floating windows.

Post

On top of that, there could be a '+' button on the right side of the mixer strip to easily add new racks without the need to go into modular area.

Post

+1 for this.

Post

Thx for your suggestion.
I've bookmarked this topic, will reread it later.
Currently focused on extending MuLab's plugin system to support multiple plugins in a single DLL.
Will take a bit of time.

Post

That sounds intriguing. Forgive my ignorance but what is supporting multiple plugins in a single dll?

Post

There are plugins that have different versions inside a single DLL file.
Currently MuLab only supports 1 plugin per DLL and so users are missing certain plugins.
I'm probably not explaining it well atm, maybe someone else can.

Post

Yes! Thank you so much Jo!
U-he uhbik VST 3 plugin is the perfect example of multiple plugins in a single file. It no longer supports VST 2 so you cannot access more than one plugin in MuLab, that is what Jo is working on.

Not sure if you are aware, but uhbik consists of ten FX plugins. Which used to be separate DLL files as VST 2. But they moved on and VST 3 supports only one plugin containing all ten FX. In Reaper it shows up as ten separate plugins, but MuLab only sees one, due to it being only a single VST 3 file. It's simply a container for all plugins in one single file.
- PolyHostInterface - VST2/3 Plugin chainer

- For curious minds... -

Post

Thanks to the tag team of proper explanation, now I know. How does clap handle this?

Post

Also CLAP supports multiple plugins per .clap file.

Post

bump

Post

humanboeing wrote: Sun Aug 17, 2025 8:38 am When this option would be switched on, whenever you added a new sub-rack it would rewire it to the end of the chain. So the wiring would look like this:

Main rack's rack slots -> Sub rack 1 -> Sub rack 2 -> Audio Output
*Adds a rack*
Main rack's rack slots -> Sub rack 1 -> Sub rack 2 -> Sub rack 3 -> Audio Output
*Rearranges Sub rack 3 with Sub rack 2*
Main rack's rack slots -> Sub rack 1 -> Sub rack 3 -> Sub rack 2 -> Audio Output

The wiring is analogous to the order of the sub-racks.

Now that we can make rack devices it would allow us a great bitwig-like workflow. You could make a bunch of mini-devices, insert a synth in the main rack and stack a bunch of processing FX in the sub racks while being exposed to all controls without having to open and manage several floating windows.
Just brainstorming:
Imagine we have a rack with a synth and some effects in the slots below, some pre-fader, some post-fader. Now lets add a sub-rack in the way you describe it, then these questions:
  • Should that sub-rack be connected to the last pre-fader slot, or the last post-fader slot?
  • What if at a later point in the project you would insert a new slot after the one the sub-rack is connected to, then would you expect the sub-rack routing to be automatically updated too? If the answer is yes (which i assume) it means quite some extra code as the rack could also have been edited modularly, in any way, and so it can be less straightforward as it seems.
Just brainstorming further, without any concrete promises: If your goal is about embedding GUI controls and avoiding floating windows then maybe an alternative way would be an option to embed the MUX front panels of certain slots (with a (rack) MUX in it) into the rack editor, alike sub-racks can be embedded. Edit: Although this will depend on the respective front panel size... That's the advantage of floating windows, the editor can be much more independent and customized.

Again i'm just reacting to your 'bump', and because some time ago i said to get back on it.
Can't make any short term promises atm.

Post Reply

Return to “MuTools”