On Mon, Mar 11, 2019 at 1:00 AM Carl Zwanzig <[email protected]> wrote: (What have you already tried?) As of now, I'm passing every decoded frame to OpenCV to perform some image analysis (like dissimilarity between present and the past frame), but this method doesn't work accurately and also time-consuming.
"glitch" can mean lots of things, and a decoding failure is only one of > them > and better to call it what it is (i.e head-switching noise from an analog > source can also be called a glitch, as could a dropped frame). Yes, it caused due to lots of things, but most of the time glitches occur at a tiny part of the frame (macroblock). In this case, it looks like a transmission/data error or dropped packet(s). > Can a frame-based filter even look for that? You're kind of getting into > Automatic Content Recognition, which gets tricky and isn't a job for the > command line utils. > I'm using FFmpeg C API not the cmd util. There is a freezedetect filter, but that may not be what you want. > it's only used to detect contiguous static frames. I think you better off looking at the log messages for decoder errors. > how to dump log of decoder.? > z! > _______________________________________________ > ffmpeg-user mailing list > [email protected] > https://ffmpeg.org/mailman/listinfo/ffmpeg-user > > To unsubscribe, visit link above, or email > [email protected] with subject "unsubscribe". _______________________________________________ ffmpeg-user mailing list [email protected] https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email [email protected] with subject "unsubscribe".
