<div>hi Michael, </div>
<div>Got it, but how is it going to affect the decoding time ?? can u give an approximation of the amount of extra % of CPU time taken by returning errors to the seek and tell function calls ???</div>
<div>How is it going to affect the low-mem decoder ??</div>
<div><br><br> </div>
<div><span class="gmail_quote">On 10/19/05, <b class="gmail_sendername">Michael Smith</b> <<a href="mailto:msmith@xiph.org">msmith@xiph.org</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">> In this respect, the Ogg file seems like a stream. How do I decode the<br>> file if ov_open(..) expects a file pointer (I can't point to a partial file
<br>> with a file pointer, can I?)? Is there a way to decode Ogg streams where<br>> the compressed data comes in streaming in a limited fashion?<br><br>You presumably want ov_open_callbacks(), which will allow you to feed
<br>data into the decoder however you want. If you don't want to support<br>seeking, you can just return errors from seek/tell, and just return<br>data with each read() call. How you do that is up to you.<br><br>You should also be able to do seeking, but that's obviously a little
<br>more work - you might skip it to begin with.<br><br>Mike<br>_______________________________________________<br>Tremor mailing list<br><a href="mailto:Tremor@xiph.org">Tremor@xiph.org</a><br><a href="http://lists.xiph.org/mailman/listinfo/tremor">
http://lists.xiph.org/mailman/listinfo/tremor</a><br></blockquote></div><br>