Hi Mike, <br> I was having a big problem earlier as there was a mismatch of over 16-20KB sometimes.<br> I have solved that problem now. After lot of debugging I could find out that granulepos wasn't being used at the correct place for identifying the pcm size of the data encoded.<br>
<br> BUT, currently I have a minor issue still left on the same lines. If I send the pcm size of the encoded data to another machine, and decode the encoded stream, there is "always" a mismatch of 4096 bytes :( Regarding your suggestion currently my mearsurement is on the same base(integer).<br>
<br>Can you help?<br>Thanks<br>Sumit<br><br><div class="gmail_quote">2009/8/28 Michael Smith <span dir="ltr"><<a href="mailto:msmith@xiph.org">msmith@xiph.org</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div></div><div class="h5">On Thu, Aug 27, 2009 at 1:12 PM, Sumit Chatterjee<<a href="mailto:getsumit@gmail.com">getsumit@gmail.com</a>> wrote:<br>
> Is the decoded pcm size of an encoded stream equal to the raw input sample's<br>
> pcm size? or Are they different?<br>
><br>
> raw sample(pcm sz1) --> encode --> decode(pcm_sz2)<br>
><br>
> Is (pcm_sz1 == pcm_sz2) ?<br>
><br>
> Could Anyone please clarify....<br>
<br>
</div></div>The number of samples will be the same. The size depends on what<br>
format your input and output are - libvorbis natively uses floats, for<br>
both input and output, so they'll be the same - but if you convert to<br>
an integer format, of course, they won't be.<br>
<br>
Mike<br>
</blockquote></div><br>