3
2
I'm using RDP to Remote Desktop from a Windows 7 machine to another Windows 7 machine, so it's RDP 7. I've got the colour depth set at 32 bits and can confirm that 32 bit colour is working properly because I'm able to use Aero over the remote desktop connection which requires 32 bit colour. I also connected to a 2008 server box at 32 bits and confirmed from the server side that the connection was using 32 bit colour.
The problem is images still look crap and have all sorts of colour banding as if they were still being sent as 16 bit images, even though the connection is supposedly 32 bits. I'm planning on using the connection for image processing and as such need the full colour depth in the images otherwise the environment is useless to me.
Ideas or experiences?
don't use RDP for graphics processing...seriously. if you have some MONSTER computer that you want to use for graphics processing on the local lan, i would use a different desktop grabbing application(rdp might be set to a particular bit display but then try to "optimize" the graphic to make network traffic skinny). if it's going over a wan link - bad idea. – RobotHumans – 2010-11-08T05:17:32.220
Also I need the dual screen ability of RDP. – Matthew Hall – 2010-11-08T05:45:51.250
If you are domain joined, a System Administrator may have set a Group Policy setting that forces it to something less than 32-bit. They might do that for saving bandwidth, etc. – vcsjones – 2010-11-08T06:11:09.337
2Rather than relying on the presence of Areo to check colour depth, why not check the desktop properties to get the depth directly (they''ll be readonly)? Both the server and client limits are applied, if the client asks for 24bpp, but the server limits to 16 (the default) then you'll get 16. – Richard – 2010-11-08T06:58:51.617