buffer~ could not parse *.aif, err-1
Last night i downloaded drumfire for m4l. when i tried to load a sample the max window just writes "buffer~ could not parse *.aif, err-1". i thought maybe its only in this patch so i restarted max, made a new patcher and tried to load a file into a buffer~ with the read message. same problem..... then i tried the same with a wav, no problem . anybody knows what "err-1" is?
Do you have an example patch/device? and a sound file?
note: I deleted the duplicated topic.
its in every patch, as soon as i want to read an aif into buffer.its not special for one specific patch. also in all patches where it was working before?????
also with soundfiles i used before
It's definitely working here with the current version.
please send a mail to support including Max version, OS, a sound file and as much information you can.
I've got the same problem with Ableton's aiff files included in Cycling'74 library....
Also Foobar2000 cannot open them.
They're corrupted.
i currently have the same problem. windows 7, m4l 6.1.7. I cannot load any aiff file into buffer (could not parse). wav files work.
Latest Quicktime is installed. Strange, i'm also pretty sure it worked before.
ok, it is not true for any aif file, there seems to be a custom aif format used in Live Packs. They want to make sure the sounds are not used outside of Live, but they also prevent this way that you load this sounds to Max ~buffers.
Now i know what i have to filter but that caused some headache. Live Pack Sellers put a label on your products: samples not working with max4live devices. At least what I can tell on the Windows site.
part of header of working aiff:
FORM ±ÒAIFFCOMM
part of header of NOT working aiff:
FORM MÐAIFCFVER ... Ableton ContentSSND
If you think about the Live Api and the recording abilities of a m4l audio device, they even left some room to build a little converting thing if you're forced to.