[gstreamer-bugs] [Bug 556521] New: [PATCH] typefind: improved MPEG4 start code recognition
bugzilla-daemon at bugzilla.gnome.org
Thu Oct 16 03:03:46 PDT 2008
If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
GStreamer | gst-plugins-base | Ver: HEAD CVS
Summary: [PATCH] typefind: improved MPEG4 start code recognition
Version: HEAD CVS
AssignedTo: gstreamer-bugs at lists.sourceforge.net
ReportedBy: arnout at mind.be
QAContact: gstreamer-bugs at lists.sourceforge.net
GNOME version: Unspecified
GNOME milestone: Unspecified
Please describe the problem:
I have a camera that specifies a YUV clamping section in the visual object
header. However, mpeg4_video_type_find always assumes a 5-byte
visual_object_start_code. The attached patch allows start codes up to 10 bytes
(the maximum according to http://xhelmboyx.tripod.com/formats/mpeg-layout.txt
Note, I'm going to make a more extended patch with more functionality in a
separate bug report. However, I wanted to submit this already in case the
other patch isn't accepted.
Steps to reproduce:
gst-launch souphttpsrc location=<JVC camera MPEG4 stream> ! typefind ! fakesink
ERROR: from element /pipeline0/typefindelement0: Could not determine type of
video/mpeg stream recognized
Does this happen every time?
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.
You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=556521.
More information about the Gstreamer-bugs