SK-AM62A-LP: limitation of resolution with v4l2jpegenc.

Jaimin Patel

Part Number: SK-AM62A-LP

Tool/software:

I am using tiovxmultiscaler gstreamer plugin for ROI of image in that. I am successfully able to run below pipeline with tiovxmultiscaler.

gst-launch-1.0 -v v4l2src device=/dev/video-rpi-cam0 io-mode=dmabuf-import ! video/x-bayer, width=1920, height=1200, framerate=60/1, format=rggb10 ! tiovxisp sink_0::device=/dev/v4l-rpi-subdev0 sensor-name="SENSOR_SONY_IMX219_RPI" dcc-isp-file=/opt/imaging/ar0235/dcc_viss.bin sink_0::dcc-2a-file=/opt/imaging/ar0235/dcc_2a.bin format-msb=9 ! video/x-raw, format=NV12, width=1920, height=1200, framerate=60/1 ! tiovxmultiscaler name=multi src_0::roi-startx=480 src_0::roi-starty=300
src_0::roi-width=960 src_0::roi-height=600 multi. ! video/x-raw,format=NV12,width=960,height=600 ! v4l2jpegenc ! tcpserversink host=172.25.4.208 port=5000

But, if I am trying with random ROI value in that case v4l2jpegenc failed. so, is there any limitation of resolution with v4l2jpegenc.

I am trying with this 920x800 in that getting below error:

ERROR: from element /GstPipeline:pipeline0/v4l2jpegenc:v4l2jpegenc0: Device '/dev/video2' cannot capture at 920x800
Additional debug info:
../gst-plugins-good-1.20.7/sys/v4l2/gstv4l2object.c(4206): gst_v4l2_object_set_format_full (): /GstPipeline:pipeline0/v4l2jpegenc:v4l2jpegenc0:
Tried to capture at 920x800, but device returned size 896x800

Pipeline:

gst-launch-1.0 -v v4l2src device=/dev/video-rpi-cam0 io-mode=dmabuf-import ! video/x-bayer, width=1920, h
eight=1200, framerate=60/1, format=rggb10 ! tiovxisp sink_0::device=/dev/v4l-rpi-subdev0 sensor-name="SENSOR_SONY_IMX219_RPI" dcc-isp
-file=/opt/imaging/ar0235/dcc_viss.bin sink_0::dcc-2a-file=/opt/imaging/ar0235/dcc_2a.bin format-msb=9 ! video/x-raw, format=NV12, wi
dth=1920, height=1200, framerate=60/1 ! tiovxmultiscaler name=multi src_0::roi-startx=0 src_0::roi-starty=0 src_0::roi-width=920 src_
0::roi-height=800 multi. ! video/x-raw,format=NV12,width=920,height=800 ! v4l2jpegenc ! tcpserversink host=172.25.4.208 port=5000

Error:

, interlace-mode=(string)progressive, colorimetry=(string)1:4:7:1
/GstPipeline:pipeline0/GstTCPServerSink:tcpserversink0.GstPad:sink: caps = image/jpeg, width=(int)920, height=(int)800, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction)60/1, interlace-mode=(string)progressive, colorimetry=(string)1:4:7:1
Redistribute latency...
ERROR: from element /GstPipeline:pipeline0/v4l2jpegenc:v4l2jpegenc0: Device '/dev/video2' cannot capture at 920x800
Additional debug info:
../gst-plugins-good-1.20.7/sys/v4l2/gstv4l2object.c(4206): gst_v4l2_object_set_format_full (): /GstPipeline:pipeline0/v4l2jpegenc:v4l2jpegenc0:
Tried to capture at 920x800, but device returned size 896x800
Execution ended after 0:00:00.352520341
Setting pipeline to NULL ...
ERROR: from element /GstPipeline:pipeline0/v4l2jpegenc:v4l2jpegenc0: Could not get/set settings from/on resource.
Additional debug info:
../gst-plugins-good-1.20.7/sys/v4l2/gstv4l2object.c(3664): gst_v4l2_object_set_format_full (): /GstPipeline:pipeline0/v4l2jpegenc:v4l2jpegenc0:
Device is in streaming mode
Freeing pipeline ...
18614.370704 s: VX_ZONE_INIT:[tivxHostDeInitLocal:115] De-Initialization Done for HOST !!!
18614.375291 s: VX_ZONE

