Greets once again,
I've been exploring this routing strategy: https://www.youtube.com/watch?v=pA-aLyHEqRg
While I'm not entirely sold on it yet (over using Carla as a middle-man), I'd be curious to know if anything can be done to make working with these inputs a bit more user-friendly.
It would be nice if we could name these ourselves (so long as they're unique).
The whole (Audo)/(Aux) thing is quite unfriendly when it comes to fitting into the mixer panel. There must be some way to optimize this? Considering there are only 2 things that can be added (input vs. send), it almost seems like a simple directional icon could be used to convey the type? In other words, a "<" would be an input and a ">" would be a send. Combined with the first suggestion and assuming I were to name the newly created input after my cat, maybe I'd see something like "< panda". As cool and tidy as that might be, I can see how that would muck with the Connections window though.
Is there any chance to coordinate between the mixer and the Connections panel? For example, clicking an input in the bus strip might highlight the input in the Connections panel? That level of interaction/coordination would save on the mental bandwidth needed to ensure connections are mapped accurately. Then again, maybe not..... I haven't given this a ton of thought.
Any possibility to combine the routing in the same step taken to create the input to begin with? Maybe kill 2 birds with 1 stone kinda thing?
All the best
re. input enhancements
hi, assuming you're taking about Insert Returns as inputs and Sends as outputs:
hth.
Add new comment