Weird Ableton behavior on Windows 10

Hi guys,

I have an implementation of a ZDF Biquad filter that’s working flawlessly anywhere (both on Windows and OSX), except in Ableton Live on Windows 10. The weirdest thing is, as soon as I stop the playback, the CPU meter increases. I already tried profiling, but I can’t figure out what’s going on there. Do you know what Ableton calls when the playback stops?


Check for floating point denormalization. If you get CPU spikes as audio fades out, that’s usually what it is.


Thanks. I had the same thought, but I’m already using doubles for those calculations. Maybe I should try to flush them to zero and see what happens.

yap, it was a denormal issue fixed using JUCE_UNDENORMALIZE. Thanks, G-Mon.

1 Like