FEEDBACK LOOP ERROR

[msmith92]

I got an MAS Detected Feedback Loop Connection Error. What does that mean? Every time I go to switch an input or output or enable a track the error pops up.

[Don T]

Hello,
Somewhere in your routing you have an output tied to an input. Or so Dp thinks, I've had rather convoluted routings cause the error popup even though the loop did not exist.

[Shooshie]

More specifically, your output is connected to its OWN input, creating a circular routing, thus "feedback loop." This happens most often when using sends, for it's easy to lose track of what is being sent where. The only cure, unfortunately, is to carefully study the affected track and look for every other track which shares an input or an output with that one. Follow the routing. You'll find it. Note: this can also happen after changing entries in the Bundles Window. If that's the case, it may be a little harder to trace. Still, the same methodology applies. I wish MOTU could give us a routing detector that would highlight all tracks an busses connected to the selected track, and show in red where any feedback loops were occurring. Doesn't seem hard to do. I think I'll suggest that as a feature for someday after they get all their bugs worked out. THAT could be a while!

Shooshie

[msmith92]

ok. thanks to both of you. looks like i got some work to sift through!

[Tesionman]

Is there a way to bypass the feedback loop error?