All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Sensible VNC encodings
Date: Wed, 21 May 2008 08:51:01 -0500	[thread overview]
Message-ID: <483428C5.90508@codemonkey.ws> (raw)
In-Reply-To: <20080521134504.GB15210@shareable.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
>
>
>   

  reply	other threads:[~2008-05-21 13:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-21  1:20 [Qemu-devel] Sensible VNC encodings Johannes Schindelin
2008-05-21  2:09 ` Anthony Liguori
2008-05-21  8:12   ` Johannes Schindelin
2008-05-21 13:06     ` Anthony Liguori
2008-05-21 13:14       ` Johannes Schindelin
2008-05-21 13:36         ` Anthony Liguori
2008-05-21 13:45           ` Jamie Lokier
2008-05-21 13:51             ` Anthony Liguori [this message]
2008-05-21  5:55 ` Alexander Graf
2008-05-21  8:08   ` Johannes Schindelin
2008-05-21 13:02   ` Daniel P. Berrange
2008-05-21 13:10     ` Johannes Schindelin
2008-05-21 13:47       ` Anthony Liguori

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=483428C5.90508@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.