Re: [Protux-devel] ugly click on wav output

[Luciano Giordana]

Just to let you know guys,
I am also working again in a daily basis on protux. commiting everyday, so 
keep in sync, guys
Now it is running again. Only lacking some jmb callbacks to be defined...

thanks


On Thursday 12 February 2004 15:16, Martin Herren wrote:
> On Sun, 8 Feb 2004 16:57:13 +0100
>
> Martin Herren <address@hidden> wrote:
> > i noticed there is again an ugly click at the begining of wav files,
> > regardless if they were generated by rendering a song to wav in Protux,
> > or if they were converted by praf...
> >
> >
> > Additional problem, which could be related: when converting a wav file to
> > wav or praf using praf, the output file is always 2 blocks bigger than
> > the original... For both problems i think it should be something related
> > to the wav headers... but didn't have time to investigate it more.
>
> ok, it seems as i found the error. When reading a wav file, i used
> read_header(), and then started with read_fragments(), wrongly assuming
> reading will begin at the right position, in fact it begins 8 bytes too
> soon ("data" keyword + audiosize (4 bytes))... this explains why the files
> grow in size, and why i had this ugly click. So before reading a file,
> skip_header() must be called, regardless if read_header() had been called
> or not. Alternatively, rewind_audio() can be used.
>
> So i can continue to split a few concerts to wav-tracks in order to make
> CDs... and continuing working on praf !
>
> /Martin

-- 
Best Regards
--
Luciano Giordana
Free Software Developer / Musician
Project Protux : Professional Audio Tools for GNU/Linux
http://www.nongnu.org/protux