[gstreamer-bugs] [Bug 549799] New: all audio codecs claim to support up to 6 channels

[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=549799

  GStreamer | gst-ffmpeg | Ver: HEAD CVS
           Summary: all audio codecs claim to support up to 6 channels
           Product: GStreamer
           Version: HEAD CVS
          Platform: Other
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: blocker
          Priority: Normal
         Component: gst-ffmpeg
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: t.i.m at zen.co.uk
         QAContact: gstreamer-bugs at lists.sourceforge.net
     GNOME version: Unspecified
   GNOME milestone: Unspecified


I think this commit should be reverted at least for the upcoming release:

        * ext/ffmpeg/gstffmpegcodecmap.c: (gst_ff_aud_caps_new):
        ffmpeg audio decoders can now do up to 6 channels... and actually
        expose it properly. Don't expect any channel mapping though.

IMHO, pad templates should announce possibilities and not impossibilities.

For decoders this is probably less critical, but in the case of encoders this
could lead to breakages, e.g. ffenc_mp2 now advertises to support 6 channels.
Arguably our ffmpeg encoder caps have a long history of being incomplete and
broken, but we should try not to add more such things.

My suggestion is to white-list the decoders that can output 6 channels for now,
and use [1, 2] for all other elements for the upcoming release.


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