Dynamic Oversampling up to 128x or more
-
@clevername27 If you use saturation or distortion (in some cases for the convolution too) in the plugin, you have to do oversampling in these parts, otherwise there will be Aliasing.
Apart from this, if there is no saturation or harmonic distortion in the other modules you use, you do not have to oversample; in fact, you should not do it so that you can ensure optimum CPU usage.
-
@orange Thanks - makes sense.
-
@Christoph-Hart Just a friendly little bump to see if this is on your radar.
-
-
@Dan-Korneff What happens if you wrap a 16x OS node into another 16x node?
-
@aaronventure Alright you get an error.
But using
Engine.setMinimumSampleRate(384000)along with the 16x oversampling node seems to work, though. That should give you 128x in non polyphonic scriptnode. -
@aaronventure I was asking for switchable linear/minimum phase in the oversampling node.
I'll hack away at it this week. -
@Christoph-Hart Could you give me a hint on what you would do to achieve this?
switchable linear/minimum phase in the oversampling node
I don't want to fill you up with too many requests and would at least like to start with your suggested approach.
-
@Dan-Korneff you could probably do this in Faust using si.rev
-
@aaronventure That sounds little more complicated than an adjustment to the existing node. Linear and minimum phase algorithms are already in the source code. I just need a button to switch between the two.
-
This post is deleted!
