[gstreamer-bugs] [Bug 521542] New: AAC decoder doesn't support raw AAC streams

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

  GStreamer | gst-openmax | Ver: HEAD CVS
           Summary: AAC decoder doesn't support raw AAC streams
           Product: GStreamer
           Version: HEAD CVS
          Platform: Other
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gst-openmax
        AssignedTo: felipe.contreras at nokia.com
        ReportedBy: ext-tommi.myohanen at nokia.com
         QAContact: gstreamer-bugs at lists.sourceforge.net
     GNOME version: Unspecified
   GNOME milestone: Unspecified


It looks like sink_setcaps() in gstomx_aacdec.c doesn't do much with the caps
it receives. Therefore the plugin only works when the stream contains enough
information about stream contents (a.k.a. has either ADTS or ADIF header).
Therefore this decoder plugin doesn't work when audio is coming from some
container, e.g. from MP4 file, because in that case the stream information is
passed in the caps:

setcaps (sink): audio/mpeg, mpegversion=(int)4, rate=(int)48000,
channels=(int)2, framed=(boolean)true, codec_data=(buffer)1190

AAC decoder element should parse these caps in a similar manner to FAAD plugin
in gst-plugins-bad. When "codec_data" info is present in caps structure,
element can be sure that it is dealing with a raw AAC stream and in this case
it needs to initialize the underlying OpenMAX codec itself (by using
OMX_SetParameter call I guess).


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