After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 676174 - Fails to decode several common h264 encodings due to libgstvideoparsersbad.so
Fails to decode several common h264 encodings due to libgstvideoparsersbad.so
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gst-plugins-bad
0.10.x
Other Linux
: Normal normal
: 0.10.24
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2012-05-16 15:24 UTC by Doug McMahon
Modified: 2012-05-17 09:51 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
video that is not decoded (714.58 KB, video/mp4)
2012-05-16 15:24 UTC, Doug McMahon
Details

Description Doug McMahon 2012-05-16 15:24:16 UTC
Created attachment 214190 [details]
video that is not decoded

As reported here on Launchpad - https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/973014
Commonly affected files are Baseline@L2.1, Baseline@L1.1 though also can extend to other h264 profiles.

Files either don't play without error or play with sound but no video.
Snippet of errors seen with gst-debug- 
0:00:00.722733943 5727 0x7f46680034f0 ERROR ffmpeg :0:: AVC: nal size 133916040
0:00:00.724185455 5727 0x7f46680034f0 ERROR ffmpeg :0:: no frame!
0:00:00.724581805 5727 0x7f46680034f0 ERROR ffmpeg :0:: AVC: nal size 23413146
0:00:00.724597030 5727 0x7f46680034f0 ERROR ffmpeg :0:: no frame!

Moving  libgstvideoparsersbad.so to a .bak solves immediately for All affected video files
Attaching a small clip - Baseline@L2.1
Comment 1 Doug McMahon 2012-05-16 15:38:11 UTC
Should also note that all affected files are decoded properly in any Ubuntu release prior to 12.04
Comment 2 Mark Nauwelaerts 2012-05-17 09:08:55 UTC
Sample works for me with recent 0.10, a.o. as it operates in pass-through.

However, in case it were not to end up that way, following fix makes sense in any case: 

commit 845d8dc844225557440dd12d22299fad941d8dfb
Author: Mark Nauwelaerts <mark.nauwelaerts@collabora.co.uk>
Date:   Thu May 17 11:03:07 2012 +0200

    h264parse: also consider nal_length_size when inserting codec data
    
    See #676174.
Comment 3 Mark Nauwelaerts 2012-05-17 09:51:54 UTC
Likewise for 1.0 btw/fwiw.

commit 7f72b99426e8615cc16bff1c8157cd7d6efdba54
Author: Mark Nauwelaerts <mark.nauwelaerts@collabora.co.uk>
Date:   Thu May 17 11:47:19 2012 +0200

    h264parse: also consider nal_length_size when inserting codec data
    
    See #676174.