Cue and loop points are saved in the metadata, the appropriate chunks are shown here https://sites.google.com/site/musicgapi/technical-documents/wav-file-format#... . Audacity will run on most anything and can read loop points.
On Sun, Nov 8, 2020 at 8:16 PM Alexandre Torres Porres porres@gmail.com wrote:
Ingo, did you have any luck on this throughout the year?
I'm also curious on this. Anyway, I had another thread here and someone suggested http://loopauditioneer.sourceforge.net/ that seems to read loop points - but I can't test it because it's linux
Em qua., 12 de fev. de 2020 às 05:39, Ingo ingo@miamiwave.com escreveu:
There are softwares like AwaveStudio that do nothing else but format conversion between different sampler formats that can handle the loop points as well.
I have been working with hardware samplers since the 80ies and used (mainly) softwares like SoundForge or Wavelab for looping. There was no extra file. All hardware samplers could read the loops.
Once a
file was looped with one sampler it would be looped with the next one. Same thing with modern software Samplers like Kontakt. I can use a sample that I looped in Wavelab and load it into SoundForge
and
it recognizes the loops. (There are options for multiple loops, though that might not work with
some
samplers.)
It can't be such a secret since over 30 years that all manufacturers (software or hardware) know about it but noone else. I have been looking around but couldn't find any information where the loops are stored in the file but they definitely are.
Ingo
-----Original Message----- From: Pd-list [mailto:pd-list-bounces@lists.iem.at] On Behalf Of
Roman
Haefeli Sent: Wednesday, February 12, 2020 8:48 AM To: pd-list@lists.iem.at Subject: Re: [PD] Sample loop - start and end point (WAV files)
On Tue, 2020-02-11 at 21:22 -0800, Alexandre Torres Porres wrote:
Well, I was really really hoping to see information here on how to get loop points from these files ;)
I looked around for specifications of the .wav-format and I wasn't able to find one that looks canonical. The ones I found didn't mention any loop start- and endpoints. I wonder whether there is a convention about how to encode this into some sort of metadata stored with file. Some description of the format describe the ability to store anything as metdata. Personally, I never dealt with such files (at least not knowingly). Maybe a good start would be to provide such a file, so that people can a have a look at it. It might be not that difficult to retrieve such data with something like mrpeach's [binfile], once you
know
how it is stored.
Roman
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list