Send Motion-user mailing list submissions to
motion-user@lists.sourceforge.net
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/motion-user
or, via email, send a message with subject or body 'help' to
motion-user-requ...@lists.sourceforge.net
You can reach the person managing the list at
motion-user-ow...@lists.sourceforge.net
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Motion-user digest..."
Today's Topics:
1. Re: raspberry pi libcamera motion bulseye (tosiara)
2. Re: raspberry pi libcamera motion bulseye (Ed Kapitein)
----------------------------------------------------------------------
Message: 1
Date: Tue, 16 Nov 2021 09:03:56 +0200
From: tosiara <tosi...@gmail.com>
To: Motion discussion list <motion-user@lists.sourceforge.net>
Subject: Re: [Motion-user] raspberry pi libcamera motion bulseye
Message-ID:
<CACHTdwRCE2y3Umzz95VTfgDVmkOus=gtvgbgtodm+gdwpy3...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Could you specify BA81 3280x2464 pixel format, run motion with -d 9
and send the log?
I'd like to see the "non-working" log
On Mon, Nov 15, 2021 at 8:59 PM Ed Kapitein via Motion-user
<motion-user@lists.sourceforge.net> wrote:
>
> Some of the observations i made are described in the known issues
> section [1], so i will
>
> try to contact the libcamera team.
>
>
> Kind regards,
>
> Ed
>
>
> [1]
> https://www.raspberrypi.com/documentation/accessories/camera.html#known-issues
>
> On 11/15/21 6:39 PM, Ed Kapitein via Motion-user wrote:
> > Hi,
> >
> > sudo v4l2-ctl --list-formats-ex -d /dev/video0
> > ioctl: VIDIOC_ENUM_FMT
> > Type: Video Capture
> >
> > [0]: 'pBAA' (10-bit Bayer BGBG/GRGR Packed)
> > Size: Discrete 3280x2464
> > Size: Discrete 1920x1080
> > Size: Discrete 1640x1232
> > Size: Discrete 640x480
> > [1]: 'BG10' (10-bit Bayer BGBG/GRGR)
> > Size: Discrete 3280x2464
> > Size: Discrete 1920x1080
> > Size: Discrete 1640x1232
> > Size: Discrete 640x480
> > [2]: 'BA81' (8-bit Bayer BGBG/GRGR)
> > Size: Discrete 3280x2464
> > Size: Discrete 1920x1080
> > Size: Discrete 1640x1232
> > Size: Discrete 640x480
> >
> > But only BA81 640x480 is working. ( i did try all the other
> > resolutions )
> >
> > So is it possible that something has changed and that motion is not
> > selecting the right resolution?
> >
> > Some of the other resolutions do not *fail*, but the image is just a
> > bunch of stripes like a monitor out of sync.
> >
> > I did try setting the format with sudo v4l2-ctl --device /dev/video0
> > --set-fmt-video=width=......
> >
> > and use the same setting for width and height in motion.conf, but to
> > no avail.
> >
> > Kind regards,
> >
> > Ed
> >
> >
> > On 11/15/21 4:39 PM, tosiara wrote:
> >> Also, you can check which formats are available:
> >>
> >> v4l2-ctl --list-formats-ex -d /dev/video0
> >>
> >> Maybe there are other resolutions that would get wider picture from
> >> the sensor
> >>
> >>
> >> On Mon, Nov 15, 2021 at 4:59 PM tosiara <tosi...@gmail.com> wrote:
> >>>> Before the upgrade to bullseye i also used 640x480 and got the
> >>>> whole FOV.
> >>> Unfortunately, there is nothing motion can do if this is the FOV that
> >>> camera provides over V4L2 interface (since MPlayer shows the same)
> >>>
> >>> You could ask Raspberry community, maybe someone came across this
> >>> issue and has a fix
> >>>
> >>> On Mon, Nov 15, 2021 at 3:58 PM Ed Kapitein <e...@kapitein.org> wrote:
> >>>> Yes, mplayer plays it just fine:
> >>>>
> >>>> Movie-Aspect is undefined - no prescaling applied.
> >>>> VO: [xv] 640x480 => 640x480 Planar YV12
> >>>>
> >>>> and is has the same FOV as the motion picture. [1]
> >>>>
> >>>> Before the upgrade to bullseye i also used 640x480 and got the
> >>>> whole FOV.
> >>>>
> >>>> [3] is a video clips made with the old setup.
> >>>>
> >>>> More info on FOV and binning (which i think is happening) is on [1]
> >>>>
> >>>>
> >>>> Kind regards,
> >>>>
> >>>> Ed
> >>>>
> >>>> [1] http://www.kapitein.org/pictures/motion.jpg
> >>>>
> >>>> [2] https://picamera.readthedocs.io/en/release-1.12/fov.html
> >>>>
> >>>> [3] http://www.kapitein.org/pictures/04-20211028034157.mp4
> >>>>
> >>>>
> >>>> PS
> >>>>
> >>>> Motion gives me a signal when the mouse is caught, so we can
> >>>> release it
> >>>> into the wild.
> >>>>
> >>>> No animals where harmed during the recording of this clip ;-)
> >>>>
> >>>>
> >>>> On 11/15/21 1:52 PM, tosiara wrote:
> >>>>> Are you able to play 640x480 mode in ffplay or vlc? Does it give you
> >>>>> the same FOV as motion or different?
> >>>>>
> >>>>> Which resolution did you use in motion prior to upgrade to bullseye?
> >>>>>
> >>>>> On Mon, Nov 15, 2021 at 2:42 PM Ed Kapitein <e...@kapitein.org> wrote:
> >>>>>> 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
> >>>>>>
> >>>>>>
> >>>>>>> <SNIP><
> >
> >
> > _______________________________________________
> > Motion-user mailing list
> > Motion-user@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/motion-user
> > https://motion-project.github.io/
> >
> > Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
>
>
> _______________________________________________
> Motion-user mailing list
> Motion-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/motion-user
> https://motion-project.github.io/
>
> Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
------------------------------
Message: 2
Date: Tue, 16 Nov 2021 09:40:18 +0100
From: Ed Kapitein <e...@kapitein.org>
To: tosiara <tosi...@gmail.com>, Motion discussion list
<motion-user@lists.sourceforge.net>
Subject: Re: [Motion-user] raspberry pi libcamera motion bulseye
Message-ID: <f8a270cd-089b-66a1-e026-c92f90f87...@kapitein.org>
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Hi Tosiara,
Thanks for your support so far, i appreciate it!
Yesterday i found out that after a clean reboot *none* of the
resolutions are working.
So the logs i attached are after a clean reboot and motion is not
working with any of the resolutions.
However, if i take a picture with libcamera-still, and then start
motion, motion will work with a 640x480 resolution, although the image
is cropped. (to small FoV)
So this leads me to believe there are two problems going on here:
-1 libcamera crops the image at certain resolutions, as described in [1]
-2 motion is not initializing the camera correctly, it only works after
taking a picture, which initializes the camera module.
Kind regards,
Ed
[1]
https://www.raspberrypi.com/documentation/accessories/camera.html#known-issues
On 11/16/21 8:03 AM, tosiara wrote:
> Could you specify BA81 3280x2464 pixel format, run motion with -d 9
> and send the log? I'd like to see the "non-working" log On Mon, Nov
> 15, 2021 at 8:59 PM Ed Kapitein via Motion-user
> <motion-user@lists.sourceforge.net> wrote:
>> Some of the observations i made are described in the known issues
>> >< SNIP ><
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 640x480.log
Type: text/x-log
Size: 28867 bytes
Desc: not available
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 3280x2464.log
Type: text/x-log
Size: 39278 bytes
Desc: not available
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 1920x1080.log
Type: text/x-log
Size: 39665 bytes
Desc: not available
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 1640x1232.log
Type: text/x-log
Size: 28641 bytes
Desc: not available
------------------------------
------------------------------
Subject: Digest Footer
_______________________________________________
Motion-user mailing list
Motion-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/motion-user
------------------------------
End of Motion-user Digest, Vol 185, Issue 15
********************************************
