Forum / NoMachine for Windows / One key press causes multiple keys on the Server
- This topic has 3 replies, 2 voices, and was last updated 9 years, 7 months ago by titan.
October 22, 2013 at 16:37 #186sthonesParticipant
I’m using NoMachine 4.0.360 on a Windows Client and a Linux Server.
I experience a lot of situations when I’m normally typing on the Client and on the Server a key press is arriving multiple times, causing texts like “heeeeellooooo”.
The issue reduced a little after selecting the “Grab the keyboard input” setting on the Input pane, but it still remains in some cases, especially for the cursor keys – so it’s very hard to navigate the cursor without using the mouse.
any ideas what’s causing this?
October 22, 2013 at 20:22 #201titanParticipant
- This topic was modified 9 years, 7 months ago by John Watts.
How long it takes between the first letter (the legitimate one) and the first spurious character? Is it compatible with the autorepeat time set on the Linux server (say 1/10th of a second), or it is much shorter (almost immediate)? Can you please try to increase the autorepeat time on the server desktop and see if it makes any difference?October 24, 2013 at 19:44 #239sthonesParticipant
The repeat is nearly immediate – so way faster than the autorepeat. but it’s not instant, so it doesn’t happen on every keypress.
An additional note, this mainly (only?) happens when I access the server via a VPN connection into the company – when I access the server inside the company’s LAN, it doesn’t happen. but parallel ssh connections through the VPN, or Lync voice calls, etc, don’t show any anomalies in regards to connectivity.
sthonesOctober 25, 2013 at 09:17 #257titanParticipant
The repeat is nearly immediate – so way faster than the autorepeat. but it’s not instant
The autorepeat we are interested in is the autorepeat timeout causing the first repetition. The further repetitions of the same key continue because the “key release” event is not received by the remote, presumably because of a network problem. So what really counts is that the round-trip time is less than the (first) autorepeat timeout.
This problem can be caused by a particular delay between packets being introduced by the network. A SSH terminal is not affected by this, since the characters sent by the terminal application are produced on the client side and only echoed by the server. Same for a voice or a video call, where the buffer underflows or the network jitter can be easily compensated. For voice and video 1 second delay (caused by buffering) is the norm. You just don’t notice that because audio and video are synchronized. When you are talking with somebody there are not many “round-trips”, but YouTube is full of videos showing the funny effect when people try to “synchronize”. Unfortunately in a system like NoMachine you can’t produce characters on the client, since how each key press is translated depends on whatever keymap or program is running on the server. NoMachine has some tricky algorithms to “compensate” the key presses, but evidently they don’t work in your case. Probably this depends on big spikes in latency, happening from time to time.
If you want, we can provide a test version with some logs enabled. This should shed more light on the issue and surely help to improve the code.
No further information provided by the user for more than 10 days. This topic was marked as closed, you can't post.