bug with peek~ and buffer~

    Aug 14 2013 | 10:54 am
    Hi all,
    it seems that there is a bug with peek~ and buffer~ and the buffer size is not defined at the initialization. The example below, which is a copy/paste of the help patch from peek, does not work, at least on my machine:
    ... but this one, where the buffer size is set in ms a the initialization, works:

    • Aug 14 2013 | 5:33 pm
      These are both working ok for me in Max 6.1.3
    • Aug 15 2013 | 7:27 am
      Both also work here. mbp non retina 2 x 2.4 ghz osx 10.8.4 max 6.1.3. Btw hi Alexis. I followed a max workshop with you at IRCAM 3 years ago. As you can see, I was hooked up...
    • Aug 15 2013 | 8:52 am
      I guess I have to provide a more precise bug report, my previous message was too vague. So, on my machine at least (non-retina MBP, 2*2.3GHz, OS 10.8.4, Max 6.1.3, both 32 and 64 bits), when I load the following patch, only the buffer on the right is correctly filled:
      The left buffer is filled with a constant value which is the final value that was sent to peek. I tested it in 32 and 64 bits, with DAC on and off, with any possible sample rate and with several audio drivers, I still have this issue.
      Has someone the same problem?
    • Aug 15 2013 | 9:08 am
      Should have mentioned : tried with 32 bits version. But as it happens to you with both version anyway...
    • Aug 16 2013 | 12:07 am
      I had the same problem, but after downloading the latest version of 6.1.3 it seems to work fine again...