AM62A7: DCC live tunning problem for IR pattern

Hello,

I'm afraid the tuning tool may not support this feature yet. Let me check internally and get back to you.

Regards,

Jianzhong

Hello，Jianzhong

When we save the raw by DCC 3.0 in different display command： No matter which video (video2 for RGB or video3 for IR) chosen, if we use GRAY8 to convert to NV12 to display, the DCC software can not save the RAW and the software will be stuck, but if we use “NV12”, it can save RAW good。

The command as following：

GYAY8 and can not save RAW：

gst-launch-1.0 \
v4l2src device=/dev/video3 io-mode=5 ! \
video/x-bayer, width=2592, height=1944, format=bggi10 ! queue leaky=2 ! \
tiovxisp using_ir_mode=True sensor-name=SENSOR_OX05B_RGBIR \
dcc-isp-file=/opt/imaging/ox05b/dcc_viss.bin \
sink_0::dcc-2a-file=/opt/imaging/ox05b/dcc_2a.bin sink_0::device=/dev/v4l-subdev2 format-msb=9 \
sink_0::pool-size=8 src::pool-size=8 ! \
video/x-raw, format=GRAY8, width=2592, height=1944 ! videoconvert ! \
video/x-raw, format=NV12 ! tiovxldc dcc-file=/opt/imaging/ox05b/dcc_ldc.bin sensor-name=SENSOR_OX05B_RGBIR ! \
video/x-raw, format=NV12, width=1920, height=1080, framerate=30/1 ! \
tiperfoverlay main-title="TI EdgeAI Hirain" title="Camera Demo" ! \
kmssink driver-name=tidss sync=false

NV12 and can save RAW：

gst-launch-1.0 \
v4l2src device=/dev/video3 io-mode=5 ! \
video/x-bayer, width=2592, height=1944, format=bggi10 ! queue leaky=2 ! \
tiovxisp using_ir_mode=True sensor-name=SENSOR_OX05B_RGBIR \
dcc-isp-file=/opt/imaging/ox05b/dcc_viss.bin \
sink_0::dcc-2a-file=/opt/imaging/ox05b/dcc_2a.bin sink_0::device=/dev/v4l-subdev2 format-msb=9 \
sink_0::pool-size=8 src::pool-size=8 ! \
video/x-raw, format=NV12, width=2592, height=1944 ! videoconvert ! \
video/x-raw, format=NV12 ! tiovxldc dcc-file=/opt/imaging/ox05b/dcc_ldc.bin sensor-name=SENSOR_OX05B_RGBIR ! \
video/x-raw, format=NV12, width=1920, height=1080, framerate=30/1 ! \
tiperfoverlay main-title="TI EdgeAI Hirain" title="Camera Demo" ! \
kmssink driver-name=tidss sync=false

Hello,

Thanks for the additional information. Saving RAW when streaming in GRAY8  is not yet supported by the tuning tool. We're looking into this.

You've probably noticed that, in your second pipeline, since "NV12" was used, the RGB data (instead of IR data) after RGB-IR separation was output to the display. The raw image should still be IR data since the input is from the IR video node.

Regards,

Jianzhong

Jianzhong, do we have plan to support the IR/GRAY color space better in terms of both DCC and GST plugins(esp. for display it after some converter) by 9.0 SDK please?

I'm asking because this IR/8 bit Gray pattern is very common for the DMS/OMS EEs. 

Hi Xu,

We're looking into improving the tuning tool to enable saving raw IR data during IR streaming. This is not tied with SDK release.

Another thing we can add support for is the auto exposure control for IR stream, but it won't be available in 9.0 SDK.

Xu(SH) Liu said:

esp. for display it after some converter

Not sure what you meant here, but did you refer to what's discussed here: https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1246666/am62a7-q1-question-related-to-gstreamer-pipeline-latency? 

Is there anything else that you think should be improved regarding IR?

Regards,

Jianzhong

Jianzhong Xu said:

Saving RAW when streaming in GRAY8

I guess this might be related to the way tuning server is implemented in SDK.
It probably assumes yuv output in NV12 format.
While yuv output is not in the expected format, tuning server may get stuck.
I would expect we only need to make some changes in SDK for saving raw.
Brandon Maciel may comment on the details.

We've reproduced this problem and will implement a fix in next release.

Hi, Jianzhong

When IR display, this issue still exist: when we save RAW or YUV, the DCC will be stuck. 

Is there any process about this issue?

Best,

Le seul