thank you!! appreciate your work. I use 2.2 all over the place in my sessions. im saying this in the nicest way possible, cuz im one too haha, but since your such a nerd, check out Acustica's clipper "Ash Ultra" or their saturator "pumpkin pro". The anti aliasing oversampling algo's they have are BONKERS.
Robert K//Groov MekanikCreator
Haha I take it as a compliment, I am definitely a nerd 🤓
I have avoided Acustica due to the stepping of parameters and high CPU usage as well as the need for an installer/licenser app. Is there something specific about their oversampling methods that you like?
Its hard to judge what they are doing because their architecture is likely to be very different with a lot of their work using machine learning. Its funny that they have up to 64x oversampling when I've learnt that I can get less aliasing with less oversampling, hence the update.
Anti-aliasing is never a single approach, its usually a combination of many smaller decisions and compromises, combined with an oversampling method that suits the particular processing. I'm all ears for improvement to oversampling methods in Max, which is part of the reason I have open sourced my code for the Linear-phase oversampling methods I'm using.
Clip
Hello, the work you do is excellent, I have been following you for a long time, if you could make a recommendation it would be that the display part be larger so that it can be appreciated much better.
Thank you so much
Greetings!
Robert K//Groov MekanikCreator
Thank you! 😊
Thanks for the suggestion 😁 Are you suggesting the input and output meters be smaller to make more room for the centre display, or create a floating window for the centre display? I normally run Live at 120% zoom and it feels pretty good to me.
2601026521509
Thankssss Robert, I use a couple of your devices , you rock man , i love your works...greetings from Spain
Robert K//Groov MekanikCreator
As do you my friend 🤘 thank you & happy music making 😁
7049330557260
Hey Robert- your devices are daily drivers for me man! Especially this clipper and the ducker. THANK YOU for making them!
I have a weird ask- would you ever consider making an enlarged version of the oscilloscope you have in Clipper? Its super helpful for visualizing not only the peaks to cut, but also the work compressors/ saturators/ etc are doing before the clipper. Just a thought!
Keep doing great work. _M
Robert K//Groov MekanikCreator
Great to hear! 🙏 That is a very good suggestion, I will consider it for a future 'Analyzer' type device, perhaps it could show the level pre/post processing. Happy Music Making!
8582207498633
Hey Robert I'm having some issues with your clipper — it's just not clipping like I would expect it to. I've set up a simple set that takes the same signal and routes it multiple tracks each with different clippers and an oscilloscope. Well, I get the results I would expect with KClip: the waveform is pushed up to 0db and the tops are chopped off perfectly and cleanly. With your clipper: it's a complete mess. Not only is the signal going way above 0, there's noise at the peaks and there's blips of noise at what should be silence between peaks — which I'm assuming is aliasing noise. You can see the same result without an oscilloscope by resampling/rendering the audio and zooming into the produced waveform.
If I enable the BW Limiter, yes now it's no longer going over 0db, but it's not even working like a clipper anymore. Peaks that should just be solid blocks of 0 values look like they were limited. This actually leads to an unwanted audible "ducking". I've been struggling with certain aspects of my mixes for a while and I've come to realize that your clipper has been the culprit. If you can send me an email I can send you the set and screenshots of what I'm looking at in the oscilloscopes.
Robert K//Groov MekanikCreator
Hey there! Please send me an email by replying to your receipt and we can inspect this problem together 😁 I've been using Clipper on clients mixes with absolutely no issues and unfortunately I can not see your name or email from your comment. I can recreate a pumping effect if I push the signal to +48dB before applying clipping and enabling the BW Limiter but this seems like an extreme scenario, in any case your feedback is valuable could help me improve the device.
Robert K//Groov MekanikCreator
For everyone else wondering; This has helped me spot a weakness in my device, I never noticed it being a problem in the way I use Clipper but its definitely there. It all has to do with the delta technique I'm using which is great an all (results in no filtering when theres no clipping) but is a bit weird if your pushing signals beyond 0dB before clipping (as many do, I tend not to) and isn't what people are used to (its beneficial to use a LPF before of after, which kind of negates the point of it to a degree, again something I account for but others probably don't), I had someone else contact me after trying to test the device with results they weren't expecting as well, so it makes sense to just remove the delta technique. Its not a bug, just perhaps not quite the right technique to use in a Clipper I've now realised... So there will be another update again soon, potentially with more oversampling options!
11 comments
thank you!! appreciate your work. I use 2.2 all over the place in my sessions. im saying this in the nicest way possible, cuz im one too haha, but since your such a nerd, check out Acustica's clipper "Ash Ultra" or their saturator "pumpkin pro". The anti aliasing oversampling algo's they have are BONKERS.
Haha I take it as a compliment, I am definitely a nerd 🤓 I have avoided Acustica due to the stepping of parameters and high CPU usage as well as the need for an installer/licenser app. Is there something specific about their oversampling methods that you like? Its hard to judge what they are doing because their architecture is likely to be very different with a lot of their work using machine learning. Its funny that they have up to 64x oversampling when I've learnt that I can get less aliasing with less oversampling, hence the update. Anti-aliasing is never a single approach, its usually a combination of many smaller decisions and compromises, combined with an oversampling method that suits the particular processing. I'm all ears for improvement to oversampling methods in Max, which is part of the reason I have open sourced my code for the Linear-phase oversampling methods I'm using.
Hello, the work you do is excellent, I have been following you for a long time, if you could make a recommendation it would be that the display part be larger so that it can be appreciated much better. Thank you so much Greetings!
Thank you! 😊 Thanks for the suggestion 😁 Are you suggesting the input and output meters be smaller to make more room for the centre display, or create a floating window for the centre display? I normally run Live at 120% zoom and it feels pretty good to me.
Thankssss Robert, I use a couple of your devices , you rock man , i love your works...greetings from Spain
As do you my friend 🤘 thank you & happy music making 😁
Hey Robert- your devices are daily drivers for me man! Especially this clipper and the ducker. THANK YOU for making them! I have a weird ask- would you ever consider making an enlarged version of the oscilloscope you have in Clipper? Its super helpful for visualizing not only the peaks to cut, but also the work compressors/ saturators/ etc are doing before the clipper. Just a thought! Keep doing great work. _M
Great to hear! 🙏 That is a very good suggestion, I will consider it for a future 'Analyzer' type device, perhaps it could show the level pre/post processing. Happy Music Making!
Hey Robert I'm having some issues with your clipper — it's just not clipping like I would expect it to. I've set up a simple set that takes the same signal and routes it multiple tracks each with different clippers and an oscilloscope. Well, I get the results I would expect with KClip: the waveform is pushed up to 0db and the tops are chopped off perfectly and cleanly. With your clipper: it's a complete mess. Not only is the signal going way above 0, there's noise at the peaks and there's blips of noise at what should be silence between peaks — which I'm assuming is aliasing noise. You can see the same result without an oscilloscope by resampling/rendering the audio and zooming into the produced waveform. If I enable the BW Limiter, yes now it's no longer going over 0db, but it's not even working like a clipper anymore. Peaks that should just be solid blocks of 0 values look like they were limited. This actually leads to an unwanted audible "ducking". I've been struggling with certain aspects of my mixes for a while and I've come to realize that your clipper has been the culprit. If you can send me an email I can send you the set and screenshots of what I'm looking at in the oscilloscopes.
Hey there! Please send me an email by replying to your receipt and we can inspect this problem together 😁 I've been using Clipper on clients mixes with absolutely no issues and unfortunately I can not see your name or email from your comment. I can recreate a pumping effect if I push the signal to +48dB before applying clipping and enabling the BW Limiter but this seems like an extreme scenario, in any case your feedback is valuable could help me improve the device.
For everyone else wondering; This has helped me spot a weakness in my device, I never noticed it being a problem in the way I use Clipper but its definitely there. It all has to do with the delta technique I'm using which is great an all (results in no filtering when theres no clipping) but is a bit weird if your pushing signals beyond 0dB before clipping (as many do, I tend not to) and isn't what people are used to (its beneficial to use a LPF before of after, which kind of negates the point of it to a degree, again something I account for but others probably don't), I had someone else contact me after trying to test the device with results they weren't expecting as well, so it makes sense to just remove the delta technique. Its not a bug, just perhaps not quite the right technique to use in a Clipper I've now realised... So there will be another update again soon, potentially with more oversampling options!