[gstreamer-bugs] [Bug 556537] New: [PATCH] typefind: more flexible MPEG4 start code recognition

[GStreamer (bugzilla.gnome.org)]

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:
  http://bugzilla.gnome.org/show_bug.cgi?id=556537

  GStreamer | gst-plugins-base | Ver: HEAD CVS
           Summary: [PATCH] typefind: more flexible MPEG4 start code
                    recognition
           Product: GStreamer
           Version: HEAD CVS
          Platform: Other
        OS/Version: All
            Status: UNCONFIRMED
          Severity: minor
          Priority: Normal
         Component: gst-plugins-base
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: arnout at mind.be
         QAContact: gstreamer-bugs at lists.sourceforge.net
     GNOME version: Unversioned Enhancement
   GNOME milestone: Unspecified


Please describe the problem:
I'm trying to push an MPEG4 stream from a JVC camera into my GStreamer 
pipeline.  However, this camera does not start the stream on a keyframe 
boundary, but just starts emitting the current P frame.  The headers are 
therefore not recognized by typefind, and typefind returns an error.


Steps to reproduce:
gst-launch souphttpsrc location=<JVC camera MPEG4 stream> ! typefind ! fakesink

Actual results:
ERROR: from element /pipeline0/typefindelement0: Could not determine type of
stream.

Expected results:
video/mpeg stream recognized

Does this happen every time?
Yes.

Other information:
Cfr.
http://sourceforge.net/mailarchive/forum.php?thread_name=200810151518.16026.arnout%40mind.be&forum_name=gstreamer-devel


-- 
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=556537.