Oversampling question...

[someone89a]

So this could be my system bugging out, my knowledge being incomplete, or the plugin being buggy...

Was testing out oversampling on MTurboComp (15.00m), by just compressing and saturating a sine wave.

When I make the oversampling higher, there is a distinct *click* as the oversampling changes - thats perfectly normal.

However, the higher I go, the audio from the compressor begin to click and stutter - yet my CPU meter in Ableton Live doesnt go into the red, there arent any overloads that I would notice...

So I recorded the following example, comparing the differences between the oversampling values, all the way up to around 16x. (recorded at 48kHz)

https://drive.google.com/file/d/16RzQQE ... sp=sharing

The higher the oversampling, the more the saturated sine wave turns into glitch music.

I'm very un-knowledgable when it comes to oversampling, rarely having had need to use it, however this doesnt seem like an intended feature...?

I think I'm just using it wrong - I'm not sure.

I am pushing the compressor very very hard, so maybe that has something to do with it? The clicks go away if I turn down the saturation.

I'd appreciate anyone's insight into this!

Screenshot 2021-07-15 at 15.02.42.png

[Held]

I tested it in Bitwig and it sounds fine for me until 128X when the DSP performance meter hits the limit.

The CPU meter doesn't necessarily predict glitches. You need to look at the DSP performance.

[someone89a]

The CPU meter doesn't necessarily predict glitches. You need to look at the DSP performance.

Whats the best way to check that do you know?
Tried the same setup in Reaper and got the exact same results - but Reaper's performance window is just showing a very low CPU hit, I'm not sure how to look for DSP performance specifically?

[someone89a]

Screenshot 2021-07-15 at 17.31.27.png

I just checked it using the Bitwig demo, same issue - looked at the DSP graph and its not a very noticable difference - bit of a spike when turning MTurboComp on, but thats expected.

[Held]

That's strange. It definitely shouldn't sound like it does in your example. Try increasing your buffer size and see if that helps.

Edit: I've tested it again to be sure and I've pushed the input over 0dB and now I get some crackles too at 16x oversampling.

Looks like the oversampling doesn't handle volumes greater than 0dB correctly.

[someone89a]

Edit: I've tested it again to be sure and I've pushed the input over 0dB and now I get some crackles too at 16x oversampling.

Looks like the oversampling doesn't handle volumes greater than 0dB correctly.

Tried again with keeping the input below 0dB and you're right, its only glitching out when pushing the input level up. Pushing the input up but lowering the saturation also reduces the crackles - seems to be some combination of the saturation and the input level not playing nicely.