Andy, I think you have it right, how you get the data out from the object is part of the problem. If that was well-mapped out, then that would make the C-coding much easier. I've never used those loop point things, so I don't really know much about them. A good starting point would be to sketch out how the interface of this loop point object would work, and how it would return the data. Then hopefully writing the C code would not be too hard.
libsndfile supports reading the loop info from .WAVs and .AIFFs http://www.mega-nerd.com/libsndfile/ .hc On Mar 8, 2009, at 1:35 PM, Andy Farnell wrote: > > > > Not sure if you could describe the job as simple > because after the initial header (which [wavinfo] > reads using byte/word offsets) the data format > can become variable length before you encounter > loop chunks. > > http://www.sonicspot.com/guide/wavefiles.html > > Also, there can be several loop points and cues, > so how should it work? > > It would be great to have an object that could > usefully do all the cool things possible with > ordinary wav files, but it needs a bit of thought. > > Maybe a message like [loop 3( could advance the > output to give the third loop boundaries, > and [next( could advance the "sampler" chunk > and show the number of repeats. > That way you could use wavs in a tracker style > as they are in simple game music audio. > > What lib were you thinking of to simplify > the job Hans? > > I think I suggested before, the idea of a more > advanced "sampler" type object set for extended. > (one that could eventually be extended by user code > to read Akai, NI and Yamaha formats and suchlike) > > A more complete [wavinfo] would be a step in > that direction. > > > > > > On Sun, 8 Mar 2009 12:01:19 +0100 > "Ingo Scherzinger" <[email protected]> wrote: > >> Unfortunately I don_t have any programming skills. Otherwise I >> would do >> something myself. >> >> To me it appears to be rather simple to expand the existing >> [waveinfo] to >> also read out sustain and release loop start and endpoints as well >> as the >> original pitch that was set. The basics about reading that >> information are >> already in this external. >> >> As mentioned this would speed up the creation of sample based pitched >> instruments tremendously. >> >> >> >> Ingo >> >> >> >> _____ >> >> Von: Hans-Christoph Steiner [mailto:[email protected]] >> Gesendet: Freitag, 6. März 2009 01:22 >> An: Ingo Scherzinger >> Cc: [email protected] >> Betreff: Re: [PD] external for sample loop start and end points? >> >> >> >> >> >> That would be very handy to have, since other apps use that wav >> info. It >> wouldn't be too hard to write one, I am sure there is a library which >> handles the hard parts. >> >> >> >> .hc >> >> >> >> On Mar 2, 2009, at 9:51 AM, Ingo Scherzinger wrote: >> >> >> >> Hi, >> >> >> >> I am looking for an external that can read the sample loop start >> and end >> points of a .wav file. >> >> I found [wavinfo] but that doesn_t do the trick _ no loop info! >> >> >> >> It would be great if anybody knew anything like that! >> >> >> >> Thank you, Ingo >> >> _______________________________________________ >> [email protected] mailing list >> UNSUBSCRIBE and account-management -> >> http://lists.puredata.info/listinfo/pd-list >> >> >> >> >> >> >> >> ---------------------------------------------------------------------------- >> >> >> >> If you are not part of the solution, you are part of the problem. >> >> >> >> >> >> > > > -- > Use the source > > _______________________________________________ > [email protected] mailing list > UNSUBSCRIBE and account-management -> > http://lists.puredata.info/listinfo/pd-list ---------------------------------------------------------------------------- Programs should be written for people to read, and only incidentally for machines to execute. - from Structure and Interpretation of Computer Programs _______________________________________________ [email protected] mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
