On Sat, Oct 07, 2023 at 01:33:48PM +0200, Jan Stary wrote: > On Oct 07 13:30:50, dco...@gmail.com wrote: > > On Sat, Oct 7, 2023 at 1:26???PM Jan Stary <h...@stare.cz> wrote: > > > > > > On Oct 07 07:08:21, kolip...@exoticsilicon.com wrote: > > > > On Sat, Oct 07, 2023 at 08:51:36AM +0000, Comte wrote: > > > > > The webcam seems well detected but no image is displayed... > > > > > > To be sure: you have kern.audio.record=1, right? > > > > kern.video.record, not kern.audio.record. > > ECOFFEE, sorry
His original mail said that he does have it enabled: On Sat, Oct 07, 2023 at 08:51:36AM +0000, Comte wrote: > # sysctl kern.video.record > kern.video.record=1 I'm pretty sure that the issue is that he is invoking ffmpeg with switches that expect mjpeg data from the camera, whereas the camera actually provides raw YUV pixel data. On Sat, Oct 07, 2023 at 08:51:36AM +0000, Comte wrote: > # video -q -f /dev/video0 > video device /dev/video0: > encodings: yuy2 > frame sizes (width x height, in pixels) and rates (in frames per second): > 320x180: 30 > 320x240: 30 > 352x288: 30 > 424x240: 30 > 640x360: 30 > 640x480: 30 > 848x480: 20 > 960x540: 15 > 1280x720: 10 > 1920x1080: 5 These combinations of resolutions and framerates are typical of the constraints of USB-2 bandwidth streaming YUV data. If it really was mjpeg, I'd expect 1920x1080 to be available at 30fps.
