On Fri, Feb 07, 2025 at 04:57:55PM +0100, Tobias Rapp wrote:
> On 07/02/2025 15:34, ffmpegagent wrote:
> 
> > This commit adds two logging flags: 'time' and 'datetime'.
> > 
> > Usage:
> > 
> > ffmpeg -loglevel +time
> > 
> > or
> > 
> > ffmpeg -loglevel +datetime
> > 
> > Update V1
> > 
> >   * Fix merge conflicts
> > 
> > Update V2
> > 
> >   * Rebased
> > 
> > Update V3
> > 
> >   * Fix print timing on exit (as reported by Michael Niedermayer)
> > 
> > Update V4
> > 
> >   * Rename variable
> >   * Rename flags to time and datetime (as suggested by Marth64)
> > 
> > Update V5
> > 
> >   * Fix commit message (as noted by epirat07)
> > 
> > Update V6
> > 
> >   * Handle empty quiet messages in log.c rather than clearing log flags in
> >     ffmpeg.c (as suggested by Tobias Rapp)
> > 
> > softworkz (3):
> >    avutil/log: support logging of date and time information
> >    fftools/opt_common: add time and datetime log flags
> >    doc/fftools-common-opts: document log timing flags
> > 
> >   doc/APIchanges               |  3 +++
> >   doc/fftools-common-opts.texi |  4 ++++
> >   fftools/opt_common.c         | 12 ++++++++++++
> >   libavutil/log.c              | 32 +++++++++++++++++++++++++++++---
> >   libavutil/log.h              | 10 ++++++++++
> >   libavutil/version.h          |  2 +-
> >   6 files changed, 59 insertions(+), 4 deletions(-)
> > 
> > [...]
> 
> Looks fine from my side regarding the handling of AV_LOG_QUIET.

will apply patchset

thx

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Awnsering whenever a program halts or runs forever is
On a turing machine, in general impossible (turings halting problem).
On any real computer, always possible as a real computer has a finite number
of states N, and will either halt in less than N cycles or never halt.