FabFilter User Forum

I managed to break proL

Apologies for the melodramatic post, but I DID get an output from proL that exceeded 0 with a lookahead of 0.1ms imgur.com/nUU7dsZ

I'm not too worried about it, just curious to know how/why it happened so I can better understand the plug

Tim

Have you verified that it's clipped in other stereo editors? Could it be an waveform draw glitch? The only other reason would be another plugin after Pro-L to cause the spike. Is it spiking during rendering only? Or during realtime playback? Does it peak past 0dB with any audio or just certain plugins?

Sam

There's nothing going on after proL, it's not a draw error, yes it happens in playback too, checked in a separate editor, last question makes no sense.

Interesting side note is that the meter in proL doesn't display the overshoot... not sure why

Tim

You should probably use 4x oversampling, and turn on ISP metering:
www.fabfilter.com/help/pro-l/using/oversampling

Cheers,

Frederik (FabFilter)

Totally forgot about oversampling, thanks, is there any reason that audio would peak through this way though? Something to do with the algorithm etc.?

Tim

Sam this isn't an inter sample peak though, it's about 3 samples that get through, so it still doesn't answer my question

Tim

That's because contiguous intersamples are peaking, resulting in a contiguous peaked waveform.

Sam

Good point, never thought of it like that

Tim

Reply to this topic: