Forum Replies Created
-
Posts
-
Thank you for all the info!
Naturally file transfer bandwidth has to be limited in a way that it doesn’t slow down the streaming of the session, but definitely what you describe doesn’t look as the correct behaviour. We will test your setup deeply in our labs.
You’re welcome!
Maybe NoMachine could display the frames information in the stream window, in one of the corners, as an option (printing it in real time).
That’s a great idea and it is present in the Feature Request we opened:
https://www.nomachine.com/FR09P03680
The file transfers between these computers reached 100mb/s through Windows, but when using NoMachine, the file transfer ranged from 300kb/s to 3mb/s
Do you confirm that you are referring to NoMachine’s file transfer service (that wouldn’t use all the available bandwidth)? Or you mean instead the streaming of the NoMachine session?
So, it could be a client-side option between showing “black margins” (simulating the 4:3 resolution on the server-side) or leaving the image stretched.
1:1 mode should be the default! Please check in the Display panel in the session menu that ‘Fit to window’ is not selected. You can also use the quick icons at the bottom of the menu to switch between display modes.
Hi Belez,
printing in the logs what is the programmatic framerate selected by the server, according to network conditions and such, seems to be something definitely missing. We’ll add it to the logs of the client, as well as when, for any reason, the programmatic framerate changes during the session. The achieved framerate, then, can be different. We’ll add it as well, but the best way to measure it is certainly by an external tool, like Fraps. As I stated, we ignore why Fraps fails to detect it. You should ask the Fraps developers. Anyway having the framerate measured by the client will be a good starting point.
I mean, i can use fraps and similar software on Steam and Splashtop streams to measure client-side FPS (and it is different from server-side), but i can’t do the same with NoMachine client-side.
Well, it’s difficult to say because we should know the exact way Fraps “gets” that a new frame is output… You should try to contact the Fraps developer and try to shed some light. Of course there may be some optimizations we have worked on that Fraps doesn’t expect… We may also explain in detailed way all those optimizations, but you will agree that it’s in our interest to keep some spice secret. 😉
Dear dd0044, this specific game seems to have a problem causing this specific issue.
It can still be a problem with NoMachine, of course, but it is absolutely advisable to first try the patch and then verify if it’s actually so.
We strongly invite you to do your best to install the game’s patch, possibly with the help of the game’s publisher, otherwise it will be difficult for us to investigate the problem without a well-specific starting point.
It’s a bug. There is a specific executable, nxdock, that is not signed. We investigated this and it seems that the bug was introduced in version 6.0.62, when we lastly upgraded the Mac build environment. We’ll fix it in the next release. Just to make things clear, the Mac and Windows packages are fully signed, as signed are all the libraries and all the executables (except those that, by mistake, got out of the procedure). We’ll fix this shortly and update the post-production unit tests.
Hi Bruce,
we’re not able to reproduce this behaviour in our labs at the moment. We are preparing a debug package to investigate on what’s going on on your Mac, if you’re willing to test it.
Unfortunately NoMachine insists on using QuickSync rather than VAAPI and the former is notoriously difficult to get working without applying a lot of hacks whereas the latter covers multiple GPU types and should “just work”.
Just to say that we started this in 2014. At that time VAAPI was not as mature and it didn’t even support the encoding side.
But now, finally, VAAPI starts to yield some results, and it is widely supported. Also considering the huge mess distributions make with Intel drivers, Intel Media SDK and the tweaking necessary to make QuickSync work, we are finally readying the VAAPI implementation.
Hi Bruce,
we will check deeply in our labs with the last macOS version. In the meanwhile, are you able to say maybe if this issue was introduced by the latest macOS update?
That FR only refers to H.264 hardware encoding on server side not yet available when using the X11 vector graphics mode. H.264 software encoding is always included in all licensed products (Workstation included), without any need for a specific license. As for the decoding side, software encoding is available in all licensed products and wherever hardware decoding is supported (that practically includes all Windows and Mac clients). If you are connecting from Windows, H.264 should be available.
At this point, I would try to disable hardware decoding on the affected client (https://www.nomachine.com/DT10O00157#5.7.).
Hi,
can you confirm you’re really using VP8 and not H.264? Please note that H.264 would be used by default where available. You can find this information in the Display settings panel in the session menu. I suspect you might be using a hardware encoder and there is some problem with video drivers.
Session logs could be useful to sort this out. See https://www.nomachine.com/AR10K00697 and https://www.nomachine.com/DT10O00163#2 for server and client side logs, respectively.
Hi,
you can connect to the server, right click on the existing session and select ‘Terminate session’ from the context menu. Alternatively, you can use the nxserver command line interface (sudo /usr/NX/bin/nxserver –terminate [<sessionid> | <display> | <username>]).
However such behaviour is certainly unexpected and, if possible, we would like to see the logs for further investigation. You can find info on how to gather logs here: https://www.nomachine.com/AR10K00697. You can attach them here or send to forum[at]nomachine[dot]com.
Hi Shu,
at the moment you have to look for this info in the logs. Session logs are located (by default) inside directories starting with the ‘C-‘ prefix in the ‘/usr/NX/var/log/node’ location. More info on how to retrieve the logs in https://www.nomachine.com/AR10K00697. If GPU is used for encoding, you will see in the ‘session’ file something like:
Info: Using H.264 hardware encoder.
Note that in future versions of NoMachine this info will also be available in the client GUI.
Hi,
I would start with checking logs. Please gather server side logs as described in https://www.nomachine.com/AR10K00697 and client side logs as decribed in https://www.nomachine.com/DT10O00163#2. You can attach them here or send to forum[at]nomachine[dot]com. Please also check CPU usage on client and server.
Hi David,
that is really strange indeed. I would start with trying to disable hardware decoding (check “Disable client side hardware decoding” in Display settings in the session menu). It would be great if you could gather server side logs as described in https://www.nomachine.com/AR10K00697 and client side logs as decribed in https://www.nomachine.com/DT10O00163#2. You can attach them here or send to forum[at]nomachine[dot]com.