[FFmpeg-user] ffmpeg defect - Unable to decode some H.264 stream after last changes
nounou.dadoun at avigilon.com
Fri Sep 1 01:20:34 EEST 2017
I have a short question - we're seeing the same behavior/error messages as https://trac.ffmpeg.org/ticket/5529 to do with errors in h264 decoding.
>From our pass-through log files:
[Wed Aug 30 09:59:00 2017] 08-30 09:59:00 WARN : ? : (ffmpeg) [h264 @ 0000000003433560] Invalid NAL unit 1, skipping.
[Wed Aug 30 09:59:00 2017] 08-30 09:59:00 WARN : ? : (ffmpeg) [h264 @ 0000000003433560] no frame!
[Wed Aug 30 09:59:03 2017] 08-30 09:59:03 WARN : ? : (ffmpeg) [h264 @ 0000000003435BE0] Invalid NAL unit 1, skipping.
[Wed Aug 30 09:59:03 2017] 08-30 09:59:03 WARN : ? : (ffmpeg) [h264 @ 0000000003435BE0] no frame!
We have an encoder (camera) running 2.8.6 (i.e. before the fix) and multiple decoders (receiving stations) running 3.1.4 (i.e. after the fix for the ticket above) demonstrating (what looks like) this issue. The question is "would this fix have affected the encoding side?" i.e. might we address the issue by upgrading the camera side? (Not something we do lightly because of regression testing.)
Thanks in advance for any attention/response . N
Senior Firmware Developer, Security Specialist
Office: 604.629.5182 ext 2632
Support: 888.281.5182 | avigilon.com
Follow Twitter | Follow LinkedIn
This email, including any files attached hereto (the "email"), contains privileged and confidential information and is only for the intended addressee(s). If this email has been sent to you in error, such sending does not constitute waiver of privilege and we request that you kindly delete the email and notify the sender. Any unauthorized use or disclosure of this email is prohibited. Avigilon and certain other trade names used herein are the registered and/or unregistered trademarks of Avigilon Corporation and/or its affiliates in Canada and other jurisdictions worldwide.
More information about the ffmpeg-user