Motion fails on RaspberryPi OS64 Bullseye, libcamera with libcamerify

[martin762]

Hello,
when prefixed with the libcamerify command, Motion is behaving well on a Bullseye armhf (32bit) PiOS, with the new libcamera s/w, It is failing on a vanilla Pi OS64 Bullseye (latest release Motion, and Bullseye up to date). Is this a known issue on Pi OS64? Might compiling the Motion master make a difference?

I appreciate that this may be a libcamera or RaspberryPI OS issue rather than Motion.
Thank you for any feedback
Regards
Martin Green

[martin762]

Expanding on my question / comment above. I have just tried to compile the master (excluding mmal) and get the same. My PI is a 4B 4M. The offending lines from the logs are:
[1:ml1] [NTC] [VID] vid_start: Opening V4L2 device
[1:ml1] [NTC] [VID] v4l2_device_open: Using videodevice /dev/video0 and input -1
[1:ml1] [ERR] [VID] v4l2_device_capability: Not a V4L2 device?
[1:ml1] [ERR] [VID] vid_start: V4L2 device failed to open

I can confirm that this is different to the logs for motion without libcamerify.

Is this pointing to libcamerify not correctly providing the compatibility layer?
Martin