Fred,
The Tight encoding was superceded in VNC release 3.3.4, which introduced
automatic encoding selection and the new ZRLE encoding. ZRLE provides
similar compression ratios to Tight (better in many cases) with less
processing overhead.
Cheers,
Dr. James Weatherall
RealVNC Ltd. - http://www.realvnc.com
---
Jeff Boerio wrote:
>
> Fred,
>
> This is a problem we have observed as well. I'm sure you notice that
> the CPU of your Windows VNC client goes through the roof as it attempts
> to do things such as redraws. It is not a network issue at all, it is
> in the Windows client itself.
>
> I spent a lot of time working with the folks at Real VNC on this
> problem, and you should see an dramatic improvement in their next
> release.
>
> - Jeff
Hi, Jeff,
I do recall reading in the archives that work was
being done with RealVNC folks to deal with it. I
don't recall if the exact CAD tool was mentioned.
I don't suppose that the change in code could be
easily incorporated into TightVNC? Tight encoding
really helps sometimes, and I'm not sure why
there hasn't been a merging of efforts.
Fred
--
Fred Ma, [EMAIL PROTECTED]
Carleton University, Dept. of Electronics
1125 Colonel By Drive, Ottawa, Ontario
Canada, K1S 5B6
_______________________________________________
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
