> 3)relying on the local system clock to provide future timestamps using the
> given value as offset.
>... this approach is vulnerable to clock drift.
I don't know about Robert's use case, but in many situations, timecode is given
as a start index and simply frame-counts up from there. Timecode a
- Original Message -
From: "Nicolas George"
Already done, for the most part. You should explain your actual problem in
details instead of trying to hire someone.
Ok, i'll try to outline the problem a bit more, and add some stuff others
wrote on the develop L.
And of course i'm inter
> -Original Message-
> From: ffmpeg-user-boun...@ffmpeg.org [mailto:ffmpeg-user-
> boun...@ffmpeg.org] On Behalf Of Bouke (VideoToolShed)
> Sent: 17 July 2014 16:42
> To: FFmpeg user questions
> Subject: [FFmpeg-user] Want to hire a coder
>
> Hi all,
> Tried this on the FFdevelop list, but
Le nonidi 29 messidor, an CCXXII, Bouke (VideoToolShed) a écrit :
> Instead of taking the timecode from the user, it could also use the system
> time. My main concern is that I get multiple recordings starting at
> different moments in sync.
>
> Does this make sense?
> Doable?
Already done, for t
> '-timecode hold_horses'
I vote for this feature. Particularly if the commandline argument is as
specified.
P
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user
