Send Motion-user mailing list submissions to
[email protected]
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
[email protected]
You can reach the person managing the list at
[email protected]
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 (MrDave)
----------------------------------------------------------------------
Message: 1
Date: Tue, 16 Nov 2021 22:19:31 -0700
From: MrDave <[email protected]>
To: [email protected]
Subject: Re: [Motion-user] raspberry pi libcamera motion bulseye
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"; Format="flowed"
The only solution that I have been able to find is to disable libcamera
entirely and revert to the old camera stack as indicated? in link
below.? I'd note that I did have to revise this further to specify the
memory as 256 to get my Pi camera to work.
/https://forums.raspberrypi.com/viewtopic.php?p=1935591&sid=b0c61887cb4c3352cae9596e9fb6bb88#p1935591/
i.e. /Edit /boot/config.txt, remove the line "camera_auto_detect=1", and
add "start_x=1" and "gpu_mem=128"/.
MrDave
On 11/16/2021 7:46 AM, tosiara wrote:
> I'm not aware if there are any talks with Raspberry Pi team. But
> MrDave has created an issue in motion's github:
> https://github.com/Motion-Project/motion/issues/1434
>
> On Tue, Nov 16, 2021 at 11:15 AM Ed Kapitein<[email protected]> wrote:
>> Yes, same PI, same camera, just rebooted.
>>
>> My guess is that taking a picture with libcamera-still caused this change.
>>
>> Are you in contact with the raspberry pi team, or the libcamera team, so
>> they can be notified of the driver problem?
>>
>>
>> Kind regards,
>>
>> Ed
>>
>>
>> On 11/16/21 10:07 AM, tosiara wrote:
>>> 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<[email protected]> 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
>>>>> <[email protected]> wrote:
>>>>>> Some of the observations i made are described in the known issues
>>>>>>> < SNIP ><
>
> _______________________________________________
> Motion-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/motion-user
> https://motion-project.github.io/
>
> Unsubscribe:https://lists.sourceforge.net/lists/options/motion-user
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
------------------------------
Subject: Digest Footer
_______________________________________________
Motion-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/motion-user
------------------------------
End of Motion-user Digest, Vol 185, Issue 18
********************************************
