But when I tested the plugin with different formats, I got different result.
The test commend is:
“gst-launch-0.10 videotestsrc pattern=checkers-8 ! “video/x-raw-yuv, width=1920, height=1080, framerate=(fraction)6,format=(fourcc)I420” ! nv_omx_hdmi_videosink -v -e”.
The display is right only when format is set as (fourcc)I420 and (fourcc)NV12.
When set as YUY2 or UYVY, there is a chaos display.
Thanks very much for the replay!
I tested as you suggest, but got such a result:
ubuntu@tegra-ubuntu:~$ gst-launch-0.10 videotestsrc pattern=checkers-8 ! “video/x-raw-yuv, width=1920, height=1080, framerate=(fraction)6,format=(fourcc)I420” ! autovideosink -v -e
Setting pipeline to PAUSED …
Inside NvxLiteH264DecoderLowLatencyInitNvxLiteH264DecoderLowLatencyInit set DPB and MjstreamingCaught SIGSEGV accessing address 0x18 #0 0xb6d635f4 in ?? () #1 0xb6d62372 in ?? ()
Spinning. Please run ‘gdb gst-launch 4299’ to continue debugging, Ctrl-C to quit, or Ctrl-\ to dump core.
^CCaught interrupt – ^C
I have tested with ubuntu desktop. But it is a non-full-screen display, while we need display with full-screen. That is why we run nv_omx_hdmi_videosink at text mode…
Inside NvxLiteH264DecoderLowLatencyInitNvxLiteH264DecoderLowLatencyInit set DPB and MjstreamingWARNING: erroneous pipeline: could not link nvvconv0 to omxhdmivideosink0