![]() ![]() MJPEG wont be used unless it is explicitly requested. If the client supports H.264 decoding (by means of the hardware or by codec libraries), then H.264 will be chosen, otherwise VP8 encoding is always used. This is one feature which I am sure other remote access products don’t have. This guide is an introduction to the NoMachine User Interface (UI) in NoMachine software version 7 or higher. This applies a filter to improve the quality of the image, but consumes more CPU. Other ways that you could further improve CPU usage is by disabling “client side image post-processing”. We are already working on improving how NoMachine handles the encoding of multi-monitors, so that each monitor is encoded separately and content is transmitted separately to the client. This behaviour is becoming less convenient nowadays what with monitor resolutions getting larger. This is to ensure a smoother experience in visualizing the content when you’re switching among monitors. In its current design NoMachine sends the content of all the remote monitors even though you may be viewing the content of one of the displays only client-side. This should help diminish the use of the CPU. You could try using H.264 software encoding, you can follow the instructions here. ![]() It would seem that the HW is to blame, not really NoMachine. You wrote that disabling hardware acceleration (decoding) on the client, the performance improves. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |