-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mouse input is stuttering on Windows #37
Comments
Yes I've seen this. I haven't verified it, but I think its a problem in
pynput.
…On Oct 28, 2020 5:21 PM, "Stefan Pruneanu" ***@***.***> wrote:
The lib is working perfectly fine on Linux (to be exact, Pop!OS 20.10)
On Windows, the mouse stutters (like it doesn't have enough resolution).
You can see it jump from Point A to Point B when swiping fast.[
https://drive.google.com/file/d/1So6IppN1Z-IUg0NSiAKADrGFA0jkRHRZ/view?
usp=sharing](video here)
The smooth one is moving the mouse directly, the laggy one is using the
reMarkable.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#37>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABJT7YJDID5S2OXCBLNQRYDSNCKNHANCNFSM4TC6ABFA>
.
|
Is there anything I can try on my end? I've seen on other issues that you
don't have access to a Windows machine.
On Thu, Oct 29, 2020, 2:29 AM Evan Widloski <notifications@github.com>
wrote:
… Yes I've seen this. I haven't verified it, but I think its a problem in
pynput.
On Oct 28, 2020 5:21 PM, "Stefan Pruneanu" ***@***.***>
wrote:
> The lib is working perfectly fine on Linux (to be exact, Pop!OS 20.10)
> On Windows, the mouse stutters (like it doesn't have enough resolution).
> You can see it jump from Point A to Point B when swiping fast.[
> https://drive.google.com/file/d/1So6IppN1Z-IUg0NSiAKADrGFA0jkRHRZ/view?
> usp=sharing](video here)
>
> The smooth one is moving the mouse directly, the laggy one is using the
> reMarkable.
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <#37>, or unsubscribe
> <
https://github.com/notifications/unsubscribe-auth/ABJT7YJDID5S2OXCBLNQRYDSNCKNHANCNFSM4TC6ABFA
>
> .
>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#37 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AD2DRLQ2PE7TAAXW3J24N4DSNCZO5ANCNFSM4TC6ABFA>
.
|
You could try this snippet and see how it performs. This will move your mouse around in a circle. import math
from pynput.mouse import Controller
import time
start = time.time()
mouse = Controller()
mouse.move(100, 100)
N = 100
for n in range(2 * N):
rad = 2 * math.pi * n / N
mouse.position = (
200 * math.cos(rad) + 500,
200 * math.sin(rad) + 500
)
time.sleep(.01)
print('total:', time.time() - start) |
It works smoothly. video here |
I'm using remarkable_mouse on Windows 10. The cursor seems to move OK but when I try to write or draw something (in Windows Journal or Paint 3D) nothing appears on screen until I lift the pen from the ReMarkable, whereupon a straight line appears on my screen joining the starting point and the finishing point. |
Here is a stripped down version of the code which should help figure out what's causing the latency. |
I've just tested it and I still get the same weird latency. |
Right, the purpose of that code is just to make it easier for others to poke around and figure out the cause. |
I've narrowed the problem down a bit on Windows: paramiko/paramiko#1801 |
@petergroves81, I had the same issue on Paint3D but it works fine on Gimp. (I used the rm2 branch with a Remarkable2). |
I no longer use a reMarkable tablet. Issue is stale. |
The lib is working perfectly fine on Linux (to be exact, Pop!OS 20.10)
On Windows, the mouse stutters (like it doesn't have enough resolution). You can see it jump from Point A to Point B when swiping fast. video here
The smooth one is moving the mouse directly, the laggy one is using the reMarkable.
The text was updated successfully, but these errors were encountered: