Notice that the code is under the MPL. AFAIK the MPL is LGPL compatible so
including it would be ok.

The MPL is not LGPL-compatible, that is, in the way necessary to combine code.

I assume that means a whole plugin based on this code would need to be MPL'd?  What implication does 
that have?

AFAICT, MPL-licensed plugins would be equivalent to LGPL-licensed plugins in
most licensing aspects.  The biggest problem would be answering questions about
it. :)

I'd prefer not to have MPL plugins in gst-plugins, mainly because we're
currently trying to get rid of all GPL plugins.

Would it still be nice to have this encoder? E.g. nothing provides this yet?

Blocking on plugins split.

there is an experimental RFC 3640 mpeg4-generic payload encoder in CVS that should be able to do aac-hbr.

ping?

closing. reopen if the proposed generic payloader does not work.