This is regarding the speexdec.c of the latest beta2 version. After decoding a frame, for packet_no =1, a new_frame_size and frame_offset are calculated and the number of decoded bytes writting onto a file depends on them. Why are they calculated? What happens if i directly write all the 320 shorts I get after decodong onto a file? --sharan -----Original Message----- From: Jean-Marc Valin [mailto:jean-marc.valin@usherbrooke.ca] Sent: Thursday, July 26, 2007 10:39 AM To: sharanu@sarayusoftech.com Cc: speex-dev@xiph.org Subject: Re: Crude delay? I think it's just the delay it found between the input and output. In any case, you shouldn't pay attention to it (unless you get a very large value, in which case it can mean a bug in how you generate the files). Jean-Marc Sharanu wrote:> Hello, > What is meant by crude delay in PESQ quality testing? > And what is its tolerant limit for good quality. > rgds, > Sharan > > >
Sharanu wrote:> This is regarding the speexdec.c of the latest beta2 version. > After decoding a frame, for packet_no =1, a new_frame_size and > frame_offset are calculated and the number of decoded bytes > writting onto a file depends on them. Why are they calculated? > What happens if i directly write all the 320 shorts I get after > decodong onto a file?You'll just get a delay that corresponds to the lookahead of Speex. No big deal. Jean-Marc> -----Original Message----- > From: Jean-Marc Valin [mailto:jean-marc.valin@usherbrooke.ca] > Sent: Thursday, July 26, 2007 10:39 AM > To: sharanu@sarayusoftech.com > Cc: speex-dev@xiph.org > Subject: Re: Crude delay? > > > I think it's just the delay it found between the input and output. In > any case, you shouldn't pay attention to it (unless you get a very large > value, in which case it can mean a bug in how you generate the files). > > Jean-Marc > > Sharanu wrote: >> Hello, >> What is meant by crude delay in PESQ quality testing? >> And what is its tolerant limit for good quality. >> rgds, >> Sharan >> >> >> > >