fons adriaensen wrote:
> Would it ? It solves the problem, and all other apps will - or
> at least _should_ according to the WAV spec - just ignore it.
> What problems would be created by adding a new chunk ?
> The alternative would be a format that isn't standard at all.
The problems are as foll
On Tue, 2006-01-24 at 00:08 +0100, fons adriaensen wrote:
> On Tue, Jan 24, 2006 at 09:02:23AM +1100, Erik de Castro Lopo wrote:
> > fons adriaensen wrote:
> >
> > > What I need in particular is some way to calibrate the time
> > > axis - i.e. to say frame #N corresponds to t = 0, and some
> > >
On Tue, Jan 24, 2006 at 09:02:23AM +1100, Erik de Castro Lopo wrote:
> fons adriaensen wrote:
>
> > What I need in particular is some way to calibrate the time
> > axis - i.e. to say frame #N corresponds to t = 0, and some
> > other similar info, mostly sample indices.
>
> There is no existing c
fons adriaensen wrote:
> Hi all,
>
> is there a recommended way to write / read additional chunks in
> WAV files, using libsndfile (assuming it's possible at all - I
> didn't find any hints to this in the docs) ?
libsndfile already supports the addition of a number of specific
chunk types like P
Am Samstag, 21. Januar 2006 14:51 schrieb fons adriaensen:
> Hi all,
>
> is there a recommended way to write / read additional chunks in
> WAV files, using libsndfile (assuming it's possible at all - I
> didn't find any hints to this in the docs) ?
Not sure if this is possible with libsndfile. If
Hi all,
is there a recommended way to write / read additional chunks in
WAV files, using libsndfile (assuming it's possible at all - I
didn't find any hints to this in the docs) ?
What I need in particular is some way to calibrate the time
axis - i.e. to say frame #N corresponds to t = 0, and so
