Dan Wilcox was working in the ability of [soundfiler] to read the loop point within Pd.

In Pd 0.51.1 there was still no change concerning sample loop points - unless it's not documented in the help file.

Reading and writing loop points outside of Pd is no problem. I've been doing this for more that 30 years.

However, I need to be able to automatically read loop points within Pd when unknown samples are being loaded.

So far I had to get the loop points in other softwares and write lists for Pd to be able to handle them.

This is rather tedious and also prone for errors. One little typo and you get clicks!

Especially this won't work for simply loading new sample into an existing Pd patch by other users.

I hope Dan didn't give up on ths . . .

Ingo

From: Alexandre Torres Porres [mailto:porres@gmail.com]
Sent: Sunday, November 08, 2020 9:13 PM
To: Ingo
Cc: Pd-List
Subject: Re: [PD] Sample loop - start and end point (WAV files)

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