Hi,
0. Add 'no codec' as a supported codec - pass a (PCM?) stream directly
from the server to client (not sure if it's a cross platform solution).
This works today ;)
If no codec capability is present raw pcm samples go over the wire.
spice-gtk sound worked that way before celt support was
On Mon, May 9, 2011 at 11:07 AM, Christophe Fergeau wrote:
> Hi Emre,
>
> On Sun, May 08, 2011 at 04:47:33PM +0400, Emre Erenoglu wrote:
>> Thanks Alon, I know the history, I had a small hope that situation could
>> have been resolved by now. Anyway, I understand that spice is not compatible
>> wi
On 09/05/2011 12:51, Alon Levy wrote:
On Mon, May 09, 2011 at 11:22:03AM +0200, Christophe Fergeau wrote:
On Mon, May 09, 2011 at 12:14:52PM +0300, Alon Levy wrote:
On Mon, May 09, 2011 at 11:04:47AM +0200, Christophe Fergeau wrote:
Hi,
On Sun, May 08, 2011 at 03:38:17PM +0300, Alon Levy wrot
On Mon, May 09, 2011 at 11:22:03AM +0200, Christophe Fergeau wrote:
> On Mon, May 09, 2011 at 12:14:52PM +0300, Alon Levy wrote:
> > On Mon, May 09, 2011 at 11:04:47AM +0200, Christophe Fergeau wrote:
> > > Hi,
> > >
> > > On Sun, May 08, 2011 at 03:38:17PM +0300, Alon Levy wrote:
> > > > This pro
On Mon, May 09, 2011 at 12:14:52PM +0300, Alon Levy wrote:
> On Mon, May 09, 2011 at 11:04:47AM +0200, Christophe Fergeau wrote:
> > 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
> >
On Mon, May 09, 2011 at 11:04:47AM +0200, Christophe Fergeau wrote:
> 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
Hi Emre,
On Sun, May 08, 2011 at 04:47:33PM +0400, Emre Erenoglu wrote:
> Thanks Alon, I know the history, I had a small hope that situation could
> have been resolved by now. Anyway, I understand that spice is not compatible
> with 0.10 and therefore we can't link it to the celt in our repository
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. T
On Sun, May 8, 2011 at 4:38 PM, Alon Levy wrote:
> On Sun, May 08, 2011 at 03:43:21PM +0400, Emre Erenoglu wrote:
> > Dear Developers,
> >
> > I'm the package maintainer for some virtualization related packages in
> > Pardus distribution. I would like to take spice into our package
> > repositori
On Sun, May 08, 2011 at 03:43:21PM +0400, Emre Erenoglu wrote:
> Dear Developers,
>
> I'm the package maintainer for some virtualization related packages in
> Pardus distribution. I would like to take spice into our package
> repositories, however, I'm facing an issue with the celt package.
>
> I
Dear Developers,
I'm the package maintainer for some virtualization related packages in
Pardus distribution. I would like to take spice into our package
repositories, however, I'm facing an issue with the celt package.
I'm sure you're aware of the issue. Spice is depending on celt 0.5.1, while
we
11 matches
Mail list logo
