How to store cue points in .wav for sliced loops? (e.g. for auto slicing)

[unknownError]

Hi! Jonathan, thanks for that great tool!

I saw the exported ".wav" files contain cue points for slicing, so when re-importing them that came pretty handy. Now I have loads of fresh loops I'd like to automatically slice and then import to the electribe (doing the slicing in an external audio tool or inside python or just some other command line tools) - just I didn't find out by looking quickly at your code how the cue points need to be stored inside a ".wav" file so Oe2sSLE can read them when importing. I'd be happy about a hint into that direction :). Are the cue points stored in a standard way that other software can read or display?

Martin

[JonathanTaquet]

Hi Martin,

I thought that cue points and loop information were stored in a "standard" way that should be understood by many software. I thought most of the daw should understand that meta data. But reading this how software may use them is probably not always standard...

I have tested that it works with wav editor of FL Studio (Edison)[https://www.image-line.com/plugins/Tools/Edison/] which allows to create/modify/edit them. But there are probably other tools that use them in a same way, and that you can use...

My code for handling that is in RIFF/cue.py
and for the loops it is in RIFF/smpl.py

I do not really remember where I took the format from, but by doing some quick search you can easily find things like this:

• cue chunk
• smpl chunk

Probably I took "cue chunk" information from the IBM/Microsoft wav file format documentation that is linked on Wave File Specifications in their local copy of the spec

and "smpl chunk" information here and there, for instance: WAVE File Format

If I remember correctly, I have debugged by checking that the cue/smpl chunk in Oe2sSLE had the same positions as in Edison. So, if Edison is not correct, Oe2sSLE is probably not too ;)

Thank you for your interest for this tool!

Jonathan