MOTUnation.com

Here’s a problem with bussing that’s intermittent and vexing when it manifests:

I often set up six or more busses in most DP Projects. I use some for side-chaining. If you do as well, you probably know that you can get a feedback loop error message (See attachment.) if you select as a Bus Send the same channel that you have selected as a Side Chain input on an effect on the same Channel Strip.

What I’m seeing occasionally is that error message when I”m 100% certain I do not have a feedback loop.

I have been able to fix this in the past on occasion by deleting the bus or busses that seem to be the problem, and then add new and different busses (like 63-64 instead of 9-10), and re-route my effects. But, on a few occasions, no amount of deleting and adding new buses and selecting them for the side chain eliminates the error.

I’ve tried Loading my Project into a new Project, and that doesn’t solve the problem. That’s been a pretty reliable fix to corrupt or problem projects in the past.

I suppose this is a bug, and not a complaint.

BTW, I grew up referring to audio paths as a “buss,” with two “s” characters. I disapprove of the single “s” spelling, but I am at peace with it.

Jim, where I grew up, a buss was something you asked your girl(boy)friend for at the movies.

One of the things I've wanted from DP, or any DAW is the ability to export a signal path. I've drawn one myself for all my templates so I can see where things might not be quite right. I can't see just how what you've done creates a loop. Do you have a template you can upload?

Haha, yes I learned that usage when I web searched for the proper spelling. That was new to me! When I was a teen, a bus was something I caught to go to school. I didn’t know about busses until I acquired a recording hobby in my thirties and bought a Teac-3 with four busses, spelled “Buss,” IIRC.

I acquired a kissing hobby in high school.

I’ve attached my template. IDK how helpful it will be.

I'll open that up when I'm at the audio system next time and see if I can get it to feed back.

I've seen an erroneous feedback path error as an intermittent, and very rarely. No evidence of an actual feedback path. Has always gone away just as quickly.

It just happened to me again on another project update. However, this time, rather than assign a bus to a compressor side chain first, then assign a channel to be a Send, I did them in reverse order and did not get the loop error message.

So, not a solution, but maybe a workaround to a definite bug.

Yea, I spelled it "buss" for a long time, but then realized I had no idea where I got that idea.

stubbsonic wrote: ↑Thu Jul 11, 2024 5:16 pm Yea, I spelled it "buss" for a long time, but then realized I had no idea where I got that idea.

Probably the same place I got it from:

stubbsonic wrote: ↑Thu Jul 11, 2024 5:16 pm Yea, I spelled it "buss" for a long time, but then realized I had no idea where I got that idea.

I do think, though, that technically "buss" is correct. At least I've seen it used that way with mixing boards. I used to use "buss" all the time but got timid about it because I saw everyone else using "bus." I think "bus" is a vehicle. But I guess now it's just one of those personal preference things.

Along those same lines, I'm trying to train myself to use "display" like Apple does for a video "monitor" because otherwise sometimes it's used as a video monitor and other times an audio monitor and it makes for confusion. So I like to say "My Mac is connected to three displays."

Bus and Buss mean the same thing. Both refer to transport along a predefined route.

bayswater wrote: ↑Thu Jul 11, 2024 7:34 pm Bus and Buss mean the same thing. Both refer to transport along a predefined route.

Right... but you wouldn't write "I need to make sure to get the next Greyhound buss out of town."

(As someone who once took a Greyhound bus overnight from the Bay Area to San Diego... you don't want to do that!)

cuttime wrote: ↑Thu Jul 11, 2024 6:05 pm

stubbsonic wrote: ↑Thu Jul 11, 2024 5:16 pm Yea, I spelled it "buss" for a long time, but then realized I had no idea where I got that idea.

Probably the same place I got it from:

Exactly.

James Steele wrote: ↑Thu Jul 11, 2024 7:52 pm Right... but you wouldn't write "I need to make sure to get the next Greyhound buss out of town."

I'm bussing out of town while you route the signal to the bus. It all works.

bayswater wrote: ↑Thu Jul 11, 2024 9:19 pm

James Steele wrote: ↑Thu Jul 11, 2024 7:52 pm Right... but you wouldn't write "I need to make sure to get the next Greyhound buss out of town."

I'm bussing out of town while you route the signal to the bus. It all works.

Sure... an extra "s" when you make the noun into a verb. But you don't write "Be on the next buss out of town."

James, were you doing anything with I/O settings when you got the message, or did it just randomly appear. I have found that I will sometimes (but rarely) get a false feedback loop message when I change the I/O in the Tracks window. It's as if the new settings haven't landed in their final destination yet, if that makes any sense. It usually quickly goes away, but on the rare occasion that it persists, closing and re-opening the project fixes it. If it doesn't fix it, it's because I've done something stupid and the error is real.

Also remember that your sends can sometimes be the culprit as well.

Your friendly neighborhood Phil