Hi, On Sun, May 08, 2011 at 03:38:17PM +0300, Alon Levy wrote: > This problem has been raised multiple times on the list, you should read the > archives. To recap: historically when spice had to choose a codec it chose the > current celt then, 0.5.1. That celt is not compatible with newer celts. The > decision was to wait for celt's on wire format to stabilize. This hasn't > happened > yet (perhaps it will happen soon). It is however possible to introduce support > for multiple codecs and have the client and server negotiate. This will still > not > allow a celt 0.10.0 linked spice server to connect to celt 0.5.1 client, or > vice > versa.
Celt 0.11.1 release announcement says "CELT 0.11.0 (originally not announced) and 0.11.1 has been released with a focus on freezing the bit-stream and updating the API. The bit-stream is now in "soft-freeze" state meaning there is an attempt to keep it fixed, but some bugs may force changes" so if some codec negociation was introduced, I'd target celt 0.11.1+ (explicitly noting that celt 0.11.1+ support may be broken at any time if celt bitstream format has to change before it's officially frozen). Christophe
pgpgJfcFW61EE.pgp
Description: PGP signature
_______________________________________________ Spice-devel mailing list Spice-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/spice-devel
