[FFmpeg-devel] (sponsored) feature request
bouke at editb.nl
Thu Jul 3 15:11:47 CEST 2014
---- Original Message -----
From: "Kieran Kunhya" <kierank at obe.tv>
To: "FFmpeg development discussions and patches" <ffmpeg-devel at ffmpeg.org>
Sent: Thursday, July 03, 2014 3:06 PM
Subject: Re: [FFmpeg-devel] (sponsored) feature request
>> FFmpeg takes time to startup, and that time is not always the same.
>> some 200 and 450 Msecs on my system)
>> Thus, by feeding a TC in the commandline, it's impossible to get a
>> timestamp on output when encoding a live stream, as by the time FFmpeg
>> the first frame to work on, a couple of frames have already passed.
>> My case is to record from several inputs at the same time, and i need
>> matching TC on all streams (Thus, NOT the same start TC value on all, as
>> streams never start at exactly the same time.).
>> More clear now?
> How do you know your input streams are locked to the same master clock
Cause they are (or can be) genlocked. (Input is from Pro stuff over SDI)
> and where are the timecodes located in such a stream?
There aren't, or they are meaningless. That's why I need to set them myself,
so each stream has a TC representing the time of the day + optional offset.
> ffmpeg-devel mailing list
> ffmpeg-devel at ffmpeg.org
This email is free from viruses and malware because avast! Antivirus protection is active.
More information about the ffmpeg-devel