From: Corentin Chary <corentin.chary@gmail.com>
To: Alexander Graf <agraf@suse.de>
Cc: Anthony Liguori <aliguori@linux.vnet.ibm.com>,
Qemu-development List <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: [PATCH 2/5] vnc: JPEG should be disabled if the client don't set tight quality
Date: Fri, 4 Jun 2010 15:48:37 +0200 [thread overview]
Message-ID: <AANLkTilXjLGsv4ESyCGh4zbDwhNIMEwXJrWoNPWj9sTe@mail.gmail.com> (raw)
In-Reply-To: <8322C67B-B7FB-4D94-A6BB-6490A4B34879@suse.de>
>
> The tight quality level is a slider on most clients. A user doesn't know when it starts being lossy. He also can only choose 0 as the lowest (iirc). And IIRC the X tightvnc client also always sent the quality level.
>
> Alex
>
>
You can use -nojpeg for that. Most vnc clients have this options.
--
Corentin Chary
http://xf.iksaif.net
next prev parent reply other threads:[~2010-06-04 13:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-04 13:18 [Qemu-devel] [PATCH 0/5] vnc updates and ui move Corentin Chary
[not found] ` <1275657527-26032-5-git-send-email-corentincj@iksaif.net>
2010-06-04 13:18 ` [Qemu-devel] Re: [PATCH 4/5] ui: move all ui components in ui/ Alexander Graf
2010-06-04 14:23 ` Corentin Chary
2010-06-04 13:18 ` [Qemu-devel] [PATCH 1/5] vnc: tight: add JPEG and gradient subencoding with smooth image detection Corentin Chary
2010-06-04 13:18 ` [Qemu-devel] [PATCH 2/5] vnc: JPEG should be disabled if the client don't set tight quality Corentin Chary
2010-06-04 13:16 ` [Qemu-devel] " Alexander Graf
2010-06-04 13:19 ` Anthony Liguori
2010-06-04 13:20 ` Alexander Graf
2010-06-04 13:48 ` Corentin Chary [this message]
2010-06-04 13:52 ` Alexander Graf
2010-06-04 14:22 ` Corentin Chary
2010-06-04 13:18 ` [Qemu-devel] [PATCH 3/5] vnc: add lossless option Corentin Chary
2010-06-04 13:17 ` [Qemu-devel] " Alexander Graf
2010-06-04 13:20 ` Anthony Liguori
2010-06-04 13:18 ` [Qemu-devel] [PATCH 5/5] vnc: rename vnc-encoding-* vnc-enc-* Corentin Chary
2010-06-04 13:18 ` [Qemu-devel] " Alexander Graf
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=AANLkTilXjLGsv4ESyCGh4zbDwhNIMEwXJrWoNPWj9sTe@mail.gmail.com \
--to=corentin.chary@gmail.com \
--cc=agraf@suse.de \
--cc=aliguori@linux.vnet.ibm.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).