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. RPi5 camera issue: Is this palette supported: SBGGR10 (Z4)
----------------------------------------------------------------------
Message: 1
Date: Sat, 15 Jun 2024 23:57:53 -0500
From: Z4 <z...@z2zcorp.com>
To: Motion discussion list <motion-user@lists.sourceforge.net>
Subject: [Motion-user] RPi5 camera issue: Is this palette supported:
SBGGR10
Message-ID: <0bb7afd4-74f6-4710-9b9b-910817aa7...@z2zcorp.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
I have an ixm296 (official RPi camera, global shutter) on a Raspberry
Pi5, and though I can get motion to work with it, the resultant image is
very green and has dozens on horizontal lines cutting through it tightly
spaced and generally poor image quality with some strange ghosting
artifacts.
I don't quite know what the v4l2_palette setting is for exactly, or if
it may come into play here:
# libcamerify /usr/bin/motion -c /etc/motion/motion.conf -l
/var/log/motion.log -k 9 -d 6
[0:motion] [NTC] [ALL] conf_load: Processing thread 0 - config file
/etc/motion/motion.conf
[0:motion] [NTC] [ALL] read_camera_dir: Processing config file
conf.d/camera-styx.conf
[0:motion] [NTC] [ALL] config_camera: Processing camera config file
conf.d/camera-styx.conf
[0:motion] [NTC] [ALL] motion_startup: Logging to file (/var/log/motion.log)
[5:19:40.119501210] [28323] INFO Camera camera_manager.cpp:284
libcamera v0.2.0
[5:19:40.140141245] [28324] INFO RPI pisp.cpp:695 libpisp version
v1.0.5 999da5acb4f4 14-06-2024 (07:31:26)
[5:19:40.167294494] [28324] INFO RPI pisp.cpp:1154 Registered camera
/base/axi/pcie@120000/rp1/i2c@88000/imx296@1a to CFE device /dev/media2
and ISP device /dev/media0 using PiSP variant BCM2712_C0
[5:19:40.167680014] [28323] WARN V4L2 v4l2_pixelformat.cpp:344
Unsupported V4L2 pixel format RPBP
[5:19:40.168163088] [28323] WARN V4L2 v4l2_pixelformat.cpp:344
Unsupported V4L2 pixel format RPBP
[5:19:40.168452848] [28323] WARN V4L2 v4l2_pixelformat.cpp:344
Unsupported V4L2 pixel format RPBP
[5:19:40.168639941] [28323] INFO Camera camera.cpp:1183 configuring
streams: (0) 640x480-YUV420
[5:19:40.168813775] [28324] INFO RPI pisp.cpp:1450 Sensor:
/base/axi/pcie@120000/rp1/i2c@88000/imx296@1a - Selected sensor format:
1456x1088-SBGGR10_1X10 - Selected CFE format: 1456x1088-PC1B
[5:19:40.169730313] [28323] INFO Camera camera.cpp:1183 configuring
streams: (0) 640x480-YUV420
[5:19:40.169836832] [28324] INFO RPI pisp.cpp:1450 Sensor:
/base/axi/pcie@120000/rp1/i2c@88000/imx296@1a - Selected sensor format:
1456x1088-SBGGR10_1X10 - Selected CFE format: 1456x1088-PC1B
Now I'm not sure what all that means, but it does appear to select the
1456x1088-SBGGR10_1X10 - Selected CFE format: 1456x1088-PC1B
sensor format. I notice that V4L2_PIX_FMT_SBGGR16 and
V4L2_PIX_FMT_SBGGR8 is supported, but not SBGGR10.
Of course, this could have nothing to do my very green image with many
horizontal lines through it, because the camera is YUV420:
streams: (0) 640x480-YUV420
So maybe that's nothing...on the other hand, the warning
WARN V4L2 v4l2_pixelformat.cpp:344 Unsupported V4L2 pixel format RPBP
has no real data available on it anywhere, so who knows.
So three questions arise from this:
1) how to fix a green image with many horizontal lines (looks fine with
rpicam-vid ...)
2) do I need to worry about the v4l2_palette setting for this camera/setup?
3) What is the meaning of "Unsupported V4L2 pixel format RPBP" and is
that something that needs addressing?
There's nothing particularly alarming in the motion.log:
[1:ml1:secn-styx] [NTC] [ALL] [Jun 15 23:16:26] motion_init: Camera 100
started: motion detection Enabled
[1:ml1:secn-styx] [WRN] [ALL] [Jun 15 23:16:26] motion_init: Invalid
configuration dimensions 0x0
[1:ml1:secn-styx] [WRN] [ALL] [Jun 15 23:16:26] motion_init: Using
default dimensions 480x640
[1:ml1:secn-styx] [NTC] [VID] [Jun 15 23:16:26] vid_start: Opening V4L2
device
[1:ml1:secn-styx] [NTC] [VID] [Jun 15 23:16:26] v4l2_device_open: Using
videodevice /dev/video0 and input -1
[1:ml1:secn-styx] [NTC] [VID] [Jun 15 23:16:26] v4l2_device_capability:
- VIDEO_CAPTURE
[1:ml1:secn-styx] [NTC] [VID] [Jun 15 23:16:26] v4l2_device_capability:
- STREAMING
[1:ml1:secn-styx] [NTC] [VID] [Jun 15 23:16:26] v4l2_input_select: Name
= "/base/axi/pcie@120000/rp1/i2c@8"- CAMERA
[1:ml1:secn-styx] [NTC] [VID] [Jun 15 23:16:27] v4l2_norm_select: Device
does not support specifying PAL/NTSC norm
[1:ml1:secn-styx] [NTC] [VID] [Jun 15 23:16:27] v4l2_pixfmt_try: Testing
palette YU12 (640x480)
[1:ml1:secn-styx] [NTC] [VID] [Jun 15 23:16:27] v4l2_pixfmt_set: Using
palette YU12 (640x480)
[1:ml1:secn-styx] [ERR] [VID] [Jun 15 23:16:27] v4l2_fps_set: Error
setting fps. Return code -1
[1:ml1:secn-styx] [NTC] [ALL] [Jun 15 23:16:27] image_ring_resize:
Resizing pre_capture buffer to 1 items
[1:ml1:secn-styx] [NTC] [ALL] [Jun 15 23:16:27] image_ring_resize:
Resizing pre_capture buffer to 201 items
though that does seem to confirm that the palette is probably not an
issue...what's confusing is that there is a CFE setting and a "normal"
palette with V4L2_PIX_FMT_SBGGR16 in it but no SBGGR10 (because its not
needed?). Hence my confusion...
Thanks,
z4
------------------------------
------------------------------
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 214, Issue 1
*******************************************
