Στις 26/03/2012 10:05 πμ, ο/η Alkis Georgopoulos έγραψε:
By default, X_COLOR_DEPTH is 32 for thin clients, which means that a
320x240 youtube video needs 73.728.000 bps bandwidth (30 fps, 32 bpp).
Setting X_COLOR_DEPTH=16 for thin clients makes that video need exactly
half the bandwidth, i.e.
Στις 27/03/2012 09:34 πμ, ο/η Ben Green έγραψε:
Almost definitely, unless it's a really old LCD one. You can see the
difference even from the default LDM login screen. At 16-bit, the blue
background is noticeably barred with distinct colour bands.
$ file
Στις 27/03/2012 10:58 πμ, ο/η Ben Green έγραψε:
That's simply not true Alkis, with 16-bit colour I see bands, with
32-bit no bands. I can provide pictures if you like. Its not a
complaint about the picture quality, I'm just saying the difference is
very visible.
Please see the next paragraph
Quoting Alkis Georgopoulos alk...@gmail.com:
That's why I'm insisting that any comparison should be done after login.
I wasn't trying to compare image quality between the two modes, and
I'm completely aware rendering will be different with different
renderers. I'm not trying to make any
A person contacted me off-list (as he had some problems posting to the
list), and reported that he tried X_COLOR_DEPTH=16, and it made XVideo
not working for him with the following chipset:
Intel Corporation 82865G 8086:2572 (rev 02)
Kernel driver in use: i915
Kernel modules: i915
That
By default, X_COLOR_DEPTH is 32 for thin clients, which means that a
320x240 youtube video needs 73.728.000 bps bandwidth (30 fps, 32 bpp).
Setting X_COLOR_DEPTH=16 for thin clients makes that video need exactly
half the bandwidth, i.e. 36.864.000 bps.
Of course that doesn't only affect
Le lundi 26 mars 2012 09:05:42 Alkis Georgopoulos, vous avez écrit :
By default, X_COLOR_DEPTH is 32 for thin clients, which means that a
320x240 youtube video needs 73.728.000 bps bandwidth (30 fps, 32 bpp).
Setting X_COLOR_DEPTH=16 for thin clients makes that video need exactly
half the
26.03.2012 10:19, Xavier Brochard kirjoitti:
I allways set X_COLOR_DEPTH=16, to save bandwith and CPU. Users never
complains, even when browsing high quality pictures (on low quality
screens...).
I aprove.
Same here. Go ahead.
Best Regards Asmo Koskinen.
Alkis Georgopoulos schrieb am 26.03.2012 09:05:
So I propose a change in upstream LTSP to set X_COLOR_DEPTH=16 by
default, if:
* LTSP_FATCLIENT is not set (fat clients would still default to 32),
* LOCAL_APPS_MENU is not set (so 32 for localapps browsers too),
* X_COLOR_DEPTH is not
Sounds OK to me, makes a lot of sense. It can easily be changed by those
who need the better definition. I don't use video on my thin clients.
Peter
On Mon, Mar 26, 2012 at 9:05 AM, Alkis Georgopoulos alk...@gmail.comwrote:
By default, X_COLOR_DEPTH is 32 for thin clients, which means that a
X_COLOR_DEPTH=16 here too. The extra resolution (which is hardly
visible) doesn't outweigh the performance hit (which is very much
visible). I think it's a good idea if it becomes default. :-)
Met vriendelijke groet,
Jan Middelkoop
Recreatie en Zorg Groep B.V.
--
Website:
Quoting Jan Middelkoop j...@recreatie-zorg.nl:
If not, then I'll implement an X_COLOR_DEPTH=auto instead, which would
give the above behavior (16 on thins, 32 on fats/localapps) only when
requested from lts.conf.
To be more positive in my response, the above would be an excellent addition.
Στις 26/03/2012 12:04 μμ, ο/η Ben Green έγραψε:
If not, then I'll implement an X_COLOR_DEPTH=auto instead, which would
give the above behavior (16 on thins, 32 on fats/localapps) only when
requested from lts.conf.
To be more positive in my response, the above would be an excellent
Quoting Alkis Georgopoulos alk...@gmail.com:
Στις 26/03/2012 12:04 μμ, ο/η Ben Green έγραψε:
If not, then I'll implement an X_COLOR_DEPTH=auto instead, which would
give the above behavior (16 on thins, 32 on fats/localapps) only when
requested from lts.conf.
To be more positive in my
hi,
On Mon, 26 Mar 2012 12:44:04 +0300
Alkis Georgopoulos alk...@gmail.com wrote:
What's the negative side of making that the default, so that the
average user wouldn't have to read all lts.conf options, detect that
one, create an lts.conf and set it there, before enjoying its speed
benefits?
Στις 26/03/2012 12:54 μμ, ο/η Ben Green έγραψε:
I don't think this setting -color depth- should be conditional, if
there's going to be a default, it should be the same for all,
otherwise it gets confusing.
I strongly disagree; the default should be to try hard to work in all
cases. That's
Quoting Alkis Georgopoulos alk...@gmail.com:
Στις 26/03/2012 12:54 μμ, ο/η Ben Green έγραψε:
I don't think this setting -color depth- should be conditional, if
there's going to be a default, it should be the same for all,
otherwise it gets confusing.
I strongly disagree; the default should
Στις 26/03/2012 02:07 μμ, ο/η Ben Green έγραψε:
The situations where having =auto as the default would cause problems are:
1. Where clients don't support 16-bit colour and are not using local apps.
Have you ever actually seen clients that don't support 16 bpp modes, or
is that theoretical?
Quoting Alkis Georgopoulos alk...@gmail.com:
Στις 26/03/2012 02:07 μμ, ο/η Ben Green έγραψε:
The situations where having =auto as the default would cause problems are:
1. Where clients don't support 16-bit colour and are not using local apps.
Have you ever actually seen clients that don't
Στις 26/03/2012 01:50 μμ, ο/η Oliver Grawert έγραψε:
we had it as default for years, you should dig on launchpad iirc there
were bugs that made us change to 32 ...
Oli the hardcoded X_COLOR_DEPTH=16 was removed in commit
http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk/revision/979
hi,
On Mon, 26 Mar 2012 15:14:02 +0300
Alkis Georgopoulos alk...@gmail.com wrote:
2) X without a -depth parameter at all.
and if that wouldnt work this would be a reason to shout at the xorg
devs and file a bug, xorg autodetects the depth from the EDID data the
panel/screen provides.
ciao
hi,
On Mon, 26 Mar 2012 15:23:35 +0300
Alkis Georgopoulos alk...@gmail.com wrote:
Oli the hardcoded X_COLOR_DEPTH=16 was removed in commit
http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk/revision/979
with no bug reports mentioned.
oops, then i remembered it the wrong way round,
Quoting Oliver Grawert o...@ubuntu.com:
oops, then i remembered it the wrong way round, sorry.
still, as mentioned in my other post, we should just rely on xorg
auto detection unless you really need to force the lower depth ...
(which i belive is what happens atm)
Having been given some
On Mon, Mar 26, 2012 at 03:14:02PM +0300, Alkis Georgopoulos wrote:
Στις 26/03/2012 02:07 μμ, ο/η Ben Green έγραψε:
The situations where having =auto as the default would cause problems are:
1. Where clients don't support 16-bit colour and are not using local apps.
Have you ever actually
After some IRC discussion, here's what will be implemented:
By default (X_COLOR_DEPTH= or X_COLOR_DEPTH=smart), thin clients get
16 bpp, and fat clients get the xorg default depth (usually 32).
No special exceptions for thins with localapps.
X_COLOR_DEPTH=auto reverts to the old behavior, i.e.
Στις 26/03/2012 08:25 μμ, ο/η Alkis Georgopoulos έγραψε:
After some IRC discussion, here's what will be implemented:
...
Sorry, some code paths depended on X_COLOR_DEPTH being numerical if
unset, so the following got committed instead:
On 26/03/2012, at 7:07 PM, ltsp-discuss-requ...@lists.sourceforge.net wrote:
By default, X_COLOR_DEPTH is 32 for thin clients, which means that a
320x240 youtube video needs 73.728.000 bps bandwidth (30 fps, 32 bpp).
Setting X_COLOR_DEPTH=16 for thin clients makes that video need exactly
27 matches
Mail list logo
