The often and occasionally muting aux channel

[rainsong]

This is driving me nuts.

Finishing up a mix. I have two kick drum tracks (real and trigger) bussed to an aux send. That Aux channel has one plugin (an EQ). On occasion, audio simply won't pass through the channel. Usually turning bypass on and off in the EQ plugin fixes the issue, but the further in to the session I've gotten the more frequent this happens.

At first I assumed it was a problem with the plugin. I was using FabFilter ProQ-2...so I removed it and put a plain old Avid EQ on instead. Same exact issue.

I made a new session copy with new audio files. Also deleted the kick aux bus and aux channel and re-created them. Same exact problem still occurs.

Anyone else ever experienced this? I can't figure it out for the life of me.

(Also, the only way I can get it to bounce without muting the kick track is to do an offline bounce.)

[Drew Mazurek]

Never seen this, sorry. And I do what you're describing everyday.

[musicman691]

Any automation on the tracks?

[clive.gardner]

Originally Posted by rainsong

This is driving me nuts.

Finishing up a mix. I have two kick drum tracks (real and trigger) bussed to an aux send. That Aux channel has one plugin (an EQ). On occasion, audio simply won't pass through the channel. Usually turning bypass on and off in the EQ plugin fixes the issue, but the further in to the session I've gotten the more frequent this happens.

Yes. Exactly this. In one session I'm working on at the moment it's happening frequently. About every 4th or 5th time I hit play. I have to deactivate/activate the bus to bring it back. I think someone else alluded to a very similar issue in another thread recently also.

Like you I've tried re-creating the busses and saving a copy of the session and working with that. The problem still exists. Trashing prefs and doing a completely clean reinstall has not helped either. It's actually got worse over time as it started at 1 but I now have 3 different busses in the session displaying this behaviour.

I'm working on Windows rather than Mac, and currently using different plugs to you. However, one thing I will say is I was also using Pro-Q (trial) at one point on the session, but its since been removed and uninstalled. Whatever it is, its driving me absolutely mad. Only seemed to kick in for me around the upgrade to 11.3. Session was originally created under 11.2 and worked fine at that point.

If you happen to find a solution, my sanity will forever be in your debt!

Clive

[Intransit]

Oh ya. This bug. Love it! So frustrating. Avid can't explain it either.

Others with the same issue http://duc.avid.com/showthread.php?t=358171

[Rosco1969]

I used to get this quite a lot with 10. something or other... not had it since 11... and now 12... I remember it was very frustrating and no one could explain it.

[clive.gardner]

In that case now all we need is someone with an active PT12 support plan and too much time on their hands...

[bashville]

Somehow I'm imagining it reacting to a phantom controller that's in actuality not hooked up. I'm wondering, in case you're not doing any other automation on the aux, what if you set the automation to "off" for that track and see if it still happens.

[take77]

Does going to the I/O dialogue and clicking Default, deleting any previously self-created busses (unused) and then re-creating the bus (if necessary after defaulting) help?