You assume everybody would use a clipper to go deep into the flesh and distort the signal heavily...which is actually not the job of a clipper...lodsb wrote: ↑Fri May 03, 2024 12:46 am You can measure the aliasing that Over produces. In my tests it was less than Kclip with 32x oversampling at about half the CPU use (single-band, hardclip, 48khz SR). So, depends on the viewpoint. If you think clipping loads of channels, generating aliasing on top of aliasing, but in a cpu-friendly manner is the usual use-case for mixing, you can drop bitwig a friendly email and ask if it is possible to implement that.
What does you serve extreme antialiasing if you use a clipper for what it´s actually made for???
It´s made to clip off transients... short spikes which often last less than a millisecond and are 99% settled just in the extreme high frequency range...
Everybody who tells me you would need any antialiasing respectively OS in this moment at all has just lost his mind...
Nonetheless many people are abusing clippers for extreme distorting as well and that´s fine...
Easy solution: Offer a simple switch where you can enable your good antialiasing in the moment you need it but do not force everybody to use 30 times the CPU for situations where it doesn´t bring anything on the table apart from CPU increase...
We run in circles here... of course there can be situations where this higher quality is wished and needed... same for this compressor+ thingie... same for Polymer... same for the Grid...
This doesn´t justify to force everybody to always spend the higher CPU costs no matter what...even if you want lower quality... you simply cannot... they do not allow it!
Again: Why did every plugin developer out there spend the effort to provide you with user settings about the quality/OS???
Because there are multiple situations... sometimes it makes sense...sometimes it just wasted resources as you cannot (or even don´t want to) make use of the higher quality...
The Bitwigs are giving a sh*t on this fact...