Issues about dynamic network data send frequency

[owl sandy]

Hi, I am trying to use Input Director between two devices.

Both devices are WIndows 10 systems. The device used as Director is a high-performance Laptop and the other is Surface Go.

The default setting of the software is dynamic network data send frequency, but this caused some problems when my Surface Go was used as a Client. The mouse became extremely slow and difficult to control.

After testing, I found that the most straightforward solution is to set the Director's sending frequency to a fixed value.

But I was curious about the cause of this problem, so after testing, I found that on my Surface go, if I put the main window of Input Director on the front end, the mouse movement will be very smooth using dynamic network data send frequency.

But once I hide the main window, the mouse delay problem occurs.

Therefore, I guess that the mechanism of dynamic network data send frequency may be related to the CPU operation in some background processes.

In low-performance computers (Surface go), once the main window of the software is hidden, the system will strictly limit the number of wake-ups of the background process, which results in a huge delay in the Input director.

I don't quite know the program logic of Input Director, so I'm asking questions here and asking for developer help.

Of course I've solved this problem by changing the sending frequency, but I'm curious about the reason behind this and if it has any possibility of improvement.

[Shane]

Hi,

It used to be that any applications that subscribed to low level input would receive the complete stream of data. Microsoft has subsequently made a change so that only the foreground application receives all the mouse movement data and background applications receive a summary, which is why the cursor is no longer smooth as Input Director primarily runs in the background.

I’m exploring a couple of options to address this. One is to include an option for Input Director to become the foreground application whenever transitioning to a client. The second is to see if I can inject additional mouse movements into the data sent to the client to ‘unpack’ the summarised movements and have it feel smooth again.

Regs,

Shane. 

[Jolly]

Can you enable a higher fixed frequency rate?  (For use with 144hz monitors and 1000hz mice)

But in practice ever since I learned I can set up input director bidirectionally I use a hard percavium and switch my mouse over to the secondary in hardware if I'm using the secondary for an extended period of time.

--
You received this message because you are subscribed to the Google Groups "Input Director" group.
To unsubscribe from this group and stop receiving emails from it, send an email to input-directo...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/input-director/fb83da88-1b5b-4624-9db8-871f1306f879n%40googlegroups.com.