NoMachine has algorithms to correct such color shift ( ), but those are enabled only for quality level 5 or above (from the middle of the Quality slider to the right). You can do that also from NoMachine user interface (‘Take the statistics’), or with the ‘ping’ command.Ī last note about Capture2.png: that blurriness around edges of coloured images is due to the chroma subsampling introduced by the encoder.
Maybe it’s worth checking the network latency too (round trip time), if you didn’t do already (VPN could play a role here). In your case, I think that the best option is to act on the Quality slider only to find the best balance between quality and responsiveness, assuming that the lack of responsiveness is only, or mostly, due to limited bandwidth. Those settings won’t change the final quality, they only affect the progression and the speed how the target quality is reached. In fact checking those boxes will limit the ability of congestion control algorythms to adapt to detected network conditions by adjusting image quality dinamically. There are more than 100 alternatives to NoMachine for a.
If there is a very limited bandwidth, I wouldn’t touch the settings at point 1 and 2, but rather let NoMachine do its job at controlling congestion. NoMachine is described as 'NX is an enterprise-class solution for secure remote access, desktop virtualization, and hosted desktop deployment built around the self-designed and self-developed NX suite of components' and is a very popular Remote Desktop tool in the network & admin category.
0 kommentar(er)
