[gstreamer-bugs] [Bug 615740] FAAD plugin do not handle AAC LATM transport format

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=615740
  GStreamer | gst-plugins-bad | git

Andrzej K. Haczewski <ahaczewski> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ahaczewski at gmail.com

--- Comment #5 from Andrzej K. Haczewski <ahaczewski at gmail.com> 2010-07-08 21:50:13 UTC ---
Hi guys,

I've also been working on AAC code for GStreamer lately, and it involves LOAS.
I've even posted to a mailing list a patch to extend aac typefind for LOAS
streams. I would love to coordinate with you.

My task at hand is a little different: I have LOAS stream, written by
commercial encoder, that I have to mux to FLV using gstreamer with video that
comes from another gstreamer pipeline. The hard part is demuxing LATM in LOAS
into raw AAC packets on one hand and reading and storing in "codec_data" field
in caps AudioSpecificConfig that comes with each AAC stream.

The first task was to recognize LOAS stream as it comes from FIFO through
simple filesrc. That's what my typefind patch is doing.
Next is to frame the LOAS packets for further processing, that's what I suppose
should be done by aacparse plugin which I'm currently working on. But I see
that in your patch you're doing exacly the same thing: parsing LOAS and getting
LATM out of it, along with AudioSpecificConfig.

How about getting the parsing part out so both aacparse and gstfaad could use
that without code duplication? Both plugins are in gst-plugins-bad module so it
might be a little easier, but I'm relatively new to GStreamer development
process, so I'd welcome suggestions from more experienced developers.

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.