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

[jonathantaquet]

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

[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