Offline Bounce Quieter than Print to internal track.

[EarHole]

I did a mix last week and printed to an internal track like I always do.
Then at the last minute the client had a quick change and everyone was waiting
on my so I did the Bounce to disk / offline option. Well, the mix was noticeable quieter. In the end I had to just re-print and export it anyways.

Has anyone else had issues?

[mesaone]

Any inserts on the Master? Master fader pushed up?

I've never encountered this, except if I forget to disable an insert when playing back a print or bounce through the same bus or master that it was printed from.

[Rich Breen]

Gotta be something else going on in the bounce. Just did a null test again on this last week on some hour-long program; BTD and Record To Track null to zero (except dither) as always...

[EarHole]

I use an Aux as a Master so I can buss it to the print track.
It was at unity and had a subtle Limiter on it.
When did the Offline Bounce, I used that Aux as my output so It should have
included the limiter.

[Carl Kolchak]

Originally Posted by EarHole

I use an Aux as a Master so I can buss it to the print track.
It was at unity and had a subtle Limiter on it.
When did the Offline Bounce, I used that Aux as my output so It should have
included the limiter.

No, you need to use the next buss downstream of the Aux, to include any effects used on that Aux track.

When you choose a buss as your bounce source, you're selecting the input of that buss, not the output.


Here's a more detailed explanation, and a test file I made.

[EarHole]

Originally Posted by Carl Kolchak

No, you need to use the next buss downstream of the Aux, to include any effects used on that Aux track.

When you choose a buss as your bounce source, you're selecting the input of that buss, not the output.


Here's a more detailed explanation, and a test file I made.

Well that would explain what happened. Why would they set it up to export the input?

[Carl Kolchak]

Originally Posted by EarHole

Well that would explain what happened. Why would they set it up to export the input?

Perhaps my use of the word "input" is a little misleading - what's being bounced is whatever is in that particular buss, but not anything you've placed across it's output :

The Water is in the pipe.

The Fluoride is in the water.

The Water Filter is across the output of the pipe.

The Tap is across the output of the water filter.


With the Bounce to Disk pop-up, when you select the bounce source, if you select the "pipe" (mix buss for example), your bounce would include the "water" and of course the "fluoride" (the mix as it appears at the Aux input), but it has not yet reached the "water filter".

I think this catches some people out because, depending on how you go about routing the output of one track, to the input of another, it can conveniently auto-name the buss, with that of the destination track.

What you need to do is set up some "Print" busses, that can either be where your global mix buss routes out through, or only used for bouncing via sends, or by temporarily changing the output of a track to that "Print" buss.

Of course, when you print to another track in real-time, you have to route through another buss, to connect to the input of your destination track, which eliminates this pitfall.

Hope that helps.

[Brandonx1]

Put a little simpler, if you bounce thr input of the aux, no plug ins on the aux are included. If you bounce the output of the aux, the plug ins on thst aux are included.