Hi, ALL
On Thu, Nov 18, 2010 at 12:39 AM, Gerd Hoffmann wrote:
>> There isn't going to be a Debian release with spice in it for around
>> 2 years now in the best case, so if there isn't another suitable choice
>> available by then, then something worse than this has gone badly wrong.
>
> Two year
Hi
2010/11/17 Ron :
> On Wed, Nov 17, 2010 at 03:48:36PM +0100, Gerd Hoffmann wrote:
>> On 11/17/10 13:04, Ron wrote:
> Why not just let systems negotiate the best codec they both know?
That was a bit my goal with this patch:
http://gitorious.org/~elmarco/spice/elmarco-spice/commit/e310493a3e5a28
Hi,
If you don't want package celt 0.5.1 -- fine. You can patch your
spice server and client to just not signal the celt capability, and
they will interoperate just fine with everybody else using raw
uncompressed audio. But IMHO it would be stupid to not support
audio compression in your spi
On Wed, Nov 17, 2010 at 03:48:36PM +0100, Gerd Hoffmann wrote:
> On 11/17/10 13:04, Ron wrote:
> >Are you seriously telling me that you have no plan whatsoever for how
> >to transition from a random snapshot of an experimental codec,
>
> We can transition just fine. server + client can signal sup
On 11/17/10 13:04, Ron wrote:
Hi Hans,
Hans de Goede writes:
The if at all part depends on if it will be doable without too much
pain to support both celt-0.5.1 and celt "1.0" in the same binary.
Should work without major trouble, the symbols exported by the shared
library have a versioned
Hi,
On 11/17/2010 01:04 PM, Ron wrote:
Hi Hans,
Hans de Goede writes:
The if at all part depends on if it will be doable without too much
pain to support both celt-0.5.1 and celt "1.0" in the same binary.
This is important to us as we care a lot about protocol
compatibility.
Are you serious
Hi Hans,
Hans de Goede writes:
> The if at all part depends on if it will be doable without too much
> pain to support both celt-0.5.1 and celt "1.0" in the same binary.
> This is important to us as we care a lot about protocol
> compatibility.
Are you seriously telling me that you have no plan
Hi,
The reason spice is still using celt-0.5.1 is that celt as
a protocol / format is considered not finished yet by celt
upstream and thus the bitstream format may change (and does
change) with every new upstream release.
In order to provide compatibility between different spice
client and serv
8 matches
Mail list logo