windows remote desktop frame rate setting

#Windows remote desktop frame rate setting driver

This worked for pre-Vista desktops, but it’s now few years since Windows switched from the obsolete memory rendering technique to a new hardware driven rendering and applications are starting to adapt.

#Windows remote desktop frame rate setting driver

Today most applications use hardware acceleration, but when you work via RDP a virtual (purely software) graphics driver is used to render your content. (The reason being that RDP is sending a lossless image and can’t real-time mpeg encode the picture because of CPU-power, latency in encoding and lossy encoding – so it has to use lossless compression that is easy on the CPU.)Ī secondary problem is GPU hardware. That should be enough for casual use, but not full screen video. Currently I have a 26/4Mb line (waiting for a 100/100Mb) at home, so the screen of my home computer is being sent to me on a 4Mb link. If it was over LAN then RDP would have no problem pushing a video, but over slower links you can notice each screen update. The problem is (for the most part) bandwidth. Since I spend most of my time in front of a computer I usually invest a fair amount of money when buying a new computer, so my home computer is often the powerful one. One screen for my laptop at work, and one screen with RDP home to a more powerful computer. Since some time back around 2000 I’ve been running a dual desktop configuration at work. NOTE: I have made new blog-post containing useful info about RDP 8.x (i.e.