Gain module creating wave errors

Hi!

Not sure if this is a bug or not, but cannot find an argument as to why this would need to be here. Also I can’t recall if this was already brought up in a different thread.

In using the gain module, I have been noticing that it’s been creating an artifact at the selection bounds. Is this audible? Well, that is a the point of discussion that I wanted to bring up, as you can clearly see the that waveform has an alteration to the cycles that do not respond differently to the feathering/fade in parameters of the selection. So, I think it would be content dependent whether this is audible, but I think is all around problematic.

I had a coworker test on another piece of audio, and they actually picked it up in wave lab as an error as well. Testing within RX as well for the exact workflow, and they have a 10-20 ms time window where the selection ramps linearly (IIRC) to the selection bounds, so this error of reshaping the wavefrom is not seen.

I had the gain module onscreen in the capture, but it didn’t render in OBS, but it is set to -7db for reference.

1 Like

While I’m not a DSP expert, I believe it is due to the maths behind the scenes not having access to audio outside of the audio selection.

As far as I’m aware, for linear phase processing to work properly, audio before and after the selection needs to be analysed so it can produce proper transitions, otherwise you get a sharp transition at the selection boundary.

It’s just a guess on my part, but two different AIs seem to agree I’m correct, and that it’s usually called “lookahead / lookbehind” or “boundary extension” processing. Something along those lines.