Closed Phaiax closed 2 years ago
Yes it's probably time to deprecate the input raspicam plugin, the raspicam can be used via v4l2 and the uvc plugin now anyway. This mjpg-streamer repo is probably still the best one for most people because it's had a fair few tweaks and patches to the uvc plugin.
The raspicam plugin should automatically not be built if the headers are lacking. So hopefully we do not need to do anything for mjpg-streamer to run on Bullseye.
Maybe we need a libcamera plugin... But tbh I think mjpg-streamer only really has legacy use now. Most browsers support streaming h264 or even AV1 now which has clear advantages.
So I'd probably want to work on a project to stream those instead.
To clarify, switch to using the input_uvc plugin with the raspicam v4l2 driver on Bullseye and things should 'just work'.
Just commenting here for other people's benefit. You can disable the new libcamera stack and re-enable the V4L2 driver by following the instructions here: https://forums.raspberrypi.com/viewtopic.php?p=1935591&sid=b0c61887cb4c3352cae9596e9fb6bb88#p1935591
Then you can run mjpg-streamer with the following command:
export LD_LIBRARY_PATH=. | ./mjpg_streamer -o "output_http.so -w ./www" -i "input_uvc.so"
Hi.
I failed to get mjpg-streamer running after an upgrade to rasbian bullseye. Only then I found this information :
Also all the videocore tools don't live in
/opt/vc
anymore. They are integrated into the/usr
structure.Maybe this info should be added to the readme? I'll try to find an alternative and post an update here afterwards.
Phaiax