Wierd behavior
John Aldrich
JAldrich "at" covista.com
Wed Jan 5 11:15:01 2005
Ahh... I didn't know that. Thanks. OTOH, you know that 24 *is* a multiple of
8... Just not an even-numbered multiple, which I'm guessing is what you
meant. I'll give --depth 16bpp a shot next time.
-----Original Message-----
From: jeff oconnell [mailto:jeffo "at" rulez.com]
Sent: Tuesday, January 04, 2005 3:28 PM
To: John Aldrich
Cc: 'RealVNC List (E-mail)'; 'James Weatherall'; 'VNC List (E-mail)'
Subject: Re: Wierd behavior
because of memory alignment issues, you shouldn't use 24-bit color with
vnc.
using it will cause a significant performance issue.
you're better off using 16- or 32-bit ( multiples of 8 ).
j-
On Jan 4, 2005, at 1:31 PM, John Aldrich wrote:
> Actually, I'm running in 24-bit color in X. I like having maximum color
> depth when I'm on the local console. Would you like me to post my
> xorg.conf?
> :-)
>
> -----Original Message-----
> From: James Weatherall [mailto:jnw "at" realvnc.com]
> Sent: Tuesday, January 04, 2005 11:44 AM
> To: 'John Aldrich'; 'RealVNC List (E-mail)'
> Cc: 'VNC List (E-mail)'
> Subject: RE: Wierd behavior
>
>
> John,
>
> There's no such thing as "full colour mode" in X - that's a VNC Viewer
> option. Are you sure you're not doing the exact opposite of what I'm
> suggesting?
>
> To clarify:
> - Run your X server with -depth 16
> - Run your VNC Viewer with Low Colour or Medium Colour (not Full
> Colour)
>
> I'm a little surprised that your viewer doesn't just stay in low
> colour mode
> when you run it - AutoSelect will only switch to Full Colour if it
> thinks
> that the connection between the viewer and server is fast enough,
> which it
> evidently isn't in this case.
>
> Regards,
>
> Wez @ RealVNC Ltd.
>
>
>> -----Original Message-----
>> From: John Aldrich [mailto:JAldrich "at" covista.com]
>> Sent: 04 January 2005 16:18
>> To: 'James Weatherall'; 'RealVNC List (E-mail)'
>> Cc: 'VNC List (E-mail)'
>> Subject: RE: Wierd behavior
>>
>>
>> Well, I tried it and it does appear to be unbearably slow in
>> full color
>> mode.
>>
>> -----Original Message-----
>> From: James Weatherall [mailto:jnw "at" realvnc.com]
>> Sent: Tuesday, January 04, 2005 10:33 AM
>> To: 'John Aldrich'; 'RealVNC List (E-mail)'
>> Cc: 'VNC List (E-mail)'
>> Subject: RE: Wierd behavior
>>
>>
>> John,
>>
>> The problem is probably that in 8bpp mode, the X server will
>> be using a
>> colour palette, rathern than true-colour. When Mozilla is
>> selected, the
>> palette will switch to what Mozilla wants. When another app
>> is selected, it
>> will switch to that app's palette.
>>
>> I'm surprised that switching your server to 8bpp makes any noticable
>> performance difference. Are you sure you didn't mean to set
>> the VNC Viewer
>> to request low- or medium- colour, while leaving the server
>> to use 16bpp
>> internally?
>> Regards,
>>
>> Wez @ RealVNC Ltd.
>>
>>
>>> -----Original Message-----
>>> From: vnc-tight-list-admin "at" lists.sourceforge.net
>>> [mailto:vnc-tight-list-admin "at" lists.sourceforge.net] On Behalf
>>> Of John Aldrich
>>> Sent: 04 January 2005 14:10
>>> To: RealVNC List (E-mail)
>>> Cc: VNC List (E-mail)
>>> Subject: Wierd behavior
>>>
>>> I'm using TightVNC on my machine at work and RealVNC on my
>>> linux box at
>>> home. Here's the script I use to launch the VNC Server:
>>> vncserver -depth 8bpp -geometry 1024x768 -nevershared -localhost
>>>
>>> For some reason, whenever I switch to an active Mozilla
>>> window, the display,
>>> except for the active Mozilla window, goes green. When I
>>> switch to any other
>>> window, it goes back to normal colors.
>>>
>>> My window manager on the linux box (Fedora Core 3) is KDE.
>> I've got a
>>> RivaTNT video card there, and I'm assuming that, since I
>>> didn't load the
>>> Riva TNT video drivers, that I'm not using those drivers.
>>>
>>> Any ideas why it's behaving this way? BTW, the 8-bit color is
>>> for speed
>>> reasons.
>>>
>>> Since this is mixing TightVNC and RealVNC I'm sending to both
>>> lists. BTW,
>>> the behavior is the same whether I'm using TightVNC or
>> RealVNC for the
>>> client. Also, since I didn't have this problem under RH9 (previous
>>> incarnation of the box that I'm connecting to) I'm assuming
>>> it's something
>>> to do with the VNC Server. OTOH, I'm using a newer version of
>>> KDE and other
>>> things are new as well (same hardware, just newer versions
>> of all the
>>> software) it could be something else as well.
>>> John
>>>
>>>
>>> -------------------------------------------------------
>>> The SF.Net email is sponsored by: Beat the post-holiday blues
>>> Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
>>> It's fun and FREE -- well,
>> almost....http://www.thinkgeek.com/sfshirt
>>> ___________________________________________________________
>>> TightVNC mailing list, VNC-Tight-list "at" lists.sourceforge.net
>>> To change your subscription or to UNSUBSCRIBE, please visit
>>> https://lists.sourceforge.net/lists/listinfo/vnc-tight-list
> _______________________________________________
> VNC-List mailing list
> VNC-List "at" realvnc.com
> To remove yourself from the list visit:
> http://www.realvnc.com/mailman/listinfo/vnc-list
>
>
> -------------------------------------------------------
> The SF.Net email is sponsored by: Beat the post-holiday blues
> Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
> It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
> ___________________________________________________________
> TightVNC mailing list, VNC-Tight-list "at" lists.sourceforge.net
> To change your subscription or to UNSUBSCRIBE, please visit
> https://lists.sourceforge.net/lists/listinfo/vnc-tight-list