On Fri, 15 Aug 2025 11:43:27 +0200, Jan Stary <h...@stare.cz> wrote: > > The only encoding supported in these by video(1) seems to be > > encodings: yuy2 > > but ffplay also reports mjpeg: > > Compressed : mjpeg : MJPEG : > 640x480 1920x1080 1280x960 1280x720 800x600 352x288 320x240 > > Raw : yuyv422 : YUYV : > 640x480 1920x1080 1280x960 1280x720 800x600 352x288 320x240 >
Yeah, our video is very limited, and I usally use ffplay to test. > Can you please confirm that the ffmpeg command above > is the ways to make the camera produce mjpeg output > (as opposed to converting to mjpeg via libavformat)? > Yes, this command looks correct. ffplay -input_format h264 -i /dev/video1 > All of these seem to work fine (deails below) except > a framerate confusion for mjpeg, which I suspect is a ffmpeg problem > not related to this: sometimes it will play back the video using > a framerate different from recording (such as 25 vs 20). > Interesting, I had reported to ffmpeg upstream an issue with my Elgato webcam: when I stream with 4K 60fps, I have "frozen" picture. Quite possible that root cause is mjpeg and that ffmpeg uses CPU to decode it, if your CPU isn't very fast, it may be an issue. > Log below, with the wordy ffmpeg headers stripped. > Thanks for confirming that I haven't broke anything. I was sure about h264 patch, but "performance optimization" had its issues. -- wbr, Kirill
