It seems seek() on mp4 file seeks to the closest keyframe (seekpoint). Is it possible to seek to exact position in between of keyframes?
Thanks!
views:
238answers:
2
+1
A:
It does in fact seek to the nearest key frame. If you want to be able to seek to more specific parts of the stream you'll need to add more key frames. Of course more key frames usually results in larger file size. Good luck!
heavilyinvolved
2010-07-26 21:08:27
@heavilyinvolved. I think it's the other way round. More keyframes mean less processor time, because there's more data and less stuff to interpolate (though it trades off space, i.e. it takes more memory/bandwidth).
Juan Pablo Califano
2010-07-27 01:34:19
@Juan Pablo Califano yeah you're right... updated.
heavilyinvolved
2010-07-27 05:52:09
A:
I have used the following properties in the meta data handler for finding the keyframes, but returned nothing:
var kfPoints:Object; for (var propName:String in metaInfoObj) { if (propName == "keyframes") { trace ("Keyframes received"); var kfObject:Object = metaInfoObj[propName]; kfPoints = kfObject["times"]; } }
How can I find keyframes in an mp4 file transcoded with an H264 codec?
supriya tenany
2010-07-28 07:02:32
They are called 'seekpoints' in the object, not 'keyframes' for mp4.`public function onMetaData(infoObject:Object):void { trace(infoObject.seekpoints)}`. If it helps, can you make separate question for this and I'll post full code?
artvolk
2010-07-28 13:24:57