[VeJa Titan] Aliasing problem

I think Titan amp is affected by aliasing problem. You can hear it clearly between 0:09 and 0:20
Can it be mitigated somehow?


This is what I’ve used for clip recording.

I didn’t noticed that, I don’t like the sound of Titan Amp, there too high frequencies. But I will ear if I have the same issue.

1 Like

I tried the AmpVST with a distortion in front since it is not a so high gain amp and oversampling 8x helps, aliasing still there but less noticeable than Titan and Onyx. Maybe we can just stick an oversampling and downsampling plugin in front of plugins that generate lot of harmonics? These operations obviously increases CPU usage. This is a key factor to consider in buying a digital amp modeler.

Are you using always the same cabinet?

Yes, it’s not related to cabinet, aliasing is there even with no cabinet in the pedalboard. Maybe it can be solved with an high cut filter for > 20kHz frequencies.

hmm ok. I asked because we discovered (and fixed) that issue on the cabinets. I’m not sure if the fixes are already available.

No they are not, but testing on this is very much appreciated! for now, you can get the WIP updated versions here :slight_smile:


This is Titan only (no cab) Vocaroo | Online voice recorder

This is Titan + faIR Vocaroo | Online voice recorder

I still hear aliasing with updated faIR.

I replaced this folder MDW/fair-cabsim.lv2 into /root/.lv2 and rebooted the Dwarf. Is it correct?

yes, that will work.
Alternatively using tar cz fair-cabsim.lv2 | base64 | curl -F 'package=@-' you dont even need the reboot

I’m able to replicate the issue, and even managed to solve parts of it already. I’ll bring this up with the rest of the team so we can see how best to proceed.

Thanks for the report!


Thanks a lot Jan! If you need beta testing feel free to ping me :grin:


Could the solution be applied system wide? I found same problem on cream machine too and maybe other plugins are potentially affected.

Seems that even Neural DSP is affected :sweat_smile:

Great explanation! So it seems that 8x oversampling is the best tradeoff for live playing. 16x I suppose would introduce too much latency.

1 Like

Yes, oversampling kills performance.

Same deal with ChowTapedelay. It may be good to patch the ttl to not allow full range of antialiasing settings?

This is something that would be nice, yes, but sadly, I don’t think it’s safely possible.

Looking at the Titan for instance, as it was made specifically for MOD, things tend to get designed with a sample rate of 48Khz in mind. Simply oversampling the full plugin is not only wasteful in terms of CPU, but can also result in unstable filters.

Imo this is something for the plugin developer to keep in mind, and make the tradeoff when it comes to the CPU load and (partially)oversampling.
Talking with the rest of the team, the Titan will probably get a toggle to enable/disable oversampling for the tube emulation part of the plugin.

For the Onyx things are a bit more tricky as the internals are completely different, and from my tests, I can not reduce the artifacts without changing the characteristics of the amp. Since this plugin is a bit older, we need to be careful changing things as we don’t want to break people’s pedalboards :sweat_smile: .


I’m wondering how would the Onyx sound with oversampling enabled. Maybe you can let the user choose whether turn it on or leave it turned off.


well, the Onyx is one of those plugins which starts to behave quite differently when the sample rate changes and even becomes unstable at some knob combinations.

I did however ask the original author Jarno to see what’s going on there, so perhaps he can get things sorted :slight_smile: .


@Jan would it be possible to add x2, x4, x8 oversampling to Onyx to see how it reacts? Maybe x2 would be a good tradeoff. I’m trying C* AmpVTS - Tube amp + Tone stack which has oversampling selection and it works nice at x2.

In theory sure, but personally speaking, I don’t think exposing such a control is better then the developer already making the trade offs between CPU and oversampling.

Nonetheless the plugin first needs to be adapted to work at different samplerates. I spoke to @Jarno and he mentioned he could have a look after some other pending things (such as the Titan update) are done.


@Jan any chance to have onyx updated?