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 708240 - Missing element: H.264 decoder .... sometimes
Missing element: H.264 decoder .... sometimes
Status: RESOLVED DUPLICATE of bug 705452
Product: GStreamer
Classification: Platform
Component: gst-omx
1.x
Other Linux
: Normal major
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2013-09-17 13:41 UTC by Peter Maersk-Moller
Modified: 2013-10-04 10:39 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Peter Maersk-Moller 2013-09-17 13:41:46 UTC
Simple pipelines for decoding mpegts encapsulated h264 streams are likely to fail identifing a suitable decoder, or in case where the omxh264dec is specified directly, it will sometimes fail identifing the right caps thus refusing to decode the stream.

The likelihood of the stream not being played increases significantly as the stream bandwidth goes up or possibly also as the video geometry increases, though in some cases the latter lead to the first.

The problem was first reported in this email http://lists.freedesktop.org/archives/gstreamer-devel/2013-September/042954.html
The email contains instructions for setting up pipelines to provoke the error.

This email list links to media files, where some works and others do not as listed in the email. The production setup was liusted in the previous email.

In this email, Erik Andresen confirms the findings:
http://lists.freedesktop.org/archives/gstreamer-devel/2013-September/042962.html
Comment 1 Peter Maersk-Moller 2013-09-17 13:45:21 UTC
By the way, all streams are identified correctly and played well on a x86 based laptop with GStreamer 1.0.6 and 1.0.9 rather than the Raspberry Pi, although the problem may lay in the tsdemux.
Comment 2 Sebastian Dröge (slomo) 2013-09-27 14:25:25 UTC
Can you provide a debug log with GST_DEBUG=6 for a case where it is failing?
Comment 3 Peter Maersk-Moller 2013-09-27 14:57:25 UTC
Hi Sebastian.

I can if you want, but in the following message, you can find both pipeline example and link to video examples that will play and video examples that will not.

http://lists.freedesktop.org/archives/gstreamer-devel/2013-September/042957.html

One of the files that won't play is this:
http://193.88.237.12/gstreamer/teststream-main-l21-660x240-notworking.ts

This message describes how the files was generated.
http://lists.freedesktop.org/archives/gstreamer-devel/2013-September/042954.html

Nevertheless, as you may not have a rasp pi, attached is a log for a minute or so.

Here is a link to debug output as per request:
http://193.88.237.12/gstreamer/debug-rasp-pi.gz
Comment 4 Sebastian Dröge (slomo) 2013-10-04 10:39:53 UTC
Relevant part of the log:

gstdecodebin2.c:1855:connect_pad:<capsfilter0>[00m trying factory <omxh264dec>
gstdecodebin2.c:1886:connect_pad:<capsfilter0>[00m caps video/x-h264, stream-format=(string)byte-stream, alignment=(string)au, parsed=(boolean)true not subset of video/x-h264, parsed=(boolean)true, alignment=(string)au, stream-format=(string)byte-stream, width=(int)[ 1, 2147483647 ], height=(int)[ 1, 2147483647 ]


This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

*** This bug has been marked as a duplicate of bug 705452 ***