I ended up breaking out a hex editor and having a go at this myself â Initially I thought I could use AudioFileWriteBytes to write the header info before writing out the sample data however this resulted in the
bytes I was writing ending up in the âdataâ chunk.
In the hex editor I noticed that all my caf files produced by afconvert had a bunch of empty space in the âfreeâ chunk so I ended up just reading the file, finding the âfreeâ chunk, adding an âinstâ chunk and
reducing the size of the âfree âchunk accordingly.
I have no idea if this is the correct way to go about this? (for instance is it guaranteed that the âfreeâ chunk has enough room for all the other chunks?)
Neil
I currently load my samples into an AUSampler using an .aupreset file, however I would prefer to just load
caf files with appropriate metadata relating to key range etc â the docs say this should be possible:
Each audio file should have been edited appropriately to contain instrument data (for example key range, velocity range, root key)
However I canât see anywhere that tells me how exactly I add this metadata â can anyone point me in the right direction?
Cheers
Neil
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden