Displaying 3 results from an estimated 3 matches for "keyframe_offset".
2008 Nov 03
0
No subject
...headers to get data=
. Some files have a first keyframe<br>
of 0, others have a first keyframe of 1. So:-<br>
<br>
2) Begin reading pages until we get at least one packet. Then check<br>
the granulepos to find the first keyframe number (0 or 1). Store this<br>
as e.g. keyframe_offset.<br>
<br>
Then:<br>
<br>
3) To get a target frame, first search through the file to find the<br>
largest granulepos<=3Dtarget, taking into account the keyframe_offset.<b=
r>
2008 Nov 11
5
further debugging of my ogg/theora decoder
Hi,
I am continuing to try to debug my ogg/theora decoder.
The issue seems to be that not enough packets are being pulled from the
bitstream, here is some sample output from my player with some debugging
comments put in:
(playback began at first frame, this is from the middle of the clip)
get page at 1765027
got packet
frame++, skip is 0
frame decoded
page processed, kframe=414 : offs=442
get
2010 Mar 11
4
Seek issue in cortado player
One of the issues I've consistently run into with the cortado player app is seek behavior, so I was curious to see how cortado handles video encoded with the latest ffmpeg2theora (0.26) and the new -seek-index option, so I tried converting an h.264 video:
ffmpeg2theora tronlegacy-tsr1_480p.mov --seek-index
This output the following advisory messages:
> Allocated 372 bytes for theora