|
From: Ed K. <ed...@ka...> - 2021-11-15 12:42:36
|
Hi Tosiara, The motion log file is attached as requested. The only way i can get motion to work is to use 640x480 as the width/height. [1] is a picture, taken with libcamera-still, that shows the complete FOV [2] is a picture from motion, which only has a small FOV. Do you have a raspberry pi (3B+) with a V2 camera module? (2B should be good too) If you do, you could download the official raspberry pi OS from [3] and use a fresh SD card to try the new libcamera setup with motion. [1] http://www.kapitein.org/pictures/libcamera-still.jpg [2] http://www.kapitein.org/pictures/motion.jpg [3] https://downloads.raspberrypi.org/raspios_lite_armhf/images/raspios_lite_armhf-2021-11-08/2021-10-30-raspios-bullseye-armhf-lite.zip Kind regards, Ed On 11/15/21 12:45 PM, tosiara wrote: > Can you attach the full motion log with -d 9 when running your Pi > camera? On Mon, Nov 15, 2021 at 1:10 PM Ed Kapitein <ed...@ka...> > wrote: >> Hi Tosiara, The new raspberry pi OS ( bullseye ) uses libcamera and >> that is very different from the old way of using the camera. The FOV >> is the Field Of View and in the attached pictures you can see that >> motion is using a small part of the picture, and i can not get the >> complete FOV with motion. It would be nice if someone with knowledge >> of motion and libcamera, could make a (per camera) table of working >> settings something like this: >> +------------------------------------------------------------------------------------+ >> | raspberry pi camera module V2 NOIR | >> +--------------+-------------------------------------+-------------------------------+ >> | device |v4l2-ctl |motion.conf | >> +--------------+-------------------------------------+-------------------------------+ >> | /dev/video0 |set-fmt-video=width=1640,height=1232 >> |with=1640,height=1232,input=-1 | | /dev/video14 >> |set-fmt-video=width=640,height=480 |with=640,height=480,input=8 | >> +--------------+-------------------------------------+-------------------------------+ >> I assume that many wildlife camera's are build around motion and will >> start to fail if people upgrade to the new raspberry pi OS Kind >> regards, Ed On 11/15/21 11:00 AM, tosiara wrote: >>> Maybe it is not motion, bet Raspberry changed something in the new >>> OS image I don't know what is FOV on pi camera and how motion can >>> control it On Sun, Nov 14, 2021 at 6:32 PM Ed Kapitein via >>> Motion-user <mot...@li...> wrote: >>>> Hi, I own a raspberry pi 3B+ and a camera v2 NOIR and use motion. >>>> After upgrading to bullseye i had and have some difficulties to use >>>> motion. For me it does not work "out of the box" I needed to rename >>>> the existing cameraX-dist.conf to something else then .conf to get >>>> motion working. And when using /dev/video0 the FOV is smaller than >>>> it should be. I assume the documentation needs an update. Motion >>>> *is* working, but i assume that with libcamera there is need of >>>> working examples of config files with the available raspberry pi >>>> camera's. Could someone please add a dedicated section for the >>>> raspberry pi and the well known camera's, so we can continue to use >>>> motion with the new setup? Let me know if i can test anything! Kind >>>> regards, Ed _______________________________________________ >>>> Motion-user mailing list Mot...@li... >>>> https://lists.sourceforge.net/lists/listinfo/motion-user >>>> https://motion-project.github.io/ Unsubscribe: >>>> https://lists.sourceforge.net/lists/options/motion-user |