I can view the image using the command below, but it is not a proper image.
gst-launch-1.0 nvv4l2camerasrc device=/dev/video1 ! 'video/x-raw(memory:NVMM),foo
rmat=UYVY,width=1600,height=1300,framerate=30/1' ! nvvidconv ! 'video/x-raw(memoo
ry:NVMM),format=GRAY8' ! nvvidconv ! 'video/x-raw(memory:NVMM),format=I420' ! nvv
vidconv ! xvimagesink
This is my image capture.
We also share trace logs.
tracelog.txt (243.4 KB)
I would appreciate your help regarding the above phenomenon.
Thanks
Set the preferred_stride to 256 alignment by below command.
preferred_stride= ALIGN_UP(width*bytes_per_pixel,256)
v4l2-ctl -c preferred_stride=3328
It is the same even if you use the command you provided.
Dump the file by vl42-ctl to confirm by 7yuv utility.
What do you check with 7yuv utility?
I want to use the 7yuv utility, but I cannot because of licensing issues.
Hi, ShaneCCC.
When you dump the file with v4l-ctl and check it with yuv viewer, you can check it normally as shown in the picture below.
From what I’ve seen, it doesn’t seem to support 1600x1300 resolution. Can I get support for this??
How about this pipeline?
gst-launch-1.0 nvv4l2camerasrc device= /dev/video2 ! 'video/x-raw(memory:NVMM), width=(int)1600, height=(int)1300, framerate=(fraction)30/1' ! nvvidconv ! nv3dsink -e
Hi, ShaneCCC.
While checking the forum, I found that the video buffer is sorted in 256 byte units, so I changed the width and height to 1792x1536 and confirmed that it worked.
Well, i think set the preferred_stride to 256 alignment should work too.
system
Closed
August 28, 2024, 5:34am
14
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.