Hi @brad,
I’d love to see the following features implemented for the routing diagram:
tabbed view of songs/racks in addition to the existing split screen view with as many tabs allowed as there are (recursive) racks in the song;
resizable objects in the diagram - this would allow to see fully the long object names to easily recognize between similarly named objects, such as different reverb or spatializer plugin objects when I am testing a song with different FX setups all on the same diagram. May be, also automatically resize an object to fit the name (add this feature to auto-arrange function?);
visual differentiation of linked racks, embedded racks, and plugins - may be, a small icon in the object’s upper right corner;
allow to assign default colors to plugin objects based on plugin tag, i.e. when I add a new tag to the plugin library I can also choose a default color for all plugins with this tag. If the tag is assigned to a plugin that already has the default color assigned, then prompt to change the color. Also, show assigned default colors in the plugin selector and allow to assign default color to any plugin from there;
visual differentiation between bypassed and suspended objects - you use hatching for both, just with different intensity - it is hard to differentiate under non-ideal conditions. May be, use different hatching directions, or use cross-hatching for disabled plugins? Not sure this is needed though as objects have easily readable indicator icons anyway,
add the bypass toggle to rack objects on the diagram to allow pass-through with a single mouse click (similar to what we have for plugin objects). This would be a top priority for me personally!
Thanks for the feedback, I’ll keep all this in mind for next time I’m working on routing diagrams.
Regarding this:
The main issue with this is how to define the mapping from input ports to output ports for a bypassed rack? For plugins this is defined by the wet/dry mix on the channel mappings and the ability to map an output directly to an input, but it’s not super intuitive.
If the rack has single midi in route, then the same midi out to all midi ports defined in out routes. if there are no midi out routes - drop the midi. If there is more than one midi in route - either mix the midi and send it to all midi out routes, or, if mixing midi streams into one will take too much effort - disable the toggle, at least for now.
If the rack has one audio in route, then send it to all audio out routes. If there are no audio out routes - do not pass audio through.
In case the pass through is impossible i.e. if there are, say, 2 audio in routes - disable the toggle.
May be, enable the toggle only if there is not more than one midi in and not more than one audio in route.
And in the case of mismatch between in and out routes, say, for a rack with single midi in and single audio out the pass through will pass nothing (or disable the toggle - this would probably be a more intuitive and safe approach).
The main reason for my request - ability to very quickly enable/disable various audio FX functionality for testing. Say, I have a sequence of predefined linked racks applying EQ, limiter, delay, reverb, spatializer, etc., and want to compare output with various combinations of these FX enabled.
The routing diagram tends to be my most used page. Using physical wiring as an example, I would love to see a staple feature. I could staple the wires going in and out of the pluigins to make them tidy. Right now I have 8 plugins on the screen and with the wiring diagrams going all over, it can be difficult to double click the plug in to edit the properties. I would love to staple 4 of the outputs going up, then staple them to the right upper corner of the screen. Then staple the other 4 outputs to the bottom, then staple them to the right lower corner of the screen.
Lately I have been trying to use the states feature. Maybe I am doing something wrong, but it seems like if I try to setup states when in the routing diagram, they don’t work right. I drag the midi sources to the inputs of plugs and it doesn’t seem to save correctly. If I setup the states using the table view, it works well. If I setup states in the table view, then switch to the routing view, the routing view looks the same as it was when I was trying to setup states in the routing view. Not sure if I am doing something wrong there or if there is an odd bug.