> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-boun...@ffmpeg.org> On Behalf Of
> Michael Niedermayer
> Sent: Freitag, 14. März 2025 01:28
> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH] avcodec/vlc: Reduce debug logging
>
> Hi
>
> On Wed, Mar 12, 2025 at 03:48:20AM +0000, softworkz wrote:
> > From: softworkz <softwo...@hotmail.com>
> >
> > Signed-off-by: softworkz <softwo...@hotmail.com>
> > ---
> > avcodec/vlc: Reduce debug logging
> >
> > It made it hardly possible to enable debug logging for viewing
> other log
> > lines due to the excessive output created by this.
> >
> > Published-As: https://github.com/ffstaging/FFmpeg/releases/tag/pr-
> ffstaging-60%2Fsoftworkz%2Fsubmit_vlclogging-v1
> > Fetch-It-Via: git fetch https://github.com/ffstaging/FFmpeg pr-
> ffstaging-60/softworkz/submit_vlclogging-v1
> > Pull-Request: https://github.com/ffstaging/FFmpeg/pull/60
> >
> > libavcodec/vlc.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
>
> will apply
Thanks!
> btw, speaking of excessive output,
> valgrind_backtrace (which is enabled by default when optimizations are
> disabled)
Only when you have it installed I suppose..?
For me, it's 0 in config.h even after ./configure --disable-optimizations
> is also a feature that is rarely useful but very annoying noise wise
> (just saying in case anyone wants to reduce noise in general)
Might make sense to require it to enable explicitly.
What I meant by excessive in that case is that it exhausted the console buffer
so that I couldn't even scroll back to ffmpeg startup and it took several
seconds to react to break (q was hardly working at all), so it was an extreme
case.
Thank you
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-requ...@ffmpeg.org with subject "unsubscribe".
