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 563433 - implement h264parse AVC output
implement h264parse AVC output
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gst-plugins-bad
0.10.9
Other Linux
: Normal enhancement
: 0.10.18
Assigned To: GStreamer Maintainers
GStreamer Maintainers
: 563434 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-12-06 12:29 UTC by kumar
Modified: 2009-12-10 12:13 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description kumar 2008-12-06 12:29:40 UTC
Hi, 
When I tried muxing H264 file for FLV using flvmux elment in gst-plugin-bad-0.10.9, its generating very small file size. Which cannot be played back in Flash player.
Pipeline:
gst-launch-0.10 filesrc location=/home/Test.264 ! h264parse ! flvmux ! filesink location=/home/Test_1.flv
Comment 1 Bruno Boaventura 2008-12-06 12:52:22 UTC
*** Bug 563434 has been marked as a duplicate of this bug. ***
Comment 2 Wim Taymans 2008-12-08 10:40:15 UTC
I'm assuming that the file 'Test.264' is an annex B byte stream? If not, please try again with a bytestream formatted input file.

It's uncertain that the above pipeline will work, usually a muxer needs an AVC H264 stream and h264parse cannot yet convert an annex B file to AVC.

Comment 3 Wim Taymans 2008-12-08 20:53:59 UTC
Got this response as a reply to the bugzilla mail:

"I am using a Annex B byte H264 stream. And I would like to know what type of
H264 file we need to provide as input to the h264parse element."
Comment 4 Wim Taymans 2008-12-08 21:00:57 UTC
h264parse accepts both AVC and bytestream formats. It produces the same format on the source pad as it received on the sinkpad.

You probably need to add a property to h264parse to turn the stream into an AVC stream or implement the feature with the caps properties discussed on the mailing list. 

Marking as enhancement to h264parse.
Comment 5 Mark Nauwelaerts 2009-12-10 12:13:35 UTC
Following commit implements such stream format transformation controlled by a property (though it would properly make more convenient sense to control this by some standardized caps properties):

commit b4d9b81b8a5d588be6ae634499a24a9be39a8aff
Author: Mark Nauwelaerts <mark.nauwelaerts@collabora.co.uk>
Date:   Sun Nov 22 19:30:43 2009 +0100

    h264parse: optional transforming from bytestream to sample format (or vice versa)