"debugging" msp


    Aug 02 2007 | 9:31 pm
    hi, it might sound trite but when learning (and patching) i usually have an arsenal o debugging clippings. in jitter (my main dish) i was saved a lot of time using a combination of unpack and cellblock, matrixinfo ect. what do you use when taking patches apart? thank you.

    • Aug 02 2007 | 9:34 pm
      something like
      On 8/2/07, yair reshef wrote: > > hi, it might sound trite but when learning (and patching) i usually have > an arsenal o debugging clippings. in jitter (my main dish) i was saved a lot > of time using a combination of unpack and cellblock, matrixinfo ect. > what do you use when taking patches apart? > thank you. >
    • Aug 07 2007 | 5:02 pm
      yair reshef schrieb: > something like
      Mine is shorter and does the same, not as clipping, but as prototype for scope~:
      The most used clipping I have is [set]->[message box]...
      I also have a special debug abhaXion, to print or display values. I can switch them on/off from a central point. This is useful as you could leave them in the patch even after its ready, because the have no cost if switched off. (Especially printing into the max window is pretty expensive...)
      Recently I created a special monitor for seeing what's going on in a pfft. It will dump values into a buffer~ and I can watch the buffer~ with wavefrom~. This is indespensible for me, for any fft work...
      Have a look at my St.ools collection. I am not sure if the latter made it to the last version...
      Stefan
      -- Stefan Tiedje------------x------- --_____-----------|-------------- --(_|_ ----|-----|-----()------- -- _|_)----|-----()-------------- ----------()--------www.ccmix.com
    • Aug 08 2007 | 7:04 am
      Stefan, i re-searched your st.ools (your meticulous and intimate knowledge of max is evident in every one of them), and couldn't find the ftt analysis abstract, which should come in very handy. please consider updating your package, i will continue following it, thanks.
      On 8/7/07, Stefan Tiedje wrote: > > yair reshef schrieb: > > something like > > Mine is shorter and does the same, not as clipping, but as prototype for > scope~: > > #P user scope~ 85 355 302 445 2 3 128 -1. 1. 0 0. 1 0. 102 255 51 135 > 135 135 0; > #P window clipboard copycount 1; > > The most used clipping I have is [set]->[message box]... > > I also have a special debug abhaXion, to print or display values. I can > switch them on/off from a central point. This is useful as you could > leave them in the patch even after its ready, because the have no cost > if switched off. (Especially printing into the max window is pretty > expensive...) > > Recently I created a special monitor for seeing what's going on in a > pfft. It will dump values into a buffer~ and I can watch the buffer~ > with wavefrom~. This is indespensible for me, for any fft work... > > Have a look at my St.ools collection. I am not sure if the latter made > it to the last version... > > Stefan > > -- > Stefan Tiedje------------x------- > --_____-----------|-------------- > --(_|_ ----|-----|-----()------- > -- _|_)----|-----()-------------- > ----------()--------www.ccmix.com > >
    • Aug 09 2007 | 7:28 am
      yair reshef schrieb: > Stefan, i re-searched your st.ools (your meticulous and intimate > knowledge of max is evident in every one of them), and couldn't find the > ftt analysis abstract, which should come in very handy. > please consider updating your package, i will continue following it, > thanks.
      For the impatient... ;-)
      Have fun...
      Save as binalyze.pat
      Save as binalyze.pfft
      Save as binalyze.help
      -- Stefan Tiedje------------x------- --_____-----------|-------------- --(_|_ ----|-----|-----()------- -- _|_)----|-----()-------------- ----------()--------www.ccmix.com