On 08/27/2011 11:39 PM, Luca Barbato wrote:

On 8/26/11 9:06 AM, Camera Man wrote:
 > (a) is there a general way to bookmark frames while writing a file in
you can use a container format that supports chapters. (mkv and nut suggested)
Thanks. I will look into that. How many chapters is reasonable? e.g., if I have 500 chapters (every few seconds of a long video), will that work reasonable?
(b) is there a general way to encode *wall-clock* time into a file I
write? e.g. I want the "pts" (or equivalent) of the first frame of the
file to be 2011-08-26 02:13:57.917 (millisec resolution sufficient - 48
bits more than enough precision).
metadata streams and per-frame metadata might fit. again you need a container supporting this kind of stuff.
That's what I'll probably be doing. Is there a way to encode that into pts/dts, and having the first ever pts not zero?
(d) is there a way, other than subtitles, to add a visual timestamp to
the file while writing it, without decoding+overlaying+reencoding?
What's wrong with subtitles?
Nothing wrong with subtitles - except that I'll have to have a new subtitle for every frame (or 5), and I suspect there's some standard for adding wall clock visual timestamp that I'm not aware of.
(e) is there a way to tell, without decoding the video stream, that a
received packet starts a new non-key frame?

You can just parse it.

True. Then, I assume there is no standard way supported by libav to tell that?
for (b) (wall clock), assume an mp4 or avi file; if I don't start

mp4 and avi are quite different beasts...

given your application why do you want to use such containers?

Yes, they are very different - basically one of the requirements is "produces standard files playable by other programs or standalone dvd/blueray/mp4 player".

plain h264 - my preference and what I'm developing with now (because of how simple they are) are not good enough because there is not even a standard way to encode timing information in them.

Thanks for the thoughtful reply!
_______________________________________________
libav-api mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-api

Reply via email to