fra81

[fra81]

Hi TimeWalker,

the original FR has been dismissed because the OMX framework, from our tests, revealed to be not suitable at its current state. MMAL is indeed under evaluation by our development team and you are right that it can be an interesting alternative.

[fra81]

Hi Jon,

yes, it could definitely have to do with the settings on the Linux system, but we can check NoMachine logs for any issue. Please find instructions for server side logs at https://www.nomachine.com/DT11R00181#1.1 (debug level, steps 1 and 2, is not necessary) and for client side logs at https://www.nomachine.com/DT11R00181#2.2.

[fra81]

Thank you for reporting!

[fra81]

Hi PRosa,

please try to uncheck the following two options (one at a time) in the Server settings -> Performance tab of the computer where you are connecting to:

Use hardware encoding

Use acceleration for display processing

Does any of them help?

[fra81]

Hi,

the problems you see are not caused by NoMachine and are described in this article:

https://www.nomachine.com/AR03P00973

You may try with a dummy HDMI display adapter or the suggestions at point 2) of the article.

[fra81]

Hi zerocool,

please try to open Server settings –> Performance tab, on the server machine, and uncheck the ‘Use acceleration for display processing’ option. Let us know if that works.

[fra81]

Hi oscahie,

some changes have been done in the new version 7.4.1. Can you try to install it on the server machine?

[fra81]

Hi Coleman,

can you show the output of the ‘xset q’  command run inside the NoMachine session, when the screen is off?

[fra81]

Thanks for the logs. I can see there is a couple of issues that are fixed in NoMachine version 7, even though it’s not completely clear if they are related to the problem you are experiencing. So please upgrade also the server side to version 7 (you are using there version 6.13.1). If the problem is still reproducible, it would be great to have a new set of logs (client + server), so that we can rule out what is not related.

[fra81]

Hi psuresh431,

unfortunately I still can’t see the relevant logs, the ‘.nx’ directory in the home of user ‘nxuser’, on the Linux machine.

In the meanwhile, to narrow things down, you could try to disable hardware decoding (see https://www.nomachine.com/DT10R00167&dn=menu%20panel#5.7).

[fra81]

Hi,

CPU and memory usage are very low, so this really seems like a network problem. You can try to test this by using the ‘ping’ command towards the server during the slow down, or by transferring a file from the server to the client with any other tool. You can also try to gather NoMachine session statistics (run the menu panel within the session by Ctrl+Alt+0 or click on the page peel, click on Connection, then click on ‘Take the statistics’).

[fra81]

You seem to be experiencing this issue, already solved:

https://www.nomachine.com/TR06R09772

Therefore I suggest you to upgrade NoMachine to at least the last version 6, that is 6.13.1.

[fra81]

Hi,

this problem doesn’t depend on NoMachine. When the machine is headless, the GPU is not working normally and some apps may fail to render correctly. If you can’t attach a monitor, you can try to use a dummy display adapter (HDMI dummy plug). In the forum post you mention, the problem was solved by updating the graphics card’s drivers.

[fra81]

Hi,

please gather server side logs from wks 1 as explained in https://www.nomachine.com/AR10K00697, and client side logs from wks 2 as explained in https://www.nomachine.com/DT10O00163#2. You can send everything to forum[at]nomachine[dot]com. As a quick test, you can try to disable hardware encoding on the server:

1)  Edit the node configuration file, /usr/NX/etc/node.cfg

2) Uncomment and disable the EnableHardwareEncoding key:

EnableHardwareEncoding 0

[fra81]

Hi kvic,

I’m sure you guys are tech savvy enough to tune it suitable for the real-time nature of NoMachine.

that was exactly the problem. A proof of concept was implemented and tested in our labs, but unfortunately the VideoToolbox encoder can’t work in fully real-time mode. It needs to buffer at least two frames before producing an encoded frame in output. This one-frame delay is not acceptable in a real-time application like NoMachine, where minimizing the latency has the maximum importance. And our tests showed that clearly.

That said, if this limitation is removed in future, NoMachine will be ready to leverage hardware encoding on Mac.

[Author]

Posts