From: Soft Works <softworkz-at-hotmail.com@ffmpeg.org> To: Marth64 <marth64@proxyid.net> Cc: Michael Niedermayer <michael@niedermayer.cc>, Soft Works <softworkz-at-hotmail.com@ffmpeg.org>, FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH v3 0/3] Add option to log timing Date: Fri, 7 Feb 2025 05:05:26 +0000 Message-ID: <DM8P223MB03657509ADCC56965A35DC2EBAF12@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw) In-Reply-To: <CAAhd_PX_UcXtTT84PqFpy8_pOWF5cfBr972pXsJZf9qAQff-GQ@mail.gmail.com> > -----Original Message----- > From: Marth64 <marth64@proxyid.net> > Sent: Friday, February 7, 2025 5:47 AM > To: Soft Works <softworkz@hotmail.com> > Cc: FFmpeg development discussions and patches <ffmpeg- > devel@ffmpeg.org>; Michael Niedermayer <michael@niedermayer.cc>; Soft > Works <softworkz-at-hotmail.com@ffmpeg.org> > Subject: Re: [FFmpeg-devel] [PATCH v3 0/3] Add option to log timing > > > it would probably also be odd when there's a single white space in- > between. > > Yes, it would look worse on white background. OK as is, then. Fine. If someone has a specific wish or idea, feel free to comment. > > Why wouldn't it be machine-parsable without those letters? > > It is more about having timezone, etc. > I actually think it is better for readability as is, but was checking > if preservation for machine parsing* (phrasing what I meant > better) was a goal, then it should be compliant. But I don't see much > value in that. We actually parse this output in some analysis tool, but only the time. > The example I was thinking of was if I wanted to look at the logs 2 > years later, it would have time zone in case of DST or whatever. > But it's a total obscure stretch case IMO. I'm not advocating for it, > just sharing what I meant with my logic. > (And if someone really needs it later they can make a +rfc3339 switch > or whatever) I don’t find that case "obscure" at all. In fact, the time zone can get really important when correlating information from multiple log files (e.g. ffmpeg + application). For this, we are printing the full date with time zone just once at the top of the logs and let ffmpeg print the time only. The date occupies a lot of horizontal screen estate which is inconvenient for manual review and largely redundant anyway. The only corner case would be a long-running process where ffmpeg doesn't print a single log line for a whole day - in that case, the time-only output would become ambiguous.. Thanks sw _______________________________________________ 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:[~2025-02-07 5:05 UTC|newest] Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-24 19:37 [FFmpeg-devel] [PATCH " ffmpegagent 2022-08-24 19:37 ` [FFmpeg-devel] [PATCH 1/3] avutil/log: support logging of date and timing information softworkz 2022-08-24 19:37 ` [FFmpeg-devel] [PATCH 2/3] fftools/opt_common: add timing and datetiming log flags softworkz 2022-08-24 19:37 ` [FFmpeg-devel] [PATCH 3/3] doc/fftools-common-opts: document log timing flags softworkz 2022-12-12 23:10 ` [FFmpeg-devel] [PATCH 0/3] Add option to log timing Soft Works 2025-01-30 3:53 ` [FFmpeg-devel] [PATCH v2 " ffmpegagent 2025-01-30 3:53 ` [FFmpeg-devel] [PATCH v2 1/3] avutil/log: support logging of date and timing information softworkz 2025-01-30 3:53 ` [FFmpeg-devel] [PATCH v2 2/3] fftools/opt_common: add timing and datetiming log flags softworkz 2025-02-02 1:13 ` Michael Niedermayer 2025-02-02 1:38 ` Soft Works 2025-01-30 3:53 ` [FFmpeg-devel] [PATCH v2 3/3] doc/fftools-common-opts: document log timing flags softworkz 2025-02-07 1:26 ` [FFmpeg-devel] [PATCH v3 0/3] Add option to log timing ffmpegagent 2025-02-07 1:26 ` [FFmpeg-devel] [PATCH v3 1/3] avutil/log: support logging of date and timing information softworkz 2025-02-07 1:26 ` [FFmpeg-devel] [PATCH v3 2/3] fftools/opt_common: add timing and datetiming log flags softworkz 2025-02-07 1:26 ` [FFmpeg-devel] [PATCH v3 3/3] doc/fftools-common-opts: document log timing flags softworkz 2025-02-07 3:58 ` [FFmpeg-devel] [PATCH v3 0/3] Add option to log timing Marth64 2025-02-07 4:37 ` Soft Works 2025-02-07 4:47 ` Marth64 2025-02-07 4:53 ` Marth64 2025-02-07 5:05 ` Soft Works [this message] 2025-02-07 5:15 ` Marth64 2025-02-07 6:27 ` [FFmpeg-devel] [PATCH v4 " ffmpegagent 2025-02-07 6:27 ` [FFmpeg-devel] [PATCH v4 1/3] avutil/log: support logging of date and timing information softworkz 2025-02-07 6:27 ` [FFmpeg-devel] [PATCH v4 2/3] fftools/opt_common: add timing and datetiming log flags softworkz 2025-02-07 6:46 ` epirat07 2025-02-07 6:54 ` Soft Works 2025-02-07 6:27 ` [FFmpeg-devel] [PATCH v4 3/3] doc/fftools-common-opts: document log timing flags softworkz 2025-02-07 7:57 ` [FFmpeg-devel] [PATCH v5 0/3] Add option to log timing ffmpegagent 2025-02-07 7:57 ` [FFmpeg-devel] [PATCH v5 1/3] avutil/log: support logging of date and time information softworkz 2025-02-07 7:57 ` [FFmpeg-devel] [PATCH v5 2/3] fftools/opt_common: add time and datetime log flags softworkz 2025-02-07 10:42 ` Tobias Rapp 2025-02-07 11:27 ` Soft Works 2025-02-07 12:03 ` Soft Works 2025-02-07 13:21 ` Tobias Rapp 2025-02-07 14:19 ` Soft Works 2025-02-07 7:57 ` [FFmpeg-devel] [PATCH v5 3/3] doc/fftools-common-opts: document log timing flags softworkz 2025-02-07 14:34 ` [FFmpeg-devel] [PATCH v6 0/3] Add option to log timing ffmpegagent 2025-02-07 14:34 ` [FFmpeg-devel] [PATCH v6 1/3] avutil/log: support logging of date and time information softworkz 2025-02-07 14:34 ` [FFmpeg-devel] [PATCH v6 2/3] fftools/opt_common: add time and datetime log flags softworkz 2025-02-07 14:34 ` [FFmpeg-devel] [PATCH v6 3/3] doc/fftools-common-opts: document log timing flags softworkz 2025-02-07 15:57 ` [FFmpeg-devel] [PATCH v6 0/3] Add option to log timing Tobias Rapp
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=DM8P223MB03657509ADCC56965A35DC2EBAF12@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM \ --to=softworkz-at-hotmail.com@ffmpeg.org \ --cc=ffmpeg-devel@ffmpeg.org \ --cc=marth64@proxyid.net \ --cc=michael@niedermayer.cc \ /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