fra81

[fra81]

Hi,

sorry for the delay. Logs don’t point to any specific issue. To rule out any driver issue, please try and 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 Michael,

just a guess: did you try to check the ‘Disable frame buffering on decoding’ option in the session menu panel, Display settings (on the Mac)? By default, when there is no local input, NoMachine assumes that there is no user interaction with the desktop and starts buffering few frames on playback.

[fra81]

Unfortunately we still can’t reproduce it in our labs the way you describe and with OBS. Is there any other detail that can be useful for us to reproduce? Any specific action that triggers the issue? For example, do you connect to the MacBook when the lid is closed?

[fra81]

Adding ProxyExtraOptions “pack=16m-png”

This option is only effective in virtual desktop sessions, when the ‘X11 vector graphics mode’ is enabled. Virtual desktops are only available for products in the Terminal Server family (e.g. NoMachine Workstation), of which you can download an evaluation version.

Because base on my understanding, the above option turned off sub-pixel sampling

To be precise, it would turn off the chroma subsampling that is introduced by the colorspace conversion from the YUV to the RGB format, as part of the encoding process. It doesn’t change the aliasing setting used by remote applications when rendering fonts.

[fra81]

Hi,

we would need also server side logs from the .nx directory in the user’s home. You can collect them by either the automatic or the manual procedure.

[fra81]

I have to turn off hardware acceleration

Do you mean the ‘Disable client side hardware decoding’ checkbox in the session menu panel?

Can you turn it on again and collect logs as explained in https://knowledgebase.nomachine.com/DT11R00181#2? You can send them to forum[at]nomachine[dot]com.

[fra81]

Hi,

colors generally need to be sub-sampled before they are fed to video encoders (typically from RGB to YUV format). This is particularly visible with bright colors (especially red) on dark backgrounds. For this reason, NoMachine performs an additional encoding pass to “fix” the colors. This is done progressively to not saturate the available bandwidth.

To alleviate this effect you can set the Display quality to the maximum level in the session menu panel, so that color refinement will happen faster. To make it even faster, you can check the ‘Disable multi-pass display encoding’ option in the advanced display options.

[fra81]

The screen blanking implementation is indeed about gamma settings. NoMachine encodes a copy of the framebuffer, so changing the framebuffer pixels would also affect what you see remotely.

As a possible alternative, you could turn the physical display off when you want to connect remotely, as explained at point 3 of this article: https://knowledgebase.nomachine.com/AR03P00973. At that point NoMachine will create a virtual (off-screen) framebuffer.

[fra81]

Please send the logs as explained above. Can you show us the ffmpeg command that you used for encoding?

[fra81]

Please check this article. If it doesn’t help, please gather server side logs as explained here. You can send them to forum[at]nomachine[dot]com.

[fra81]

Hi,

does this issue occur only when using fullscreen mode? And does it occur only when the remote screen is scaled (i.e. does it occur also in ‘viewport’ mode)?

Then please try to add the following key in the /Applications/NoMachine.app/Contents/Frameworks/etc/node.cfg file on the server machine:

DisplayServerExtraOptions "-oldeventapi 1"

Restart NoMachine and see if anything changes.

[fra81]

Hi Nyquist,

we can’t reproduce this issue in our labs and we didn’t receive similar reports. Should it happen again, please let us know, possibly with the steps to reproduce.

[fra81]

Hi,

sorry for the delay! We verified that indeed it doesn’t work and this issue is the reason:

https://github.com/raspberrypi/firmware/issues/1274

[fra81]

Hi,

so this seems to be a problem with the specific combination of graphics card and drivers. Even if sending data to the GPU for rendering can be fast, in some exceptional cases pulling data back from the GPU for screen capture can be much slower. When you stop lightdm, NoMachine creates a virtual framebuffer which is independent from the actual graphics card and drivers. Unfortunately that issue can’t be solved in NoMachine, but you may check for a different version of video drivers. For example, you may try to install proprietary Nvidia drivers or, in case you did already, install the open source ones.

[fra81]

Hi mrl,

is the server a headless machine (no monitor attached to it)? In that case, you can try one of the suggestions here: https://knowledgebase.nomachine.com/AR03P00973.

[Author]

Posts