[gstreamer-bugs] [Bug 582081] New: ffenc_mpeg4 got two SRC pads

GStreamer (bugzilla.gnome.org) bugzilla-daemon at bugzilla.gnome.org
Sun May 10 09:24:52 PDT 2009


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=582081

  GStreamer | gst-ffmpeg | Ver: 0.10.x
           Summary: ffenc_mpeg4 got two SRC pads
           Product: GStreamer
           Version: 0.10.x
          Platform: Other
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gst-ffmpeg
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: Uraeus at linuxrising.org
         QAContact: gstreamer-bugs at lists.sourceforge.net
     GNOME version: Unspecified
   GNOME milestone: Unspecified


So as the only encoder I found so far ffenc_mpeg4 got two SRC pads.

One is video/mpeg,mpegversion=4 and the other is video/x-divx,divxversion=5.

So according to the ffmpeg FAQ http://ffmpeg.mplayerhq.hu/faq.html#SEC23 there
difference between these two (and divxversion=4) which you can also set on the
ffmpeg level is the FOURCC value.

Having to take this situation into account would make my code quite a bit more
complex as I can no longer iterate on element to create my dictionary between
caps and elements, with caps as the unique value, but have to instead iterate
on caps and at the same time finding back to the original element which had
that caps.

My suggestion is that we do here what we did for qtmux, which is to have one
virtual element for each caps type.


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




More information about the Gstreamer-bugs mailing list