[CELT-dev] celt-dev Digest, Vol 34, Issue 2
atascon at gmail.com
Tue Jul 12 15:55:01 PDT 2011
So, once all those things are in place what Andrew says WILL happen?
I think plans as important as that deserves an announcement.
Roadmap for the project? Future directions for the main committers?
Are there patent issues?
Date: Mon, 11 Jul 2011 20:45:14 -0400
> From: Gregory Maxwell <gmaxwell at gmail.com>
> Subject: Re: [CELT-dev] Mailing list and project shutdown
> To: Andrew Lentvorski <bsder at allcaps.org>
> Cc: celt-dev at xiph.org
> <CAAS2fgSShUwdzPsGxPYy2cb42fRO0Pd9_uSc1Fyey1KWBGZBYA at mail.gmail.com
> Content-Type: text/plain; charset=UTF-8
> On Mon, Jul 11, 2011 at 6:02 AM, Andrew Lentvorski <bsder at allcaps.org>
> > If everything has moved and this mailing list has gone dormant, how
> > about an official announcement as well as official pointers to the new
> > stuff?
> > It would also be good to have some sort of "migration document" given
> > that you have to do specific things to OPUS in order to get the old CELT
> > behavior.
> Hm. I think we're sort of in a weird limbo right now.
> The Opus codebase has major regressions in everything outside of the
> codec itself: build system, tests, tools useability, API, and
> licensing status all have issues that need to be cleared up.
> Once the IETF bitstream standardization hurdles are out of the way it
> will be easier to dedicate time to getting these issues resolved.
> Until then I'd feel bad making a heavy-handed push to the new stuff
> when it's not currently a drop in replacement due to these issues.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the celt-dev