<br><br><div><span class="gmail_quote">On 10/9/06, <b class="gmail_sendername"><a href="mailto:Nagaraj.CG@flextronicssoftware.com">Nagaraj.CG@flextronicssoftware.com</a></b> <<a href="mailto:Nagaraj.CG@flextronicssoftware.com">
Nagaraj.CG@flextronicssoftware.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br><font face="sans-serif" size="2">So i want to use only file seek functionality
in forward and backward.</font>
<br><font face="sans-serif" size="2">So i am planning to use this formula</font>
<br>
<br><font face="sans-serif" size="2">present_require_file_offset = (total_file_size
* 20 )/Total_time_of_stream(which i know)</font>
<br>
<br><font face="sans-serif" size="2">If i seek my file pointer to value of
"present_require_file_offset" ,whether i will be at 20 sec duration
of song or not,I know it cant be accurate ,but it is ok for</font>
<br><font face="sans-serif" size="2">me if i am at 19th or 21st second also.</font></blockquote><div><br>Yes, that is acceptible. Our vorbisfile also implements a similar fast seek. <br><br>You can seek to an approximate raw location in the compressed data, then simply report the next valid time seen from granule position when playback resumes.
<br><br>Monty <br></div><br></div><br>