MichaIng

Can you please share the service logs: ```sh journalctl -u motioneye ```

You need to select a different "Movie format" in the settings. AFAIK H.264/OMX one is only supported with the Raspberry Pi FFmpeg build. Would actually make sense to check for...

There should be two frame rates shown in motionEye, one is the intended frame rate and one is what finally appears at the frontend. Are both reported at close to...

Okay, then I'm not sure whether it's the camera itself providing a new picture only at 5 FPS while it is possible to grab (then repeating) pictures at 30 FPS....

Which motionEye version are you using, v0.42.1 or v0.43.0 dev version already?

Hmm those packages should have been installed with ffmpeg already. What does the following say? ```sh apt policy libavcodec58 dpkg -l | grep libavcodec ``` Probably volumio has another conflicting...

The cameras I deal with are shown as `/dev/video*`. Can you check whether they are listed here: ```sh v4l2-ctl --list-devices ``` It may be related to RPi MMAL camera detection...

I'm not sure how such infrared camera is commonly provided. E.g. based on `v4l2-ctl --list-devices` output it seems like `/dev/media1` can also be obtained from `/dev/video0`, but `/dev/media0` is associated...

Ah right, makes sense that it doesn't work as MMAL with modern camera stack. I'm wondering why the cameras are spread across so many `/dev` devices. CLI can only access...

Looks like we should add the device path to the camera name, for such cases where multiple devices have the same name, or one camera provides multiple devices for whatever...