freeing zero signal?

    Oct 25 2012 | 8:07 pm
    i have this message in my max window i don't from where and what does it means??? can you help me?
    thank you laurent

    • Oct 26 2012 | 10:25 pm
    • Oct 27 2012 | 10:02 am
      I used to get the same thing occasionally. Or rather, I still do somethings, but even more rarely?
      There's an old thread on the forum but the relevant comments have been deleted, so not sure what to make of it really.
    • Oct 28 2012 | 7:22 pm
      What version of Max are you using? Are you on a Mac or Windows machine? Do you only get it with only one patcher, or all the time? Does it happen when you first launch the patcher, or when something gets changed in the patcher? Does it seem to be related to a specific object? These kinds of things--as well as being able to see the patcher itself--can help folks identify the issue. Periodically, I get odd things in the Max window as well, but they seem to happen much less frequently than before.
    • Oct 28 2012 | 7:54 pm
      On Mac (10.8.2), latest Max (6.0.7) though the problems have happened pre 10.8 and through all versions of Max6.
      It's hard to reproduce but always happens when I'm editing the patch, and only really pops up once per time I notice it (hence why it's so hard to reproduce). I used to think it was related to using old externals (fftease) but even after dropping them, I still get it from time to time. The only externals I'm using are AHarker externals.
    • Oct 28 2012 | 8:39 pm
      I think I only get this message when using poly~ But I've never experienced this error compromising the patch's performance.
    • Oct 28 2012 | 9:10 pm
      I've got polys for days in my patch.
      Same here, never had any problems with it, I just hate the fact that clicking on it doesn't highlight what causes the error (and that there's no documentation on it on top of that).
    • Oct 29 2012 | 12:06 pm
      i use max 6.0.7 on mac os 10.6.8 this message appears since i use poly (with a groove and record in it), i don't know from where it comes, i work only on one project so it's allways the same patch and appears all the time when i lauch the patch, it's possible that it slow down the launching of my patch