Re: [DIGImend-users] Experiencing lag (with Huion 1060)
Brought to you by:
spb_nick
Menu
▾
▴
Re: [DIGImend-users] Experiencing lag (with Huion 1060)
|
From: Nikolai K. <sp...@gm...> - 2015-03-02 10:33:41
|
On 03/02/2015 02:04 AM, Sarah Owens wrote: > Sure, here are some lines from usbhid-dump: > > 002:011:000:STREAM 1425254057.106243 > 07 81 BC 46 1B 2A FF 07 > > 002:011:000:STREAM 1425254057.136175 > 07 81 BC 46 1D 2A FF 07 > > 002:011:000:STREAM 1425254057.140231 > 07 81 BC 46 1F 2A FF 07 > > 002:011:000:STREAM 1425254057.144242 > 07 81 BC 46 21 2A FF 07 > > 002:011:000:STREAM 1425254057.148184 > 07 81 BC 46 23 2A FF 07 > > 002:011:000:STREAM 1425254057.152161 > 07 81 BA 46 28 2A FF 07 > > > And here are some lines from evtest: > > Event: time 1425254448.564150, -------------- SYN_REPORT ------------ > Event: time 1425254448.568167, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0042 > Event: time 1425254448.568167, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1 > Event: time 1425254448.568167, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0043 > Event: time 1425254448.568167, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0 > Event: time 1425254448.568167, type 3 (EV_ABS), code 0 (ABS_X), value 13767 > Event: time 1425254448.568167, type 3 (EV_ABS), code 24 (ABS_PRESSURE), value 1730 > Event: time 1425254448.568167, -------------- SYN_REPORT ------------ > Event: time 1425254448.572168, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0042 > Event: time 1425254448.572168, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1 > Event: time 1425254448.572168, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0043 > Event: time 1425254448.572168, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0 > Event: time 1425254448.572168, type 3 (EV_ABS), code 1 (ABS_Y), value 17067 > Event: time 1425254448.572168, type 3 (EV_ABS), code 24 (ABS_PRESSURE), value 2047 > Event: time 1425254448.572168, -------------- SYN_REPORT ------------ > Event: time 1425254448.576169, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0042 > Event: time 1425254448.576169, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1 > Event: time 1425254448.576169, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0043 > Event: time 1425254448.576169, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0 > Event: time 1425254448.576169, type 3 (EV_ABS), code 0 (ABS_X), value 13770 > Event: time 1425254448.576169, -------------- SYN_REPORT ------------ > Event: time 1425254448.580162, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0042 > Event: time 1425254448.580162, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1 > Event: time 1425254448.580162, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0043 > Event: time 1425254448.580162, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0 > Event: time 1425254448.580162, type 3 (EV_ABS), code 0 (ABS_X), value 13773 > Event: time 1425254448.580162, type 3 (EV_ABS), code 1 (ABS_Y), value 17065 Thanks, Sarah! However, I'll need to have more output to calculate and compare the report rate. A thousand events, at least. You can just do a few scribbles and send gzipped output. Or, you can calculate the report rate yourself. You have the timestamps both in usbhid-dump and evtest output. In usbhid-dump you need to sample every report, and in evtest only the SYN_REPORT lines. > The evtest looked like events were registering immediately--when I clicked > with the pen, it would immediately register an ABS_PRESSURE, and when I took > the pen away from the tablet, all events would immediately stop. Yes, I would expect that. I was suspecting simply too many reports, but now when I look at your evtest samples I see that BTN_TOUCH is toggled on and off in every report, which might be the reason for the slowdown. I'll check the code and will try it with my H610. Meanwhile can you check that you get BTN_TOUCH toggled in every evtest report? Or perhaps just send me both full usbhid-dump and full evtest outputs. BTW, which version of the driver are you using? Nick |
