From: Nicolas George <george@nsup.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v2] lavfi/drawtext: Add localtime_ms for millisecond precision
Date: Sun, 16 Jan 2022 12:06:38 +0100
Message-ID: <YeP8Pm18oyNaZhrY@phare.normalesup.org> (raw)
In-Reply-To: <350ccc44-07dc-25c6-49a1-4281139d93ac@mail.de>
[-- Attachment #1.1: Type: text/plain, Size: 1563 bytes --]
Thilo Borgman (12022-01-14):
> v6 does:
>
> $> ffmpeg ... drawtext="fontfile=...:text='%{localtime \:%a %b %d %Y %S}'" (seconds)
> $> ffmpeg ... drawtext="fontfile=...:text='%{localtime_ms\:%a %b %d %Y %S}'" (milliseconds)
>
> I suggest v7 should according to your remark:
>
> $> ffmpeg ... drawtext="fontfile=...:text='%{localtime \:%a %b %d %Y %S}'" (seconds)
> $> ffmpeg ... drawtext="fontfile=...:text='%{localtime \:%a %b %d %Y %S}':show_ms=1" (milliseconds)
>
> Good?
I dislike both versions, from a user interface point of view: if there
is a format string, then it stands to reason, for the user, that the
resulting text is governed by the format string, not by an extra option
somewhere else.
There is no "use_four_digit_year=1" option, there is %Y instead of %y.
There is no "use_slashes=1" option, you write %Y/%m/%d instead of
%Y-%m-%d.
There are no "omit_date=1" and "omit_hour=1" options, you just write
what you want in the format string.
My proposal goes the same way:
$> ffmpeg ... drawtext="fontfile=...:text='%{localtime \:%a %b %d %Y %S.%3N}'"
It has several merits over your proposal:
- It can be extended later to support printing the milliseconds at
another place than the end (for example to put the time in brackets).
- It can be extended to support microseconds or centiseconds (%6N, %2N).
- It is somewhat compatible with GNU date and possibly a few others.
And I do not think it is harder to implement.
Regards,
--
Nicolas George
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 251 bytes --]
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2022-01-16 11:06 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <280498BE-226E-41E2-BE17-DE2D47EAFFC0@mail.de>
[not found] ` <tencent_9187CFF05512A70F389C961C4D142031CD07@qq.com>
[not found] ` <0768FA6E-731F-4214-8B90-A3F38764010F@mail.de>
[not found] ` <20211210164657.GF2829255@pb2>
[not found] ` <727CF2F6-C834-415A-B771-4F70661F8BE8@mail.de>
[not found] ` <AM7PR03MB6660ED0E212D1CCB2134A4DD8F729@AM7PR03MB6660.eurprd03.prod.outlook.com>
[not found] ` <3E808BD2-808B-4C53-B1F7-B9DFFE2BF687@mail.de>
[not found] ` <YbZXwy3d8Z9rG/hD@phare.normalesup.org>
2021-12-29 10:47 ` "zhilizhao(赵志立)"
2021-12-29 11:46 ` Nicolas George
2022-01-03 15:22 ` Thilo Borgmann
2022-01-06 11:27 ` Thilo Borgmann
2022-01-14 12:14 ` Thilo Borgmann
2022-01-14 13:17 ` "zhilizhao(赵志立)"
2022-01-14 17:40 ` Thilo Borgmann
2022-01-14 18:02 ` Zhao Zhili
2022-01-14 18:05 ` Andreas Rheinhardt
2022-01-14 18:15 ` Thilo Borgmann
2022-01-14 18:22 ` Andreas Rheinhardt
2022-01-14 17:57 ` Nicolas George
2022-01-14 18:04 ` Thilo Borgmann
2022-01-14 18:08 ` Nicolas George
2022-01-14 18:20 ` Thilo Borgmann
2022-01-16 11:06 ` Nicolas George [this message]
2022-01-18 12:52 ` Thilo Borgmann
2022-01-19 3:16 ` "zhilizhao(赵志立)"
2022-01-20 12:04 ` Thilo Borgmann
2022-01-20 14:58 ` Thilo Borgmann
2022-01-20 15:03 ` Andreas Rheinhardt
2022-01-20 15:32 ` Thilo Borgmann
2022-01-31 10:13 ` Thilo Borgmann
2022-01-31 13:08 ` Nicolas George
2022-01-31 20:59 ` Thilo Borgmann
2022-01-31 23:10 ` Andreas Rheinhardt
2022-01-31 23:40 ` Andreas Rheinhardt
2022-02-08 9:17 ` Thilo Borgmann
2022-02-08 9:27 ` Andreas Rheinhardt
2022-02-08 10:41 ` Thilo Borgmann
2022-02-22 11:36 ` Thilo Borgmann
2022-03-06 20:38 ` Thilo Borgmann
2022-03-08 12:30 ` Thilo Borgmann
2022-01-14 13:10 ` James Almer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YeP8Pm18oyNaZhrY@phare.normalesup.org \
--to=george@nsup.org \
--cc=ffmpeg-devel@ffmpeg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git