Re: [Jack-Devel] Switch from CELT to Opus in JACK1/JACK2 sources

> 
> 
>> I think we should clearly avoid degrading the performances (and
>> adding code complexity with any buffering scheme..) because of this
>> kind of reasons.  Going from CELT to Opus is not "our" choice, so we
>> should keep pushing to keep the best we can.
> 
> 
> The question boils down to this:
> 
>  A)  use standard opus modes
>     + makes some opus-devs and packagers happy
>     - adds latency
>     - adds code-complexity to jack (re-framing to N*120 frames)
>     + possibly improved compressed sound-quality
> 
>  B) use opus custom-modes.
>     - may not be available on all systems
>       (requires libopus to be compiled with --enable-custom-modes)
>     + no additional latency
>     + simple code in jack
>     - possibly substandard compression quality
>       (should still be better than celt, though)
> 
> 
> I'm leaning towards (B). Favor simplicity and fixed low latency over
> quality when using compression. -- Users who require high-quality or
> loss-less transmission won't be using Celt, Opus or whatever, anyway.
> 
> (A) Re-framing the buffers, modifying the port-latencies on netjack, etc
> are no complicated tasks per se. ..but taking care of all details and
> integration is certainly not trivial.
> 
> ciao,
> robin
> 

+1 for B)

(BTW on OSX and Windows, I will certainly compile and link Opus statically anyway...)

Stéphane 

1347037078.32312_0.ltw:2,a <1DEC0898-3C54-4DA6-848E-9B217147C55C at grame dot fr>