El.stutter~ + el.chopper~: why do they often crash Max?


    Oct 13 2008 | 2:54 am
    Hello - i just downloaded Eric Lyon's library of el objects, and am exploring the capabilities of el.stutter!~ and el.chopper~. These often crash Max for me. I thought it might be because I need to turn off DSP before changing files in a buffer~, and that has helped, but even while doing that, I still have Max crash while using these objects. Why might this be and what can I do to prevent this?
    much thanks.

    • Oct 13 2008 | 5:21 am
      The most productive step would be to post a patch with instructions that reliably produces the crashes you are experiencing.
      Eric
    • Oct 13 2008 | 11:10 pm
      hi,
      eric, since you're here... i really like your pot pourri i tried bashfest~ and i noticed that if you start the dsp without having given a buffer to bashfest~, it crashes max...
      -start max -create a new patcher -create [el.bashfest~] -start audio
      result :
      Thread 0 Crashed: 0 lyon.bashfest~ 0x035a870e bashfest_setbuf + 26 1 lyon.bashfest~ 0x035aa91e bashfest_dsp + 35 2 com.cycling74.MaxAudioAPI 0x170618e6 dspchain_ugendoit + 729 3 com.cycling74.MaxAudioAPI 0x17061e58 dspchain_donegraph + 430 4 com.cycling74.MaxAudioAPI 0x17062490 dspchain_compile2 + 325 5 com.cycling74.MaxAudioAPI 0x17062550 canvas_compile_dsp + 56 6 com.cycling74.MaxAudioAPI 0x1705f7b9 ad_start + 217 7 com.cycling74.MaxMSP 0x0002cf19 defer + 97 8 com.cycling74.MaxAPI 0x03405fa9 defer + 67 9 com.cycling74.MaxAudioAPI 0x1705bbcf ad_mess_start + 69 10 com.cycling74.ezdac~ 0x036ddac2 ezdac_start + 87 11 com.cycling74.ezdac~ 0x036ddbbd ezdac_mouseup + 40 12 com.cycling74.MaxMSP 0x000ac413 object_method + 901 .....
      cheers
      g
      2008/10/13 Eric Lyon
      > > The most productive step would be to post a patch with instructions that > reliably produces the crashes you are experiencing. > > Eric > >
    • Oct 14 2008 | 8:38 am
      Thanks G,
      That's a good bug report. The bashfest~ in the next LyonPotpourri release will not instantiate unless you specify a buffer, which of course prevents the bug you mentioned. I'll be taking a closer look at what happens when buffers are switched or invalid in several of my externals. Since I rarely change buffers after instantiation, I rarely encounter this kind of bug unless someone else reports it.
      Eric