On Wed, 11 Mar 2009, Adam Tkac wrote:
We should always send second preferred encoding to server in case
that server doesn't support JPEG. So, in theory, existing code will be
improved this way:
for speeds = 16Mbps client sends Raw, JPEG, hextile, zrle
for speeds 16Mbps client sends JPEG,
On Wed, 11 Mar 2009 15:35:29 +0100
Adam Tkac at...@redhat.com wrote:
If non-SIMD JPEG is not so slower than raw encoding we can prefer
Tight JPEG encoding all the time. Otherwise we can use JPEG on low and
medium bandwidth nets and raw on high bandwidth nets. I think that
current algorithm
Raw by itself is completely useless. However, using a combination of
Raw tiles and paletted tiles, both encoded using the Tight encoder, is
useful. TurboVNC 0.5 does that for its mathematically lossless modes.
What we found is that there is really no reason to use any encoder other
than the
