Feb 21, 2024, 15:43 by jamr...@gmail.com:
> The output of TX is extremely verbose and makes it harder to find other debug
> log messages, so only print it at trace level.
>
> Signed-off-by: James Almer <jamr...@gmail.com>
> ---
> libavutil/tx.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/libavutil/tx.c b/libavutil/tx.c
> index f991618b4b..eefb3e2ac7 100644
> --- a/libavutil/tx.c
> +++ b/libavutil/tx.c
> @@ -643,7 +643,7 @@ static void print_cd_info(const FFTXCodelet *cd, int
> prio, int len, int print_pr
> if (print_prio)
> av_bprintf(&bp, ", prio: %i", prio);
>
> - av_log(NULL, AV_LOG_DEBUG, "%s\n", bp.str);
> + av_log(NULL, AV_LOG_TRACE, "%s\n", bp.str);
> }
>
> static void print_tx_structure(AVTXContext *s, int depth)
> @@ -651,7 +651,7 @@ static void print_tx_structure(AVTXContext *s, int depth)
> const FFTXCodelet *cd = s->cd_self;
>
> for (int i = 0; i <= depth; i++)
> - av_log(NULL, AV_LOG_DEBUG, " ");
> + av_log(NULL, AV_LOG_TRACE, " ");
>
> print_cd_info(cd, cd->prio, s->len, 0);
>
> @@ -816,10 +816,10 @@ av_cold int ff_tx_init_subtx(AVTXContext *s, enum
> AVTXType type,
> AV_QSORT(cd_matches, nb_cd_matches, TXCodeletMatch, cmp_matches);
>
> #if !CONFIG_SMALL
> - av_log(NULL, AV_LOG_DEBUG, "%s\n", bp.str);
> + av_log(NULL, AV_LOG_TRACE, "%s\n", bp.str);
>
> for (int i = 0; i < nb_cd_matches; i++) {
> - av_log(NULL, AV_LOG_DEBUG, " %i: ", i + 1);
> + av_log(NULL, AV_LOG_TRACE, " %i: ", i + 1);
> print_cd_info(cd_matches[i].cd, cd_matches[i].prio, 0, 1);
> }
> #endif
> @@ -929,7 +929,7 @@ av_cold int av_tx_init(AVTXContext **ctx, av_tx_fn *tx,
> enum AVTXType type,
> *tx = tmp.fn[0];
>
> #if !CONFIG_SMALL
> - av_log(NULL, AV_LOG_DEBUG, "Transform tree:\n");
> + av_log(NULL, AV_LOG_TRACE, "Transform tree:\n");
> print_tx_structure(*ctx, 0);
> #endif
>
It's a chunk of few dozen lines, I don't think it's spammy enough for trace.
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
