From: Soft Works <softworkz-at-hotmail.com@ffmpeg.org> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH] avcodec/vlc: Reduce debug logging Date: Fri, 14 Mar 2025 03:46:35 +0000 Message-ID: <DM8P223MB03650DE6C1FF514618A91A95BAD22@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw) In-Reply-To: <20250314002823.GF4991@pb2> > -----Original Message----- > From: ffmpeg-devel <ffmpeg-devel-bounces@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 <softworkz@hotmail.com> > > > > Signed-off-by: softworkz <softworkz@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-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2025-03-14 3:46 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-03-12 3:48 softworkz 2025-03-14 0:28 ` Michael Niedermayer 2025-03-14 3:46 ` Soft Works [this message] 2025-03-15 1:03 ` Michael Niedermayer
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=DM8P223MB03650DE6C1FF514618A91A95BAD22@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM \ --to=softworkz-at-hotmail.com@ffmpeg.org \ --cc=ffmpeg-devel@ffmpeg.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel This inbox may be cloned and mirrored by anyone: git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \ ffmpegdev@gitmailbox.com public-inbox-index ffmpegdev Example config snippet for mirrors. AGPL code for this site: git clone https://public-inbox.org/public-inbox.git