2022.7 Track Clip Indicators Not Working

[JingleDjango]

I can't get my clip indicators to hit red, regardless of the signal I pass through.

Example:
https://youtu.be/vBMFG3Jgel8

In Pro Tools Preferences, Peak Hold is set to 3sec. Clip Indication is set to Infinite.

[albee1952]

Hmmm, some thoughts:
1-is your session created in 32 bit float format?
2-is the distortion from Pro Tools or from the input signal(are you over-driving an external preamp)?
3-you should not be pushing your input level any higher than just into the yellow
4-you may have discovered a bug(but you can see the very top meter block holding a yellow indicator for 3 seconds). Looks like it functions, but with the incorrect color. Did a quick test here and found the same. The Clip indicator shows as yellow so I'm off to report a bug

[JingleDjango]

Originally Posted by albee1952

Hmmm, some thoughts:
1-is your session created in 32 bit float format?
2-is the distortion from Pro Tools or from the input signal(are you over-driving an external preamp)?
3-you should not be pushing your input level any higher than just into the yellow
4-you may have discovered a bug(but you can see the very top meter block holding a yellow indicator for 3 seconds). Looks like it functions, but with the incorrect color. Did a quick test here and found the same. The Clip indicator shows as yellow so I'm off to report a bug

Hey, thanks for taking the time to respond.

1. Session format is 24bit, 48kHz.

2. Distortion is from gaining that clip up to an extreme level to demonstrate the issue. I'm recording with the macOS app Screenflow and sending the audio directly from that track to the video recorder via Source Nexus, bypassing my VO Bus which contains dynamics inserts that would mask the problem. I've gained the audio track down for the purpose of the video, to avoid blowing the viewers' ears out.

3. Well, yeah. . . I still expect the meters to alert me of issues. I'm levelling takes and pushing into my VO chain but because I have dynamics processing including a peak limiter at the end, I want to know if I accidentally set the gain too high, to the point of clipping. I will be taking processed and unprocessed versions of these clips as deliverables.

4. Good to know. I'll be curious to hear from other users. I expect a red line that stays put until I clear it by clicking or using the keyboard command.

[originalscottyg]

I'm not positive, but I think the this is the new expected behavior, since the internal summing mixer is floating point. Since you can turn that aux with the Bus 1 input down and "un-clip" the signal, PT doesn't really consider it clipped. I think that physical outputs still show red clipping, but internal paths that are floating point don't.

[K Roche]

I think that (showing yellow not red ) is the standard now isn't it ?
As noted I get red in the meters on my Carbon but not in PT

[JingleDjango]

So does solid yellow at the top of the meter indicate >=0dB?

[mbourque]

Maybe it has to do with the type of meter you're using for the track. Have you tried to change it?

[JingleDjango]

I normally use K-12 or K-14 for music but switched to sample peak for this game audio project. I tried Pro Tools Classic as well to see if I could trigger the Clip light but I think the above comments are correct with respect to the clip indicator only applying to physical inputs and outputs.

[BScout]

There is no more red on internal busses (I think this is dumb but all meters are working that way.)

[JingleDjango]

Thanks everyone for the confirmation.