Opened 8 months ago

Last modified 8 months ago

#10922 reopened enhancement

"ssim", "psnr" output should be categorized "warning"?

Reported by: MasterQuestionable Owned by:
Priority: normal Component: avfilter
Version: unspecified Keywords: loglevel ssim psnr
Cc: MasterQuestionable Blocked By:
Blocking: Reproduced by developer: no
Analyzed by developer: no

Description (last modified by MasterQuestionable)

(for less verbose output in CLI)

Valid use case:
ffmpeg -hide_banner -nostdin -v warning -i ${in0} -i ${in1} -lavfi "ssim; [0][1]psnr" -f null -

This currently gives nothing at all... for which cataloged "info".

Change History (5)

comment:1 by Cigaes, 8 months ago

Resolution: invalid
Status: newclosed

Log levels are not random words, they have meaning, warning means that something went wrong enough to warrant the attention of the operator but not enough to stop the process. The normal result of a filter cannot be considered to be something that went wrong.

comment:2 by MasterQuestionable, 8 months ago

Resolution: invalid
Status: closedreopened

Semantically, yes.
But in the aforementioned case: to get SSIM and PSNR without all the verbosity by "info":
There lacks an easy way.

comment:3 by Cigaes, 8 months ago

Resolution: invalid
Status: reopenedclosed

Then open a ticket requesting an properly designed way of extracting information from the filters. Or read the doc and see that there is already one.

comment:4 by MasterQuestionable, 8 months ago

Resolution: invalid
Status: closedreopened
Summary: "ssim", "psnr" output should be categorized "warning""ssim", "psnr" output should be categorized "warning"?

After more checking I noticed the "stats_file".
But it doesn't appear quite suitable for the usage.

And its format appears somewhat inconsistent with the info message.
And there seems to be documentation issues: inconsistency between the doc and help.

Modifying existing ticket shall be more effective. (better aggregation)

comment:5 by MasterQuestionable, 8 months ago

Description: modified (diff)

What are the potential caveats of doing so?
Is there significant CLI usage that causes abort on warning meanwhile using the named filters?

Note: See TracTickets for help on using tickets.