[FFmpeg-devel] Is it ok to add G.722.1 decoder as external lib?

Hyun Yoo easetheworld at gmail.com
Wed Sep 18 08:34:59 EEST 2019


According to wiki, g.722.1 is not variants of G.722 and
they use different patented compression technologies.

There is a reference code in ITU-T
https://www.itu.int/rec/T-REC-G.722.1-200505-I/en
and the freeswitch version is a wrapper with cleaner api.
(I recently contacted the freeswitch guy and got permission)
so I think the source code is ok to use.

The codec itself is licensed by Polycom so I agreed it should be notified
to user.
How can I mark the new external codec as “nonfree” in configure?
Any document about that?

I also found old thread about "Differences between Cook and G.722.1"
https://lists.ffmpeg.org/pipermail/ffmpeg-devel/2007-May/034060.html
I can find CODEC_ID_COOK but not G722_1 so maybe they turned out to be
different.

2019년 9월 17일 (화) 오후 5:27, Moritz Barsnick <barsnick at gmx.net>님이 작성:

> On Tue, Sep 17, 2019 at 09:52:48 +0200, Carl Eugen Hoyos wrote:
> > > But that said: ffmpeg already has a native G.722 encoder (and decoder),
> >
> > See: https://en.wikipedia.org/wiki/G.722.1
> > The numbering...
>
> Yes, my next paragraph referred to that. But I just figured out that
> G.722 was apparently differently licensed, and therefore it was
> probably quite straightforward to port libg722 to ffmpeg, unlike this
> G.722.1 code or codec.
>
> > (The library is non-free and we cannot change that.)
>
> Indeed.
>
> Moritz
> _______________________________________________
> ffmpeg-devel mailing list
> ffmpeg-devel at ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>
> To unsubscribe, visit link above, or email
> ffmpeg-devel-request at ffmpeg.org with subject "unsubscribe".


More information about the ffmpeg-devel mailing list