01-31-2016, 11:43 PM
(01-30-2016, 08:11 AM)Ben@Harrison Wrote: @smallbutfine: unlike normal "DAW" bus routing, Mixbus's routing is automatable. So you can (for example) turn a send to a delay on&off with automation.
For that reason, we have to assume that every track "can" send to a bus (whether it is right now or not ). So connecting a mixbus back to a track is interpreted as a potential feedback loop. Keep in mind that we aren't worried about "audible" feeedback, but rather the problem that a loop breaks the "graph" which is used to calculate time-alignment. If you make a loop, there's no correct answer for "how long should I delay this track to feed the buses and have it time-aligned?" That's why the audio stops, and the Feedback indicator lights up.
There is a special-case workaround, though. We -do- allow you to route the Master bus back to a track, for bounces. Maybe you can use that feature to solve your needs.
Best,
-Ben
Wow. thanks for the detailed information, Ben, very appreciated.
I understand the issue much better now i know the reasons that lead to this design decision.
Yes, now that i know i can find eventually another simple solution for recording live from the bus, like a file writing recording plugin after the bus fader or something similar, maybe drop that completely and get by with extensive use of the automation features and really just do bounces from Master bus only, which indeed is a very useful feature. I didn't test this because i thought it would be the same for all busses - dang!
Thanks for the great explanation!