Clip in master - go to offending events

What is the fastest way to identify a single channel clip event (or all channels) that shows up in the master? After a clip in the master, it would be great to right click on the red indicator and select - go to the clip event.

What is the best way to find the event quickly? The goal is to have a clean export with no clips.

The ideal solution would be to select the offending peak in the waveforms, auto-select it and then process that peak (not the file) down -3dB or what ever is needed.

Thanks for the suggestions or an update with this feature.

Hi,

Most probably, it’s not a single Channel clipping. The mix of the Channels is clipping.

So adding a brick wall limiter on every channel will not fix a summing clip, aka the master. Will a brickwall limiter or a Maximizer plug-in in the master section prevent such clips? I do not see any clips of the single channels.

Silly me thought 0 + 0 = 0. I was apparently wrong.

Thanks for the lesson.
Peace,
Kurt

It would also be cool to add a single channel clip → go to offending cycle in the wavefile. This would be a great improvement to add.

If a channel is overloaded, it is indicated by the overload display for the respective channel. If the summing signal clips, no specific channel can be identified as the originator. It’s like a barrel into which 10 people pour water at the same time. If the barrel overflows, whose last drop caused the barrel to overflow? Nobody knows. My recommendation: Reduce your sum level or use a peak level limiter in the sum.

No channel in Cubase can clip. It can reach a level above 0.0dbFS, but it will not clip. Clipping can only occur when the signal is passed from Cubase to the ASIO driver. That is also the reason why only channels that are output busses have a clipping indicator.

What you are asking for is a function to find the position of the highest volume value of a track .

Please add the feature-request tag to your topic.

it´s not 0+0, its something + something = more than something

What? Signals are not 0.

Since we are all musicians I incorrectly assumed everyone knew that 0 means 0 dB. Again, silly me. So, if all channels are outputting at less than 0 dB the sum of all channels can then exceed 0 dB. What is the 0 dB reference “value” in pro-audio in power, V*I? Is it still 10x Log(some watts)? Where 3 dB is twice or half change in power?
I have been mixing rock bands in Cubase since 1999. What changed in Cubase metering? I have never seen this issue before now, no channels clipped but the sum is clipping. Someone (thanks) suggested setting the master below 0 dB. This is confusing to me.
Keep in mind when medical folks are discussing patients they say his temperature was 100. They never say 100 degrees, because in the context we all understood that degrees is obvious. My bad…

What is the quickest way to avoid summed clipping? Thanks in advance.

Erm… Using the master fader ? :thinking:

3 Likes

Thanks again. I will give it a shot. Why is this new to Cubase? What changed?

Nothing has changed. Channels in a DAW that uses floating point amplitudes (i.e. all DAWs) never clip. Never have. Never will. Adding two signals together will almost always produce something louder than either of the two signals alone. That has always been true in audio and always will be.

It’s not rocket science. 2 coherent signals with 0 dB (voltage) result in a sum level of +6.021 dB, and this is exactly what the meter in Cubase shows. And yes, +6.021 dB will clip when D/A converted, therefore the red warnig area in the sum, but not in the channels.

More: Total level adding of coherent signals


Possible measure to avoid clipping in the summing channel

“dBFS is not defined for analog levels”
Kindly read this section on Wikipedia:

That means, it differs for the converter implementations available. But most professional converters use 22dBu as the maximum output level.
And the very professional converters are switchable.

1 Like