What does it mean when -
a patch is running, audio (as indicated by meter~s) is coming into the patch, being processed by modules (meter~s in the modules), arriving at the receive~ objects just before the output faders (meter~s attached to the receive~ objects), and yet when I attach them to the output faders, nothing comes out.
A bit more...
The patch (actually this occurs with several different patches - but all with similar patcher modules in them) will run along fine for a while, then there'll suddenly be a huge splat, and the audio output disappears. Turning audio off and on again just produces another huge splat (though audio is still running in the patch, according to all the meter~s). The only solution is to quit and restart max.
I've tried removing several of the modules, thinking that perhaps it's a problem with a vst~ plugin, or biquad blowing up, but I still get the random blowup after 5-10 minutes. I haven't taken out the main processing modules (otherwise nothing to test!) which contain elasticx~, but then they still seem to be working when the audio blows up, so...
[edit - I just ran everything again, with number~s in parallel with the output faders, and when things blow up I can see [nan] there (which is what i expected). I'll add more number~s working backwards to see if I can narrow down where it's coming from, but any input as to what could cause this would still be appreciated!]
I'm now at a loss as to what to try next. Any ideas?
(This has only started occurring since I moved to Max6. And this is on a retina macbook pro, with latest OS and latest maxmsp etc etc)