FabFilter

Sorry forgot the KVR topic.

www.kvraudio.com/forum/viewtopic.php?p=5204910

Please add HQ or oversampling options to your older plugins, as the aliasing can be an issue.

For instance, there are settings on volcano (high resonance with modulation) that clearly sound better @ 96 kHz than 44.1 kHz.

I'm sure users would appreciate if they didn't have to run their entire system @ 96 kHz just because of 1 or 2 plugins.

Thanks,

John

I have tested both Saturn and Pro-C, the two accused plugins in that thread, and found that a) aliasing is not a problem with Pro-C at all, and b) it's only an issue with Saturn when using the amp sim modes (not tape or tube modes) and then only when the HQ mode is turned off. If you turn on HQ before rendering, aliasing should never be an issue with Saturn.

Hi all,

We're certainly aware of an aliasing problem with our 'creative' filters in Volcano, Timeless and Twin. This is primarily audible if you use the high-pass filters: the low-pass filters typically filter away their own aliasing, unless you use very high resonance: but even then the distortion usually hides the aliasing.

In addition, Twin might also introduce some aliasing when you use oscillator sync or ring modulation.

All of these problems can be solved with internal oversampling, which is precisely what we've done in Saturn (the HQ mode). We're definitely planning to add this to our other Creative plug-ins in a future update!

Most of our Pro plug-ins already have a linear-phase oversampling feature, except for Pro-C: we're planning to solve this in an upcoming new version as well. However, as bitflipper already mentioned, currently Pro-C certainly doesn't suffer from severe aliasing: the effect will be very subtle, but we still want to add the option of oversampling here too to be able to achieve the highest possible sound quality.

Cheers,

Thanks Frederik. You guys are awesome.

• Jeff

p.s. how about a "groove/feel" feature in a future Timeless update? :-)

Hi, It's great news that oversampling will be added. However, may I suggest oversampling the whole signal and not just one component ala voxengo.

Example: Oversampling just the compression/saturation part and not the filters or crossover path. You can see this in saturn in HQ mode aswell. Only the saturation part is oversampled and not the crossovers part. You can see this by soloing the band. You can see the frequency cramping near nyquist.

Same thing with Pro-C sidechain crossovers in the advanced mode.

My point is that voxengo for examle has this global oversample mode, where the entire signal path is oversampled so everything gets oversampled.

Hopefully, I've been able to explain my point clearly.. (fingers crossed :-D)

I'm very happy with this news :)

Thanks for chiming in Frederik...

John

@suuny_j: In Saturn we made the decision to oversample only the saturation part because it saves a massive amount of CPU. Otherwise you probably wouldn't be able to use 8x oversampling in practice.

Yes, you see some frequency cramping near the Nyquist frequency with the band crossover filters, but that doesn't do any harm. You get a slightly different crossover than an analog crossover would give you, but it doesn't influence the sound quality. And it doesn't introduce aliasing.

Cheers,

Hey guys

Any chance all plug-ins could always be oversampled during export? Maybe as an option? I like using several instances of your processors per project and find it inconvenient to have to go through each plug-in to check before bouncing.

Best,
Gero

We'll investigate that, but I'm hesitating to turn that feature on all the time. It's possible that you want the exact same sound when exporting so in that case, oversampling shouldn't be turned on in offline mode.

So this feature would require a separate option somewhere and we need to think about a way to integrate that intuitively.

Cheers,

Thanks, BIG Saturn fan here :-)

Hey when will an oversampling feature update to Timeless2, Volcano2, Twin2 be released?

You don't really need oversampling as much in the other plugins as in Saturn (distortion causes the most aliasing).

We'll definitely consider it when doing major updates to any of these plug-ins though!

Cheers,

Hi just thought I would put in a second vote for oversampling in volcano. I'm using the latest version and it noticeably sounds better when rendered at higher levels. I use it a lot and I use it at the more extreme settings of resonance etc. An optional oversample of say 4x or higher would be very useful to me personally. I'd love to see it included in a future update.

If you do introduce oversampling, could you maybe implement options similar to The Drop, where you can individually choose realtime and offline bounce internal sample rates? Maybe even an option to apply changes globally within a session? I'm not sure how difficult that would be. Just a request. :)

I do LOVE Volcano, especially the modulation. You guys by far have the best modulation system and GUIs. Obviously I like the sound as well ;)

As a side question, for Saturn...are there any particular tube circuits you modeled? I've been able to closely match SPL Twintube utilizing multiband mode and tone curving. Just wondering. It sounds good. I just can't place where I've heard them before.

Good idea regarding offline/realtime oversampling. However, we don't want to automatically enable oversampling for offline bounces because it can change the character of the sound.

Regarding Saturn, we didn't model any circuit in particular: just listened to a lot of different existing analog/digital saturators and tuned our algorithms the way we liked them best! :-)

Cheers,