Thanks,
Jaimin

over 1 year ago

0 Suren Porwar over 1 year ago

TI__Mastermind 27995 points

Hi Jaimin,

I am guessing the width and height should be a multiple of 32.
Does providing correct resolution for JPEG encoding after scaling work?

Best Regards,

Suren

0 Jaimin Patel 11 months ago in reply to Suren Porwar

Intellectual 650 points

Hello Suren,

With multiple of 32 of width and height it's working. can I know why this limitation ?

One observation in capture image using below command getting black line in image.

gst-launch-1.0 -v v4l2src device=/dev/video-rpi-cam0 io-mode=dmabuf-import ! video/x-raw, width=1920, height=1200, framerate=60/1, format=GRAY16_LE ! tiovxmultiscaler name=multi src_0::roi-startx=0 src_0::roi-starty=0 src_0::roi-width=960 src_0::roi-height=600 multi. ! video/x-raw,format=GRAY16_LE,width=960,height=600,framerate=60/1 ! filesink location=data.raw

ROI_992x928

ROI_512x416

Thanks,
Jaimin

0 Suren Porwar 11 months ago in reply to Jaimin Patel

TI__Mastermind 27995 points

Hi Jaimin,

I was able to replicate the issue with just running the below pipeline:

gst-launch-1.0 -v videotestsrc ! video/x-raw, format=NV12, width=1920, height=1200, framerate=60/1 ! tiovxmultiscaler \
name=multi src_0::roi-startx=0 src_0::roi-starty=0 src_0::roi-width=512 src_0::roi-height=416 multi. ! \
video/x-raw,format=NV12,width=512,height=416,framerate=60/1 ! filesink location=data-nv12.raw

screenshot of the data_nv12.raw as viewed in pixelviewer:

I have created a Jira to track this issue internally.

Best Regards,

Suren

0 Jaimin Patel 11 months ago in reply to Suren Porwar

Intellectual 650 points

Hello Suren,
Any update on this ?

Thanks,
Jaimin

0 Suren Porwar 11 months ago in reply to Jaimin Patel

TI__Mastermind 27995 points

Hi Jaimin,

The team is still analyzing and root causing the issue. Will keep you posted on any developments by next week.

Best Regards,

Suren

0 Jaimin Patel 11 months ago in reply to Suren Porwar

Intellectual 650 points

Hello Suren,

Any update ?

Thanks,
Jaimin

0 Suren Porwar 11 months ago in reply to Jaimin Patel

TI__Mastermind 27995 points

Hi Jaimin,

This seems to be a cache-issue and the team is diligently working on root causing and fixing it. Will keep you posted early next week, when I will have an update from our SW team.

Best Regards,

Suren

0 Jianzhong Xu 10 months ago in reply to Suren Porwar

TI__Guru 58785 points

Hello Jaimin,

Sorry for the delay. We've identified a few things that may have caused this issue. Can you try the following?

1. Apply this patch to /opt/edgeai-gst-plugins: https://github.com/TexasInstruments/edgeai-gst-plugins/commit/a6db8dd7931b15290235f33265052ef51848e338

2. Rebuild Gstreamer plugins by running script /opt/edgeai-gst-apps/scripts/install_gst_plugins.sh. Make sure the EVM has network connection so that it has correct date information for the script to run.

Another fix needs to rebuild the ti-firmware-builder. Do you have that? Which version?

Regards,

Jianzhong