[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

--- Comment #7 from Andrzej K. Haczewski <ahaczewski at gmail.com> 2010-07-14 09:16:10 UTC ---
(In reply to comment #6)
> Sorry, I might have misunderstood: getting the LAOS/LATM parsing out of gstfaad
> into aacparse?
>
> Then one would use gstfaad only for decoding what faad supports (ADTS, raw). In
> case of different AAC profiles, user would use aacparse+faad?
> 
> I'll gladly test any patch and help you if it is decided to go on with this.

Yes, more or less that's what I'd like to have in the end: parsing of different
AAC streams, so that other elements could use that, not only faad decoder.

I'm working now on finalizing the aacparse patch so it gets LOAS/LATM right,
but I'm not sure how it should handle multiple streams in LATM. If the output
from aacparse is to be LOAS/LATM then there's no problem, but for raw AAC
output that is needed by FLV should I create more src pads?

Also, if an element like flvmux requires raw AAC stream should it be able to
negotiate it with aacparse? That's also a case for faad, which might want to
get raw AAC data from LATM: should it negotiate or should it be a property in
aacparse ("raw-output" in example)?

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