Log in

View Full Version : GetAnnexbNALU: no Start Code at the beginning of the NALU, return -1 Error while gett


ssuave
31st December 2013, 17:13
Hi,
It could be a trivial issue but I am not sure the reason why this would occur:

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

Guest
31st December 2013, 17:31
Please tell us what software is producing that!

An unprocessed source stream sample will also be required.

It could be a corrupted stream. Or it could be you open a non-AVC file.

ssuave
31st December 2013, 17:50
Hi again, here is snapshot of the command line:

./ldecod.exe decod.cfg
----------------------------- JM 16.1 (FRExt) -----------------------------
Decoder config file : decod.cfg
--------------------------------------------------------------------------
Input H.264 bitstream : paris_plr0.1_1825.264
Output decoded YUV : paris_cif_1825.yuv
Output status file : log.dec
Input reference file : paris_cif.yuv
XML trace file : paris_plr0.1_1825.xml
XML log level : 3
--------------------------------------------------------------------------
POC must = frame# or field# for SNRs to be correct
--------------------------------------------------------------------------
Frame POC Pic# QP SnrY SnrU SnrV Y:U:V Time(ms)
--------------------------------------------------------------------------
GetAnnexbNALU: no Start Code at the beginning of the NALU, return -1
Error while getting the NALU in file format Annex B, exit

Guest
31st December 2013, 18:10
Give us the source stream if you really want an answer.

Probably the stream has been cut badly at the start or is otherwise corrupted.

ssuave
31st December 2013, 19:13
Uh sorry, I missed attaching an example file. Please see the attachment.

Guest
31st December 2013, 19:36
Thank you. Downloading now to analyze it...

Guest
31st December 2013, 19:40
That doesn't look like a valid H264 file. Can you tell us more about it, where it came from, how it was processed, etc.?

And it is a ridiculously small file for a video stream. Did you cut it down?

foxyshadis
1st January 2014, 00:37
That looks like an index file, not a movie file. Maybe you named the wrong file .264?

ssuave
1st January 2014, 11:25
That doesn't look like a valid H264 file. Can you tell us more about it, where it came from, how it was processed, etc.?

And it is a ridiculously small file for a video stream. Did you cut it down?

Hi again, happy new year.
Thanks for your time. Well, I got these files from the "Impaired bitstreams" available at the following link:
http://vqa.como.polimi.it/sequences.htm

The password to open the archive is: epflpolimivqa

Guest
1st January 2014, 14:38
They intentionally corrupt the bitstreams; that is what "impaired" means! So are you asking us why a corrupted bitstream is generating an error at the decoder? Or are you asking us what it actually means when the error message says there is a missing start code? What are you actually trying to accomplish here?

ssuave
2nd January 2014, 11:48
Thanks for your time, I solved the problem by considering the fact that NALU is of RTP packets in nature, and not of Annex B type.