UltraVNC 1.2.1.1 RC3 - Last call

[Rudi De Vos]

I'm gonna prepare release 1.2.1.1 next week ( setup,msi,binzip)
Looks like it's a stable release

[WAJIM]

Why new versions 1.2.0.9-1.2.1.1rc3 always auto-selects ZRLE and never Hextile for high-speed local connections (100 mbps)?
1.2.0.1-1.2.0.6 -> auto-selects to Hextile
1.2.0.9-1.2.1.1rc3 -> auto-selects to ZRLE

WinXP 32bit - 1.2.1.1rc3:
http://rgho.st/8rsYp8Q4P/image.png
http://rgho.st/6hdzRzy2G/image.png

[Rudi De Vos]

Encoder depend on multiple parameters.
network/cpu server/cpu viewer
Some parameters to select the required encoder changed to avoid fast encoder switching.

If you know what encoder you want based on your network knowledge it alwast better to manual select the encoder
and save it as default.

This avoid a slow startup because multiple encoders send the same data the determ the speed and guested required encoder.

[WAJIM]

network/cpu server/cpu viewer

Client - Phenom2 1100T (6 cores 6 threads 3800 Mhz)
Server - Atom N2600 (2 cores 4 threads 1600 Mhz)
Network - Ethernet 100 mbps
Not enough for u2/Hextile?

Normal , if your viewer support ultra2 encodings it is used from 20.000 to 256
if not zrle is used when speed drop below 10000

What about Hextile auto-selection? All old versions (1.0.5.3-1.2.0.6) always use Hextile for my config.

Ahother question - why 1.2.1.1rc3 can't use u2 encoding in manual mode? ZRLE selects instead of u2!
UVNC: Server (XP Embedded 32bit) = Client (XP Pro 32bit) = 1.2.1.1rc3
http://rgho.st/6FRG7yNcy/image.png
http://rgho.st/7t5fgchKz/image.png

[WAJIM]

It seems that u2 encoding not supports 16-bit screen color depth on server side (XP 32-bit). Is it right?
When color depth = 32-bit -> u2 works fine (auto and manual)
When color depth = 16-bit -> u2 falls to ZRLE (auto and manual)

[Rudi De Vos]

Correct u2 encoding is a jpeg encoding and this works only on 32bit.
In case of 16bit we falback to other encoders.

Thanks for the tip... i can test what i want in 32bit and never agree with you.
I will check 16bit, it' more natural to fallback to hextile if u2 is disabled.

[WAJIM]

I will check 16bit, it' more natural to fallback to hextile if u2 is disabled.

Yes, thanks!

But its better if user can also change auto-select logic selector (ini):
OLD (<= 1.0.2.6) - ZRLE / hextile (16/32-bit)
NEW (> 1.0.2.6) - ZRLE / (u2 if 32-bit / hextile if 16-bit)

I don't like u2 because of lossy. Its good for video/demos but not for remote work.

[Rudi De Vos]

You can set a higher jpeg quality to minimize lossy against size.

[WAJIM]

You can set a higher jpeg quality to minimize lossy against size.

Yes, but even when jpeg q=9 compression artifacts appears.

[Rudi De Vos]

Yes, you need to use what you likes most.
It's always a trade between speed/size and quality.
You can customize the defaults.

Howto change defaults.
make your option selections
[v] save as default
press connect

Next time you start the viewer use your customized defaults.

[WAJIM]

New (1.2.0.9+) encoder auto-selection logic is very strange.
All viewer presets (slow/modem/medium/lan/ultra) are lossless (zrle/hextile/ultra).
But auto mode can select lossy (u2) encoder, u2 not included in presets. This is not logical.