TDA4VH-Q1: Require assistance to understand h265 decoding using hardware VPU.

jenius Robinson

Part Number: TDA4VH-Q1

Hi team,

We are using "ti-processor-sdk-rtos-j784s4-evm-11_00_00_06" and "ti-processor-sdk-linux-adas-j784s4-evm-11_00_00_08".

In our case we are trying to use hardware decoding VPU to decode our H265 file or Stream. At that time it is throwing "Internal data stream error". Meanwhile the avdec_h265 processing the input without any issue. Our ultimate goal is to use the hardware decoder, because our main application already needed the maximum processing of CPU.

please find the log of terminal given below:

root@j784s4-evm:~# gst-launch-1.0 -v udpsrc port=5000 ! application/x-rtp, media=video, clock-rate=90000, encoding-name=H265, payload=96 ! rtph265depay ! h265parse ! v4l2h265dec ! videoconvert ! video/x-raw, format=NV12 ! fakesink
Setting pipeline to PAUSED ...
Pipeline is live and does not need PREROLL ...
Pipeline is PREROLLED ...
Setting pipeline to PLAYING ...
New clock: GstSystemClock
/GstPipeline:pipeline0/GstCapsFilter:capsfilter0.GstPad:src: caps = application/x-rtp, media=(string)video, clock-rate=(int)90000, encoding-name=(string)H265, payload=(int)96
/GstPipeline:pipeline0/GstRtpH265Depay:rtph265depay0.GstPad:src: caps = video/x-h265, stream-format=(string)byte-stream, alignment=(string)au
/GstPipeline:pipeline0/GstH265Parse:h265parse0.GstPad:sink: caps = video/x-h265, stream-format=(string)byte-stream, alignment=(string)au
/GstPipeline:pipeline0/GstRtpH265Depay:rtph265depay0.GstPad:sink: caps = application/x-rtp, media=(string)video, clock-rate=(int)90000, encoding-name=(string)H265, payload=(int)96
Redistribute latency...
/GstPipeline:pipeline0/GstH265Parse:h265parse0.GstPad:src: caps = video/x-h265, stream-format=(string)byte-stream, alignment=(string)au, width=(int)1280, height=(int)720, framerate=(fraction)30/1, chroma-format=(string
ERROR: from element /GstPipeline:pipeline0/GstUDPSrc:udpsrc0: Internal data stream error.
Additional debug info:
/usr/src/debug/gstreamer1.0/1.22.12/libs/gst/base/gstbasesrc.c(3134): gst_base_src_loop (): /GstPipeline:pipeline0/GstUDPSrc:udpsrc0:
streaming stopped, reason not-negotiated (-4)
Execution ended after 0:00:00.792701025
Setting pipeline to NULL ...
Freeing pipeline ...
root@j784s4-evm:~#

root@j784s4-evm:~# gst-launch-1.0 filesrc location=output.h265 ! h265parse ! v4l2h265dec ! videoconvert ! video/x-raw, format=NV12 ! fakesink
Setting pipeline to PAUSED ...
Pipeline is PREROLLING ...
Redistribute latency...
ERROR: from element /GstPipeline:pipeline0/GstH265Parse:h265parse0: Internal data stream error.
Additional debug info:
/usr/src/debug/gstreamer1.0/1.22.12/libs/gst/base/gstbaseparse.c(3699): gst_base_parse_loop (): /GstPipeline:pipeline0/GstH265Parse:h265parse0:
streaming stopped, reason not-negotiated (-4)
ERROR: pipeline doesn't want to preroll.
Setting pipeline to NULL ...
Freeing pipeline ...
root@j784s4-evm:~#

Let me know if you need additional information from my end.

Regards,

Jenius R

6 months ago

0 Sarabesh Srinivasan 6 months ago

TI__Mastermind 21550 points

Hello Jenius,

Will review this and get back to you in the next couple days.

Thanks,
Sarabesh S.

0 Sarabesh Srinivasan 6 months ago in reply to Sarabesh Srinivasan

TI__Mastermind 21550 points

Hi Jenius,

Apologies for the delay. I talked to our development team and it seems like it could be an error with encoding and incorrect pixel format. Could you share the input stream so I can try to replicate the issue.

Regards,
Sarabesh S.

0 jenius Robinson 6 months ago in reply to Sarabesh Srinivasan

Prodigy 130 points

Hi Sarabesh,

Thank you for your valuable response,

As per your reply, If the issue was pixel format means.

The "avdec_h265" decoder processing the file without throwing any issue, meanwhile v4l2h265dec throwing error.

Could you please help to handle it.

Please find the zip file contains the sample H265 file.

Encoded_sample.zip

Regards,

Jenius R

0 Sarabesh Srinivasan 6 months ago in reply to jenius Robinson

TI__Mastermind 21550 points

Jenius,

Thanks for the file stream I will inspect and let you know my findings.

Best,
Sarabesh S.

0 jenius Robinson 5 months ago in reply to Sarabesh Srinivasan

Prodigy 130 points

Hi Sarabesh,

We are waiting for your valuable reply,

Please provide solution as soon as possible.

Regards,

Jenius R

0 Sarabesh Srinivasan 5 months ago in reply to jenius Robinson

TI__Mastermind 21550 points

Hi Jenius,

Could you try the following pipeline:

gst-launch-1.0 filesrc location=/output.h265 ! h265parse ! v4l2h265dec ! videoconvert ! video/x-raw,format=NV12,width=640,height=480 ! fakesink

From the error message the issue seems to be with the pipeline's caps negotiation. Let me know if this poses any issues for you.

Thanks,
Sarabesh S.

0 jenius Robinson 5 months ago in reply to Sarabesh Srinivasan

Prodigy 130 points

Hi sarabesh,

We have tested the given gstreamer command.

But this also throwing the same error.

Regards,

Jenius R

0 Sarabesh Srinivasan 5 months ago in reply to jenius Robinson

TI__Mastermind 21550 points

Hi Jenius,

Will continue investigating

0 Sarabesh Srinivasan 4 months ago in reply to Sarabesh Srinivasan

TI__Mastermind 21550 points

Hi Jenius,

I saw no issues with decoding if you use absolute paths. Please specify the full path of your stream in your decode pipeline and it should work.

My test case:

filesrc location=/root/jellyfish_1920x1080_hevc.265 ! h265parse ! v4l2h265dec ! videoconvert ! video/x-raw, format=NV12 ! fakesink

stream: https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/791/jellyfish_5F00_1920x1080_5F00_hevc.265

0 jenius Robinson 4 months ago in reply to Sarabesh Srinivasan

Prodigy 130 points

Hi sarabesh,

We are using meta data in this H265 encoded file sample "output.h265 ". meanwhile it is properly decoding by "avdec_h265".

Issue only with v4l2h265dec.

Is "v4l2h265dec" have the capability of decoding the h265 files with metadata.

Regards,

Jenius R

0 jenius Robinson 4 months ago in reply to Sarabesh Srinivasan

Prodigy 130 points

Please find my attached images for the decoding performance between "avdec_h265" and "v4l2h265dec" with obsolute path.

0 Sarabesh Srinivasan 4 months ago in reply to jenius Robinson

TI__Mastermind 21550 points

Hi Jenius,

I was able to replicate. Will inspect the stream to see why our decoder is not able to decode this stream.

0 Sarabesh Srinivasan 4 months ago in reply to Sarabesh Srinivasan

TI__Mastermind 21550 points

Reached out to the IP vendor to identify the issue that we are seeing. Will let you know their feedback.

Thanks,
Sarabesh S

0 Sarabesh Srinivasan 4 months ago in reply to Sarabesh Srinivasan

TI__Mastermind 21550 points

Hi Jenius,

The issue is due to the input stream like we suspected. The encoded format of the stream is YUV422 as indicated by the chroma_format_idc=2 value. The Wave521CL does not support decdoing streams encoded as YUV422.

Note:
The encoder accepts YUV422 as an input format, but internally converts it to YUV420 before encoding.
But the decoder does not support decoding streams that were encoded as YUV422.

Best,
Sarabesh S.

Processors

Processors forum

TDA4VH-Q1: Require assistance to understand h265 decoding using hardware VPU.