Missing an aux when I bounce to disk

[aaronbagby]

Hello. I have the following issue perplexing me at the moment.

I have a session with all instruments feeding various auxes, which all feed a mix bus (127-128). All auxes are audible during playback, except the aux featuring my acoustic drum samples. It catches all of my SSD5 drum tracks, feeds them out to a master drum bus where it combines with some Linn LM1 samples, which then feeds my mix bus. Routing is sound, and I'm able to correctly solo anything all the way through the chain. But when I bounce to disk (yes, bounce source is set to Out 1-2) the acoustic drums are not there. I can't figure this out, and it's very important I figure it out ASAP. Thanks in advance for any help!

[Emi]

Trash preferences, restart.

This is what I do when something weird happens. It usually works.

[Teej]

If that doesn't work, can you try a Commit or a Bounce of that aux before bouncing and use that as the source instead of the "live" SSD5 as a workaround? At least that should get you to the finish line and/or let you know if the problem is before or after that aux channel.

[musicman691]

Originally Posted by Teej

If that doesn't work, can you try a Commit or a Bounce of that aux before bouncing and use that as the source instead of the "live" SSD5 as a workaround? At least that should get you to the finish line and/or let you know if the problem is before or after that aux channel.

Another thing is is the routing being done by outputs of the aux tracks or via sends? If by sends then just use the regular output of the aux.

[albee1952]

And one more longshot....something you THINK is routed to a physical output just MIGHT actually be feeding a bus with the same name. I know that sounds convoluted, but I had it happen to me where everything sounded fine on playback, but the bounced mix was missing several parts. It turned out that my routing had gained a bus with the same name as my main output I deleted that bus path from the IO setup and reset those track outputs properly and all was good.

[Rich Breen]

Originally Posted by albee1952

And one more longshot....something you THINK is routed to a physical output just MIGHT actually be feeding a bus with the same name..

^^^ This
Almost certainly a busing error - *carefully* examine your I/O setups (physical out and bus pages).

[albee1952]

Originally Posted by Rich Breen

^^^ This
Almost certainly a busing error - *carefully* examine your I/O setups (physical out and bus pages).

In my case, I never created a bus called Main Out L/R(which is the name of my main output path). Somehow, PT created the bus and in checking output routing, I discovered the bus on the list