fra81

[fra81]

Hi,

in your case I would not change any of the default settings and let NoMachine adapt automatically to network conditions and available hardware resources, but with one exception: check the ‘Disable client side image post-processing’ option, that can be a heavy operation for your pi. Do not choose a specific codec or a specific frame rate, as NoMachine will use, at any moment, the best values to optimize performance.

 

[fra81]

Hi Jon,

just for the record, x264 is the software H.264 encoder, that doesn’t make use of the GPU, while you want to leverage the hardware encoding made available by the graphics card, namely NVENC. Hardware encoding support is not available in virtual desktop sessions when X11 vector graphics mode is enabled, as explained here. You can try to disable X11 vector graphics, so that hardware encoding will be used, and compare the results. It will mostly depend on the applications used.

The graphics card is also used to accelerate the applications running in the virtual desktop, by means of VirtualGL support (https://knowledgebase.nomachine.com/AR05P00982). This would only be useful if you run applications that use OpenGL for rendering.

[fra81]

Hi,

are you running a virtual desktop session or connecting to the physical display of the server? Do you confirm that the ‘setxkbmap -print’ command you showed is run in the remote session and not on the client machine? And could you run it also on the other side?

Logs can be useful. Please find how to gather them in https://knowledgebase.nomachine.com/AR10K00697. You can send them to forum[at]nomachine[dot]com.

Finally, please do a test. Instead of creating a new KDE desktop (assuming you are connecting to a virtual desktop, as per my initial question), try to ‘Create a new custom session’, by selecting to run the console ‘in a virtual desktop’. Is the keyboard layout correct there?

[fra81]

Hi Axel,

did you check the system logs? They could show some hints. You can use the ‘journalctl -b’ command for that. Feel free to send the output to us so we can check.

[fra81]

Hi,

we would need client and server logs to investigate. Please collect them by following the instructions in https://knowledgebase.nomachine.com/AR10K00697. You can send them to forum[at]nomachine[dot]com.

[fra81]

The current behaviour is in place since NoMachine version 7.0.

[fra81]

Can you try to measure your network latency, for example with the ping command? You can also try to send the logs to us, in case they would provide any hint. You can find instructions in https://knowledgebase.nomachine.com/AR10K00697 and send everything to forum[at]nomachine[dot]com, by referencing this thread.

[fra81]

There is no evidence of a NoMachine problem in the logs, so this really looks like a problem with the drivers, or anyway at the system level.

[fra81]

Hi,

the NoMachine player translates the Alt+Scroll combination into a horizontal scroll purposedly. This is probably what you are experiencing. I understand this might not be the expected behaviour, even though it could be handy in some cases, and we will evaluate to change it in the next NoMachine version.

[fra81]

Sorry, I made a mistake in my last post. To disable hardware decoding the key should be like this:

<option key=”Enable hardware accelerated decoding” value=”disabled” />

[fra81]

Thanks for the info. However, the reasons I mentioned above remain true. OBS is a different kind of application.

[fra81]

Hi,

for a start, let’s confirm the session closes due to a problem with the driver. To do that, please edit the $HOME/.nx/config/player.cfg and change the ‘Enable hardware accelerated decoding’ key to:

<option key=”Enable hardware accelerated decoding” value=”true” />

[fra81]

I checked the logs and they look clean. This is very strange. Is it possible that there is more than one X session running on that server machine? What is the output of the ‘ps -ef | grep X’ command run on the server? Do you have physical (local) access to that machine? Is everything normal if you use it locally?

[fra81]

Hi,

the current behaviour is intentional. It is assumed that, as long as the remote connection is active, the remote user is watching it. Also, a black screen in the remote desktop may lead the remote user to believe there is a problem with the connection. However, we understand that this may not be the expected behaviour for some users, so we are going to add an option to choose a different behaviour. Therefore I opened the following Feature Request:

https://knowledgebase.nomachine.com/FR02T04241

[fra81]

Hi,

would you take the session statistics from the menu panel (https://knowledgebase.nomachine.com/DT10R00167#9) and show us?

[Author]

Posts