NAL parcer error about h264bsd HOT 3 CLOSED

Is the emulation prevention byte will work in the start code prefix (first 4 bytes). It's intended to keep decoders from accidentally adding the start code prefix in a regular byte stream.

I'll look in the decoding of the rest of the NAL unit.

Your test header has two lines. Is it intended to be 2 example byte streams or one long example?

from h264bsd.

It is one example. I parce h264 video generated from test data

ffmpeg.exe -i test_640x360.h264 -vf scale=320:240 -profile:v baseline -f h264 vv.h264

When decoder get pVuiParameters->numUnitsInTick in h264bsdDecodeVuiParameters function it not skip emulation prevention.
In test example in not skip emulation prevention too, but bytes in example data afte shifting by chance that not exist bit of nalHrdParametersPresentFlag.

from h264bsd.

I just ran through a test using xCode but I can't repeat the problem. Once the code gets to h264bsdDecodeVuiParameters the input pStrmData points to a buffer with all of the emulation prevention bytes stripped out. The timingInfoPresentFlag is set and the VUI values agree with ffprobe (1/50 in the case of test_640x360.h264)

It looks like you're using Windows. I'll try the same test using Visual Studio and see what it says.

from h264bsd.