[FFmpeg-devel] PATCH: Make -copyts a tri-state
rodger.combs at gmail.com
Fri Oct 17 10:19:16 CEST 2014
> On Oct 15, 2014, at 06:00, Rodger Combs <rodger.combs at gmail.com> wrote:
>> On Oct 15, 2014, at 05:37, Nicolas George <george at nsup.org> wrote:
>> Le quartidi 24 vendémiaire, an CCXXIII, Rodger Combs a écrit :
>>> Discussed this briefly on IRC; decided this was a good idea. I'm not sure
>>> if the commit message explains it well enough; please poke me here or on
>>> IRC if it doesn't.
>>> From 617b532c8a403c1cf06e60c99e9f36c787553b43 Mon Sep 17 00:00:00 2001
>>> From: Rodger Combs <rodger.combs at gmail.com>
>>> Date: Wed, 15 Oct 2014 05:00:02 -0500
>>> Subject: [PATCH] Make copyts a tri-state, with `no` normalizing input
>>> This doesn't change the default or `-copyts` behavior, but allows
>>> `-nocopyts` to make e.g. `-ss 50` have timestamps starting at 50 seconds,
>>> even if the input file's timestamps start at a value other than zero.
>>> ffmpeg.c | 6 +++---
>>> ffmpeg_opt.c | 4 ++--
>>> 2 files changed, 5 insertions(+), 5 deletions(-)
>> It looks like you forgot to update the documentation too.
>> Nicolas George
>> ffmpeg-devel mailing list
>> ffmpeg-devel at ffmpeg.org
> Indeed I did. Here you go:
> It occurs to me that it might be more useful in some cases to have one master input file (the first one?) be shifted so its timestamps start at zero, and the rest be shifted by the same amount as the master. That might be a good argument for making this its own option, instead of making copyts a tri-state.
> I'm not particularly attached to the naming or implementation here, so suggestions are plenty welcome :)
Upon some further testing, this seems to create some unusual and undesired behavior in some cases, and I'm not sure exactly why. The patch is definitely not ready, but I'd appreciate it if anyone could help work out a better design for the feature.
More information about the ffmpeg-devel