[FFmpeg-devel] [PATCH 1/2] timecode: move timecode muxer options to metadata.

Tim Nicholson nichot20 at yahoo.com
Thu May 31 12:22:15 CEST 2012

On 30/05/12 17:03, Clément Bœsch wrote:
> On Wed, May 30, 2012 at 04:45:51PM +0100, Tim Nicholson wrote:
>> On 30/05/12 13:58, Clément Bœsch wrote:
>>> From: Clément Bœsch <clement.boesch at smartjog.com>
>>> Some demuxers set a timecode in the format or streams metadata. The
>>> muxers now make use of this metadata instead of a duplicated private
>>> option.
>>> This makes possible transparent copy of the timecode when transmuxing
>>> and transcoding.
>> That sounds very handy.....
> :)
>>> -timecode option for MPEG1/2 codec is also renamed to -gop_timecode. The
>>> global ffmpeg -timecode option will set it anyway so no option change
>>> visible for the user.
>>> [...]
>> So what happens if rewrapping an existing stream and setting
>> -gop_timcode? Does this mean you could have wrapper timecode set to one
>> value (by transparent copy) and gop_timecode to something else?
> Yes but you are not supposed to use -gop_timecode (it's not documented)
> except if you know what you are doing. Just use -timecode all the time.

I try to convey an air of knowing what I'm doing. Most of the time I get
away with it.. ;)

> If you really want to do this, you can:
> % ./ffmpeg -v 0 -f lavfi -i testsrc -t 5 -c:v mpeg2video -s ntsc -timecode 01:02:03:04 -gop_timecode 04:03:02:01 -y out.gxf
> % ./ffprobe -v 0 -show_format -show_streams out.gxf|grep timecode=
> timecode=04:03:02:01
> TAG:timecode=01:02:03:04
> %

I can think of a number of uses where that would be extremely helpful...

All that's lacking now is the .mov support :P


More information about the ffmpeg-devel mailing list