I’ve been experiencing this issue somewhat rarely where the onset detection in my patches stops working (all other audio carries on), and it’s been very tricky to track down since recompiling the DSP chain resets the problem (so adding
scope~s and such ends up fixing things before I can find out where the problem is happening).
Last night I managed to be able to narrow it down to, I believe,
fluid.ampfeature~. Here’s a video showing the problem (pardon the shitty audio as it’s just a laptop screencapture):
In the vid you can see that the signal coming out of
fluid.ampfeature~ completely stops (and Max playback continues). I didn’t have a
number~ box connected, but that scope is going from 2-20 so it likely dropped to 0 when it died(?). You can also see the CPU drop when this happens. When I delete/undo the
live.scope~ you can see the audio start up again.
If you listen closely you can hear a little ‘click’ when the audio freezes as well.
Coincidentally in this video the freeze seems to happen right as the audio comes to the end of the loop, but this is just chance as it happened many other times and seemingly randomly.
This is on my (slower) laptop, but I have also experienced the same issue on my (M2) desktop this morning, but much much more rarely (it’s happened once this morning while testing the same patch but having a hard time reproducing).
This is on version 1.0.6+sha.e748875.core.sha.f694a366 (on both machines), with the desktop being Max 8.5.6 on OS 13.4.1, and the laptop on 8.5.5 and I don’t remember the OS but it’s a maybe OS11 or thereabouts).
One thing that occured to me is that it could somehow be the internal filter blowing up as that sort of click followed by silence reminds me of that. Trying to see if I can get it to reproduce now to then set
@highpassfreq to 0 to bypass it (according to the docs).
Does this point to anything?
Is there anything else I can try and do to “capture” the problem? (since it’s not crashing or producing a crash report, that’s about as far as I know how to look).
I’ll see if I can get it to reproduce consistently again and see if the
@highpassfilter bypassing removes the problem (potentially pointing at a blown up filter being the issue?