Bouncing stems produced clicks/pops in Main

[oortone]

I made a bounce like this (see figure) and the Main stem file got clicks/pops. These were not coinciding with high peaks near fullscale but way below. All other stems in the project are subgroups routed to Main. No pops in these.

If I bounced only Main, no pops/clicks.
Repeated several times with same result.

Has anyone seen anything similar?

[tope d]

Originally Posted by oortone

I made a bounce like this (see figure) and the Main stem file got clicks/pops. These were not coinciding with high peaks near fullscale but way below. All other stems in the project are subgroups routed to Main. No pops in these.

If I bounced only Main, no pops/clicks.
Repeated several times with same result.

Has anyone seen anything similar?

Have you tried importing this sessions data to a new session to see if the same issue occurs?

[tope d]

Originally Posted by oortone

I made a bounce like this (see figure) and the Main stem file got clicks/pops. These were not coinciding with high peaks near fullscale but way below. All other stems in the project are subgroups routed to Main. No pops in these.

If I bounced only Main, no pops/clicks.
Repeated several times with same result.

Has anyone seen anything similar?

Have you tried importing this sessions data to a new session to see if the same issue occurs?

[its2loud]

If MAIN is your physical hardware outputs, don’t bounce this way. Use an internal bus as your source to bounce the full mix.

[oortone]

Originally Posted by its2loud

If MAIN is your physical hardware outputs, don’t bounce this way. Use an internal bus as your source to bounce the full mix.

Yes, I suspected that could be the issue. Do you know why that is?

What does it actually mean to bounce the "physical output" vs. the "main bus" (that goes to the physical output). I mean, the actual physical output is of course not really acessible for ProTools from within ProTools, it would have to be routed manually back into some input.