Re: [Motion-user] raspberry pi libcamera motion bulseye

[tosiara <to...@gm...>]

Your log now is different:

Was:

[1:ml1] [NTC] [VID] [Nov 15 13:27:34] v4l2_pixfmt_select: Supported palettes:
[1:ml1] [NTC] [VID] [Nov 15 13:27:34] v4l2_pixfmt_select: (0) pBAA
(10-bit Bayer BGBG/GRGR Packed)
[1:ml1] [DBG] [VID] [Nov 15 13:27:34] v4l2_pixfmt_select: 0 - 10-bit
Bayer BGBG/GRGR Packed (compressed : 0) (0x41414270)
[1:ml1] [NTC] [VID] [Nov 15 13:27:34] v4l2_pixfmt_select: (1) BG10
(10-bit Bayer BGBG/GRGR)
[1:ml1] [DBG] [VID] [Nov 15 13:27:34] v4l2_pixfmt_select: 1 - 10-bit
Bayer BGBG/GRGR (compressed : 0) (0x30314742)
[1:ml1] [NTC] [VID] [Nov 15 13:27:34] v4l2_pixfmt_select: (2) BA81
(8-bit Bayer BGBG/GRGR)
[1:ml1] [DBG] [VID] [Nov 15 13:27:34] v4l2_pixfmt_select: 2 - 8-bit
Bayer BGBG/GRGR (compressed : 0) (0x31384142)

Now:

[1:ml1] [NTC] [VID] [Nov 16 09:09:09] v4l2_pixfmt_select: Supported palettes:
[1:ml1] [NTC] [VID] [Nov 16 09:09:09] v4l2_pixfmt_select: (0) pRAA
(10-bit Bayer RGRG/GBGB Packed)
[1:ml1] [DBG] [VID] [Nov 16 09:09:09] v4l2_pixfmt_select: 0 - 10-bit
Bayer RGRG/GBGB Packed (compressed : 0) (0x41415270)
[1:ml1] [NTC] [VID] [Nov 16 09:09:09] v4l2_pixfmt_select: (1) RG10
(10-bit Bayer RGRG/GBGB)
[1:ml1] [DBG] [VID] [Nov 16 09:09:09] v4l2_pixfmt_select: 1 - 10-bit
Bayer RGRG/GBGB (compressed : 0) (0x30314752)
[1:ml1] [NTC] [VID] [Nov 16 09:09:09] v4l2_pixfmt_select: (2) RGGB
(8-bit Bayer RGRG/GBGB)
[1:ml1] [DBG] [VID] [Nov 16 09:09:09] v4l2_pixfmt_select: 2 - 8-bit
Bayer RGRG/GBGB (compressed : 0) (0x42474752)

The third pixel format changed from BA81 to RGGB (8-bit Bayer
BGBG/GRGR (compressed : 0) (0x31384142) to 8-bit Bayer RGRG/GBGB
(compressed : 0) (0x42474752))

If you are still using the same camera module, then something is
seriously wrong with the driver

On Tue, Nov 16, 2021 at 10:40 AM Ed Kapitein <ed...@ka...> wrote:
>
> 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
> > <mot...@li...> wrote:
> >> Some of the observations i made are described in the known issues
>
> >> >< SNIP ><