I meant obscure in the context of running ffmpeg CLI in a short lived
(<1 day) session for the average user.
Nonetheless I am good. Thanks!
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubsc
> -Original Message-
> From: Marth64
> Sent: Friday, February 7, 2025 5:47 AM
> To: Soft Works
> Cc: FFmpeg development discussions and patches de...@ffmpeg.org>; Michael Niedermayer ; Soft
> Works
> Subject: Re: [FFmpeg-devel] [PATCH v3 0/3] Add option to lo
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 +
> 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.
> 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 w
> -Original Message-
> From: Marth64
> Sent: Friday, February 7, 2025 4:58 AM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Cc: Michael Niedermayer ; softworkz
> ; Soft Works hotmail@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATC
It works good. First pass thoughts:
1- Rename `timeBuf` -> `bp_time`, in this way it follows snake case
convention and conveys clearly that the parameter is an `AVBPrint`
2- Option switch: +datetime and +time feels lighter/easier (vs. -ing)
3- Term color: the space after the time keeps the backgr
