<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Dear all<br>
<br>
Sorry for pushing this up again. I'd really like to implement a correct
seeking functionality.<br>
Whats the best method to get the time representation of a frame?<br>
<br>
Regards,<br>
Stefan<br>
<br>
<br>
Am 21.06.2010 11:58, schrieb Stefan Weber:
<blockquote cite="mid:4C1F37E1.5000002@blyth.ch" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
Dear all<br>
<br>
Conrad, thank you for your inputs and your help so far. I will use and
test the seek-rewrite branch as soon as possible.<br>
<br>
I figured out that the Keyframe position in the granulepos is the
NUMBER of the keyframe. When seeking with OGGZ, one has to supply the
TIME-position (milliseconds) of the desired frame. So I made a short
workaround by calculating the milliseconds position as follows:<br>
<blockquote><i>ms = (granulepos >> shift) * 1000 / noFPS;<br>
</i></blockquote>
Needless to say, this won't point me to the exact keyframe position.
Probably this rough calculation is not exact enough?<br>
What is the best approach to calculate the TIME-position for
oggz-seeking out of a given frame number?<br>
<br>
Kind regards,<br>
Stefan<br>
</blockquote>
</body>
</html>