Latency in bounced session

[Jcalla]

TITLE CORRECTION: Latency getting printed in bounced track.

So I was trying out the MAAT EQ Orange and Red on one single track and bouncing at the highest resolution. After a bit of testing here's what I've found:

Bouncing using MON L/R as output causes no latency and the track starts at exactly the same time as the bounced track without the EQs.

Bouncing using physical output (in this case my MacBook Pro speakers) prints the same latency in the bounced file (over 3 sec long) exactly like what happens if I try to play the file in the session.

Is this normal? If so, why does it happen and what's so special about MON L/R that makes such an incredibly CPU-intensive plugin (the red) to behave normally while bouncing?

Sorry if this is a noob question.

[Darryl Ramm]

Just noting you said "CPU intensive", CPU intensive is irrelevant here the latency is inherent in the algorithms used by the plugins, not related to that they happen to use a lot of CPU.

I'm not sure what is going on, don't follow exactly what you are doing, it's easier if it was in front of me. But any latency here is well outside what Pro Tools can correct for with plugin latency correction.

And MAAT EQ Orange and Red are normally going to get thrown on a master bus or master fader and not a single track, and so not result in any compensation.

[Jcalla]

Originally Posted by Darryl Ramm

Just noting you said "CPU intensive", CPU intensive is irrelevant here the latency is inherent in the algorithms used by the plugins, not related to that they happen to use a lot of CPU.

I'm not sure what is going on, don't follow exactly what you are doing, it's easier if it was in front of me. But any latency here is well outside what Pro Tools can correct for with plugin latency correction.

And MAAT EQ Orange and Red are normally going to get thrown on a master bus or master fader and not a single track, and so not result in any compensation.

I get that you're trying to help, but you're completely missing the point.

Imagine the single track was the master bus instead, boom, your last point is solved. I should have mentioned, the entire test project was one single track, exactly done to mimic a master bus. I removed all other tracks and plugins to make the test as unadulterated as possible.

All I wanted to know is: why is Pro Tools printing the latency to the bounced track when I'm using the "Physical Output" option as the output in the bounce menu, but there's no latency and the bounced track sounds normal if I choose the MON L/R as output instead. That's my question.

There's not much to imagine, it's a one track project with 2 choices of outputs in the bounce menu which all Pro Tools users have and see each time they choose to bounce a track. One prints the latency (called Physical Output), the other doesn't (MON L/R). My question is "Why?"

[Rich Breen]

LLM engaged?

[Jcalla]

Originally Posted by Rich Breen

LLM engaged?

No it's off. I tried turning it on and redoing the test. Got the same results in both cases. Also it didn't lower the latency while monitoring at all, the music started at exactly the same time as without it, not sure why as well...

[albee1952]

Are you bouncing as wave or as mp3?
Are there any plugins on the master that have latency?

[Jcalla]

Originally Posted by albee1952

Are you bouncing as wave or as mp3?
Are there any plugins on the master that have latency?

AIFF, and both thEQorange and thEQred have A LOT of latency. 1 sec for orange and 2 seconds for red so in total 3 seconds of latency. The track itself is the master bus. There is no actual master bus, it's just a one audio track test project.

My question is, why is the latency being printed onto the track when I choose "Physical Output" and is NOT printed (thankfully) when I choose "Output: MON L/R" as output during bouncing?

Oddly enough, I'm having the same issue in Logic Pro, but I can't seem to fix it there like I did in Pro Tools by using MON L/R (I mean the option isn't there, not that I tried MON L/R and it didn't work in Logic).