Forum Replies Created
April 11, 2019 at 11:07 in reply to: Much faster screen updates in latest version #22010
Well, we make H.264 the new default, by including the (MPEGLA patented) code from FFMPEG even in the free-of-charge version (paying the MPEGLA fee for each copy). Previously in the free version we used VP8, if the H.264 HW encoding was not available or the user had not purchased the H.264 code included in the AVC Pack. VP8 is definitely a good encoder and we have worked a lot to optimize its usage, but x264… Well… is better.January 22, 2018 at 15:02 in reply to: NoMachine caused intermittent network issue? #17257
@Fra81, just for the record, it sounds a bit unlikely that a small amount of multicast UDP packets can cause such an issue, although I agree that it’s best to test. Anyway (again for the record), did we have any report of other issues, directly or indirectly related to mDNS?September 13, 2016 at 08:17 in reply to: NoMachine Network (Anywhere) Status #12341
We’re almost there! Smoothing out the rough edges in the architecture and graphic interface. And testing, testing, testing. But rest assured, it’s not far off.April 16, 2014 at 20:11 in reply to: Performance tuning when published via Citrix XenApp? #3157
I published the NX enterprise client via Citrix XenApp and connected to my test machine (again, h.264) and it’s very laggy.
If I understand correctly, the NoMachine client is running on the server and its output is encoded by Citrix XenApp and forwarded to the XenApp client at the remote location (through the NetScaler VPN). So (again if I understand correctly) NoMachine encoding is taking place between the XenApp server (where the NoMachine client is running) and the NoMachine Enterprise Desktop, with the NoMachine client displaying its output as if the XenApp backend was the real display. If this is the case, I’m afraid this looks more a Citrix performance problem than a NoMachine performance problem.
I read that this is not possible in your case, due to other constraints, but can you compare the performance connecting directly from the client side to the NoMachine Enterprise Desktop machine using the NoMachine client and the same NetScaler VPN link? This could be a good starting point.April 9, 2014 at 17:39 in reply to: Error 60: Operation timed out #3051
Please be sure that all of you update to the latest version. This should be always a requirement before starting any investigation.
There have been months of work and plenty of bug fixes since the 4.0.370. I wouldn’t be surprised if the problem you are experiencing was already solved.April 9, 2014 at 17:25 in reply to: Windows 8 RT #3049
<rant> NoMachine is built on top of a foundation library which implements the POSIX interface on top of Win32. Building a native player for Windows RT requires rewriting this code to ditch almost completely the Win32 API, including socket communication, thread programming and low-level networking. This is a huge endorsement. Android and iOS allow C/C++ applications using the POSIX API to work almost unmodified, compared to the same application working on a desktop computer, with modifications mostly limited to the input and the GUI. This is a small percentage of the total amount of code that a developer has normally to port from a platform to the other. </rant>
Well, sorry for the rant, but this just to say that it’s not surprising that very few of the biggest and more complex applications, made like NoMachine of many C/C++ libraries tied together, are available on Windows RT :-).
Fortunately it seems that Microsoft is changing its course. There is hope that the Win32 API (and thus some sort of POSIX compatibility) can make a return in the near future:
This doesn’t mean that you won’t see a NoMachine player running on Windows RT soon, even if not as a “native” application. The hardware is generally pretty good and NoMachine can already run as a HTML application on practically every browser. Now that the software is starting to mature on the “native” platforms, we are going to give to our Web player a big boost. Making a mixed native/HTML version optimized for Windows RT should not be very difficult, albeit such work has not started yet.April 8, 2014 at 17:56 in reply to: General usability comments #2998
Hi, thanks for your feedback, it’s much appreciated.
– make minimize default when clicking in corner (like in NX 3): Once setup I rarely need to reach the NX menu but often need to switch back to the host
There is a “Show extended icons in the page peel” (you set it via the Menu -> Input -> Use action icons in the page-peel) . This gives access to the screen manipulation icons without having to open the full menu. Or open the full menu and click on the minimize icon on the bottom. We can’t just make “click in the corner” the action to minimize. If we do that we have the big problem of finding a replacement for opening the menu. Such a replacement must be easily accessible on all platforms, intuitive and not overlapping with any common action that the user is normally performing on the system. It is not by casuality that both the latest Windows and the latest OS X are recurring to “click the edge of the screen to…” actions. It was one of the few actions remained not taken by something else.
– add an exit button to the NX menu: only way to exit on Windows is to use ALT-F4 or switch to task manager and kill-it.
Open the menu, click on the “Disconnect” icon you find on the extreme right, just below the “Done” button. I assume you are talking about a NX window displaying full screen. If the session runs in a overlapped window you just close the window.
– add a Restart service button to NX Service: when changing some settings it says to restart the service – but I don’t know how.
Good point. We’ll made the “restart the service” notice a link. Clicking on the link will restart the server (after the confirmation).
– why is the menu full screen/over other windows and not a regular window?
Are you asking why is the menu an overlay and not a window that you can move inside the remote desktop? Because it is not part of the remote desktop, but part of the viewer. We need to create a clear separation between what is happening locally and what is happening remotely. Most users would be confused by a “Stop” button appearing inside the scene of the movie they are watching. 😉February 19, 2014 at 15:25 in reply to: Blurry image when resolution doesn’t match #2437
By the way, these are three screenshots taken with the three software, so you can judge for yourself.
Attachments:February 19, 2014 at 14:59 in reply to: Blurry image when resolution doesn’t match #2427
We did our homework. This was also a good chance to compare NoMachine with the competition (something we regularly do, as everybody should be doing in any business). Well, let me say… WOW. I mean, both software you mentioned are definitely fast by any measure, but… Well, you understand what I mean. I don’t know what the people here put in the software but let me say: good job ;-).
But let’s back at our scaling problem. Yes, I confirm that is a scaling issue. Both UltraVNC and TeamViewer make a better job at scaling. The reason is that at the present moment we use an implementation that is optimized for speed, rather than quality. This implementation was originally intended to be a fallback for when HW accelerated scaling is not available, but since HW accelerated scaling is proceeding more slowly than expected (people have been busy with other tasks) it’s basically the only scaling available at the moment. We can improve the quality of this SW scaling, of course. The problem is how to do that in real-time without impacting the rest. There are some ideas on the table. I promise you will see consistent improvements in the next releases.February 19, 2014 at 10:38 in reply to: Client Zoom Level? #2423
Note taken. If I understand your idea, this would apply to both the 1:1 view (what we call viewport mode, with or without scrollbars) and “Fit to window”, so that the remote screen is always displayed at 80%, right?February 19, 2014 at 10:16 in reply to: Ctrl+Alt+Del for Windows to Windows #2421
This is an idea: we know when Windows enters the login screen so we can insert a hint panel similar to the welcome panels we display at startup. Would this be sufficient to save your head?February 19, 2014 at 10:01 in reply to: Ctrl+Alt+Del for Windows to Windows #2417
I have been trying for a few hours now banging my head against the wall trying to figure out why I cannot send Ctrl+Alt+Del sequence to a Windows
Next time, instead of screaming or banging your head against the wall, spend 5 minutes at searching the Internet or the NoMachine Knowledge Base. Windows doesn’t allow intercepting the Ctrl+Alt+Del for security reasons, so doing this from the keyboard is impossible by design.
Feel free to suggest how we can improve the user experience. We would love to make a search unneeded but so far nobody here came with a good idea on how to do it.February 18, 2014 at 11:34 in reply to: Lagging and weird keyboard strokes #2389
I think I am the minority (though I am surprised that majority needs to remote back to watch netflix and play video games).
There is a minority of the total computing population that needs or likes remote desktops. In that minority there is a majority that would like to do with a remote desktop the same things it does with a real computer. So, no pun intended, we can say that you are in the minority of the minority.
The success of AirPlay or the buzz created by OnLive or Sony Remote Play demonstrate that there is a significant interest in a big part of the computing population for “remoting” things. Speaking for myself, I already narrated in another post that I have a couple of iMacs I use as TV sets. I find it very handy to be able to watch the MotoGP on the laptop when I’m dining, since in the dining room there is no iMac. For me the ability to use NoMachine this way is a killer feature. I use the same iMacs with various virtual machines for development. All my development activity takes place from remote, on the command line, where a terminal and ssh serve me well. If the purpose of remoting was to help this my development activity, I would not need NoMachine or a remote desktop and even less I would be willing to pay for it.February 17, 2014 at 15:45 in reply to: Firewall settings that worked for me on Fedora 20 #2365
Technically, you just need port 4000 TCP (or the port you decided to use for the NX service).
I presume the additional port 24004 is what the client or server selected at random for UDP. You can change it or disable UDP altogether in Edit connection, Advanced.
Both the client and the server try to use UDP, if they can. First the server will try to use the UDP port opened by the client, then the client will try to establish the communication on the UDP port opened by the server. If both attempts fail, the communication will continue using only the TCP port.
At the time I’m writing, the ports are added automatically to the firewall configuration on Windows. Not so on Mac and Linux. This is going to change in the future.February 17, 2014 at 14:40 in reply to: Connecting to 4.1 physical desktop resets display frequency #2363
and no more sound forwarding message each time I log
Wait! We didn’t remove that dialog :-). That dialog is absolutely essential, since if you are connecting to someone else’s machine, that someone else won’t probably want you to steal his/her audio!
Can it be that you clicked “Don’t show this message again”?
TO ALL PEOPLE WILLING TO “CONNECT WITH ONE CLICK”:
Just be sure you click on the “Don’t show this message again” check boxes you find along the way! 😉