> -----Original Message----- > From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf Of Gyan > Sent: Wednesday, July 10, 2019 7:33 AM > To: ffmpeg-devel@ffmpeg.org > Subject: Re: [FFmpeg-devel] [PATCH] avfilter: add rawdump filter > > > > On 10-07-2019 07:51 PM, Eoff, Ullysses A wrote: > >> -----Original Message----- > >> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf Of > >> Hendrik Leppkes > >> Sent: Wednesday, July 10, 2019 4:13 AM > >> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> > >> Subject: Re: [FFmpeg-devel] [PATCH] avfilter: add rawdump filter > >> > >> ... > >> I believe using -reinit_filter 0 with ffmpeg can achieve such a > >> result., as long as you make sure all filtering done (preferably none) > >> is capable of on-the-fly changes. > >> > > Excellent! I wouldn't have thought to try -reinit_filter 0 for such a > > scenario. I > > just tried it and it achieves the exact result we're looking for. But it's > > unfortunate > > that it generates a warning message for every frame processed. Is there a > > simple > > way to silence that message, yet still get other verbose logging (I don't > > want to > > flood our automation logs)? > > No. You'll have to upgrade the level in libavfilter/buffersrc.c >
I see. Would anyone object if I sent a patch to upgrade the level to AV_LOG_DEBUG? > Gyan > _______________________________________________ > 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". _______________________________________________ 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".
