From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Jyoim-00054f-Cv for qemu-devel@nongnu.org; Wed, 21 May 2008 09:51:12 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Jyoik-000542-P2 for qemu-devel@nongnu.org; Wed, 21 May 2008 09:51:12 -0400 Received: from [199.232.76.173] (port=58489 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Jyoik-00053z-LD for qemu-devel@nongnu.org; Wed, 21 May 2008 09:51:10 -0400 Received: from py-out-1112.google.com ([64.233.166.177]:50845) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Jyoik-0006QJ-He for qemu-devel@nongnu.org; Wed, 21 May 2008 09:51:10 -0400 Received: by py-out-1112.google.com with SMTP id p76so163265pyb.10 for ; Wed, 21 May 2008 06:51:09 -0700 (PDT) Message-ID: <483428C5.90508@codemonkey.ws> Date: Wed, 21 May 2008 08:51:01 -0500 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] Sensible VNC encodings References: <4833845C.9000603@codemonkey.ws> <48341E3D.70102@codemonkey.ws> <48342542.4070205@codemonkey.ws> <20080521134504.GB15210@shareable.org> In-Reply-To: <20080521134504.GB15210@shareable.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Jamie Lokier wrote: > Anthony Liguori wrote: > >> I really don't like the idea of using a lossy encoding though. >> > > Lossy encoding sounds very useful if you're on a very slow link and it > would take 30s to display a major update even with the most brilliant > of lossless compressions. Having a blurry, progressively updated > image until it's exact would sometimes be useful. > VNC has a builtin notion of "lossy" encoding via SetPixelFormat. You can use it to reduce the overall color depth. Hextile et. al. are also paletted encodings so I doubt there are a lot of circumstances where jpeg compression really saves you anything. If someone wants to actually do some experiments and can post numbers where jpeg compression provides the best bandwidth/quality, I'd be happy to implement it. FWIW, Tight is not part of the RFB spec. ZRLE (which is meant to replace it) does not support JPEG encoding at all. Regards, Anthony Liguori > -- Jamie > > >