Forum Replies Created
-
Posts
-
Hello,
for sure your hardware should be able to stream 60 fps without problems! What is your client side hardware and OS? And would you exclude bandwidth problems? For example, does it get any better if you lower the Display quality in the Display settings menu?
Additionally you could send us the logs, so we can search for any hints. For the server side: https://www.nomachine.com/AR10K00697. For client side: https://www.nomachine.com/DT10O00163#2. You can send them to forum[at]nomachine[dot]com.
Hi,
I see in the logs that the Wayland display manager is enabled on your system.
We are actively working on Wayland support. You can be notified when it will be released by applying in the relevant Feature Request:
https://www.nomachine.com/FR10N03221
In the same link, you can find a possible workaround.
Hi fred1,
we’ve never seen anything similar. Indeed log files look zeroed when the freeze occurs. Maybe you could run a sanity check on your hard disk, just to be sure.
Please provide the following information:
1. Gather content of “C:\Windows\Minidump” directory.
2. Export Event Viewer logs:
– Open Control Panel -> System and Security -> Administrative Tools -> Event Viewer
– To export events, select the type of logs you want to export, click on Action menu and pick Save All Events As.
We’re interested in ‘Windows Logs/System’, ‘Windows Logs/Application’ and ‘Application and Services Logs/Hardware Events’ logs.
There is something strange. I see two X server processes running, and one is in failsafe mode.
I would suggest you to reset everything:
systemctl stop lightdm
killall Xorg
killall -9 Xorg
systemctl start lightdm/usr/NX/bin/nxserver –restart
Or reboot the machine… 🙂
Hi!
You may try to disable mDNS broadcasting and discovery in NoMachine.
To disable broadcasting from servers, click on the NoMachine tray icon and unselect Show the service status -> Server preferences -> Services -> Advertise this computer on the network.
To disable discovery on clients, select Player preferences -> Privacy -> Don’t show other computers on the network.
You can change one of those two options at a time. The important thing is that you apply them an all machines of your network.
Hi Fred,
this issue is not known. Could you try to uncheck the ‘Use acceleration for display processing’ checkbox in Server preferences -> Performance tab? You can open Server preferences from the NoMachine tray icon by clicking on ‘Show the service status’, on your Windows 10 machine, before starting the connection.
Hi,
what does the ‘ps -ef | grep X’ command return on the server?
Is it maybe a headless server (no monitor attached)?
Hi Holger,
what NoMachine product are you using? Can I assume that you are running a Virtual Desktop session?
In that case, you may try to disable the ‘X11 vector graphics mode’ on the server, via the Performance tab in the ‘Server preferences’ UI or by changing the AgentX11VectorGraphics key in ‘/usr/NX/etc/node.cfg’. That mode is specifically optimized for multimedia content.
In any case, I would check if H.264 encoding is being used. You can check that in the session menu of your NoMachine Player, at the botton of ‘Display settings’ menu.
Hi Ve0,
did you try to verify the network bandwidth actually available, and latency as I suggested above?
I see that the editor modified also my marks, but I think you got the point 🙂
Alternatively, libraries can be copied to the proper folder by hand.
I’m going to answer in any case, as this might be useful for someone else.
$ ./configure –disable-cli –enable-shared –disable-avs –disable-swscale –disable-lavf –disable-ffms –disable-gpac –libdir=”C:\Program Files (x86)\NoMachine\bin”
I don’t know if you just copied and pasted here the actual command. In that case, the reason could be the use of quotation marks ”” instead of “”. Or you can try with apostrophes ‘ ‘.
So, if I understand, the non-working case is with NoMachine player running on the Windows 7 guest, connecting to NoMachine server running on the Windows Server 2016 (virtualized) host.
The fact NVENC encoder is available or not shouldn’t have any effect on the blank screen, but maybe there is some problem with the passed-through GPU. Please try to open the NoMachine Server preferences menu on the Windows Server host (server side of the connection), go to Performance tab, and uncheck ‘Use acceleration for display processing’.
In any case, you can send us the logs for further investigations as eplained in https://www.nomachine.com/DT07M00098. You can send to forum[at]nomachine[dot]com.
Hi,
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. In fact checking those boxes will limit the ability of congestion control algorythms to adapt to detected network conditions by adjusting image quality dinamically. Those settings won’t change the final quality, they only affect the progression and the speed how the target quality is reached.
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. Maybe it’s worth checking the network latency too (round trip time), if you didn’t do already (VPN could play a role here). You can do that also from NoMachine user interface (‘Take the statistics’), or with the ‘ping’ command.
A last note about Capture2.png: that blurriness around edges of coloured images is due to the chroma subsampling introduced by the encoder. NoMachine has algorithms to correct such color shift (https://www.nomachine.com/FR03M02907), but those are enabled only for quality level 5 or above (from the middle of the Quality slider to the right).
Well spotted!
The intention was to say:
Setting a higher value for the ‘latency’ option means that NoMachine will not attempt to reduce the throughput to minimize response time as long as the latter is below the indicated value.
I corrected the FR accordingly. Thanks for reporting!