Conceptual flaw? Oversampling setting of modules is not sample rate dependent

[Hanz Meyzer]

As far as I understand it, the oversampling setting within the modules are not sample rate dependent, e.g. in the merger module... Is that correct?

If this was the case, this clearly would be the wrong approach. The plugin then will sound different dependent on samplerate. Instead it should be related to a lowest sample rate, so 2x always is 96khz, etc. Also the effective target sample rate should be shown at least as a tooltip or so, so it would be way more clear what actually is happening.

So how is it currently done?

[MeldaProduction]

It is always multiplying the current sampling rate getting into the module. That's imho the correct approach and cannot be changed anyways if you don't like it.

[Hanz Meyzer]

This wasn't meant to be a discussion about my personal pereferences, more about what is the expected and most logical approach.

I would then disagree that the current approach is correct and argue that you would expect the same sound from a synth, no matter the global sample rate is set to. So if you only change sample rate, but not the oversampling, the sound is expected to sound the same. But if you change the oversample setting, it is very likely expected that the sound can change.

In the end it's your synth, not mine. Yet I am trying to give you another point of view from a users' perspective.

[Held]

I've never seen a synth/FX that doesn't implement oversampling as a multiple of the sample rate.