Saving polybuffers in Max 6 for Live 9
I’m having a lot of trouble trying to get a polybuffer~ to save with my song.
I have tried using both readfolder and a live.drop without much success.
Using readfolder with @embed 1, the initial load works okay but on reloading the song the polybuffer~ comes back empty. I can confirm that the samples are in Max’s search path, and no errors are printed to the console.
When dragging multiple files to a live.drop which appends to the polybuffer~ each time it’s called, the initial load is also fine but subsequent reloads get corrupted, for example the last item gets repeated many times, most other samples are missing, etc.
If there’s no recommended way to save polybuffers~ with M4L, I might look into creating a large number of live.drop and buffer~ pairs. But you would think there would be a better way!
Thanks in advance…
Half way there: I managed to get vanilla polybuffer~ reload working…
The file dialog for File Preferences initially came back with a path of format DISK:/Users/Me/etc.
The polybuffer~ loaded okay with readfolder, but reloading didn’t work.
Changing the path to ~/Me/etc fixed that.
The main downside is that the same samples are shared for each instance (meaning sample-loading can’t be part of the instrument). Not ideal but acceptable for what I want to do.
Now despite the weirdness surrounding live.drop and polybuffers~ with @embed 1, it looks like live only safely supports one-file-per-live.drop.
It seems like the only way to get full integration with Live then is to create individual live.drop and buffer~ pairs.
If I’m missing something please let me know!
[I'm on OSX by the way, running Max 6 on Live 9.]
i was trying to find a solution to this as well. figured out a fix and just posted this : http://jeremystewart87.tumblr.com/post/94120329288/m4l-automate-and-store-data-with-non-live-objects
hope this is helpful
- This reply was modified 1 week by jeremystewart87. Reason: Link