buffer~: can't read file now - why not?!?

    Jan 10 2012 | 3:36 pm
    A couple of old threads referring to this in the forums but neither with an answer.
    I'm trying to load a .wav into buffer object in a m4l device.
    It's giving me this error.
    Can anyone shed any light?

    • Nov 23 2012 | 8:31 am
      same problem here...did u find the problem? or a solution?
    • Nov 23 2012 | 10:17 am
      It seemed to happen for me when there was too much going on in my patch cpu wise.
      Optimizing and liberal use of deferlow seemed to sort it out for me.
      But I was feeling my way in the dark really.
    • Nov 23 2012 | 10:26 am
      i found the problem, too...it seems to be the elasricx~ object which i love and which doesn't seem to work anymore for MAX 6
    • Nov 25 2012 | 8:23 pm
      You might try to replace elasticx~ with Timo Rozendal's grainstretch. http://www.timorozendal.nl/?cat=11