libcamerify on 32 bit OS
#1944
Replies: 5 comments 3 replies
-
|
Hi @Mr-Dave I'm having a heck of time getting motion to work on a RPi Zero W running Trixie Lite 32-bit. I wrote about it in the Pi forums here I've tried to follow the instructions to build from source on my RPi Zero W running Trixie Lite 32-bit, using the Build Guide here; running Running Also, when I try to run |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
The issue is reported upstream here I've compiled and tested the master branch on my PI Zero W. My guess is that there is possibly a missing dependency causing the problem with Check for everything being up to date and clean with a |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Thanks for your reply @Mr-Dave Is it still necessary to start motion with libcamerify? I don't think so, right? I've copied /usr/local/var/lib/motion/motion-dist.conf to /usr/local/var/lib/motion/motion.conf When I start motion with; I see; And ~/motion.log contains; What could the problem be? Here is my motion.conf Here is camera1.conf; |
Beta Was this translation helpful? Give feedback.
-
|
You do not need to use Instead you use the configuration options of (If you need specific libcamera parameters outside of the defaults, you'd specify them using |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Ok, got it.... I'm not using libcamera. So, I've set v4l2_device So, then why am I getting these errors? And importantly, how do I fix it? |
Beta Was this translation helpful? Give feedback.
-
I'm not sure you are understanding libcamera, libcamerify, the v4l2 devices and how it all interacts with the PI camera. The traditional method to use the PI camera was to use the The new method that is only available via building Motion from source is by specifying the |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Oooooohhh my.... I'm a dork. I had definitely conflated a couple things there. I've adjusted motion.conf to;
|
Beta Was this translation helpful? Give feedback.
-
|
np. Please make sure to also update your discussion/comments in the PI forum so others looking there can know the resolution/process. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Just a FYI to everyone that libcamerify is not currently functional when used on a 32 bit OS. It has been raised upstream to the libcamera team as a bug but there is not currently an ETA for when this would get resolved.
This means that for platforms that do not support a 64 bit OS (e.g. Pi 1, Pi 2, Pi Zero, Pi Zero W), the historical method for using the Pi camera and Motion will not work. For these platforms, Motion will need to built from source off of the master branch to get version 5.0+ and use the libcam options.
Beta Was this translation helpful? Give feedback.
All reactions