No valid metadata for frame

Robotics & Edge Computing Jetson & Embedded Systems Jetson TX2
1

hi.
I launch decoder sample from MM API samples:

./video_decode H264 --disable-rendering --report-metadata ./no_metadata.h264

Output:

No valid metadata for frame

Why? This is bug?

This is my video file “no_metadata.h264”: https://drive.google.com/open?id=1Pm52RRMpzrVCzg1Mpomn5oWcJRhKbyNE

2

Hi,
You may compare no_metadata.h264 to sample_outdoor_car_1080p_10fps.h264.

$ ./video_decode H264 --disable-rendering --report-metadata ../../data/Video/sample_outdoor_car_1080p_10fps.h264

Or inspect no_metadata.h264 through JM decoder

3

Hi.

Why do I need to compare something? I ask you to check my file and answer the question: why is the metadata not extracted in this example?

I see that there are no nal-units with type 5 (idr) in the keyframes in my file. Only aud,sps,pps,sei,single nal-units. Could this be the reason?

Then it must be said that the medadata cannot always be extracted, there are limitations. Or is it a bug.

4

In other words, if there is no idr nal’s, then the metadata will not be valid?

5

Hi,
JM decoder cannot parse the h264 stream. It reports the error:

get_annex_b_NALU: no Start Code at the beginning of the NALU, return -1
Error while getting the NALU in file format Annex B, exit

We have reference h264 stream and would encourage users do initial debugging/comparison first. Probably I did not express in a soft manner. My apology.

6

hi.
i’m sorry for my video file. i converted him to valid h264 bitstream, JM decoder parse that stream ok.

Please, check again: https://drive.google.com/open?id=1LbYK7NRegoS00KCo1sfld4MeWRxXOU_N

7

Hi,
JM decoder still shows

Warning: Decoding does not start with an IDR picture.

Your comment is correct. It has to start with IDR frame.