Re: [DIGImend-users] Experiencing lag (with Huion 1060)

[Sarah O. <owe...@gm...>]

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


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.

Thanks,
Sarah

On Sun, Mar 1, 2015 at 11:00 AM, Nikolai Kondrashov <sp...@gm...>
wrote:

> Hi Sarah,
>
>
> On 03/01/2015 12:56 AM, Sarah Owens wrote:
>
>> I am trying to set up my Huion 1060pro
>> (http://huion-tablet.com/product/product.php?sku=1020), in Ubuntu
>> 14.04.  I
>> installed the DIGImend drivers by following the instructions on github,
>> and
>> I'm having a few problems.
>>
>> When drawing on Krita or the Gimp, my brush-stroke lags seconds behind
>> where
>> my pen is.  The stroke seems to buffer up, and will finish out the stroke,
>> but takes forever to do so.
>>
>> To solve this problem, I was thinking I might need an xorg.config to lower
>> sampling rate?  My computer has 8g of RAM (5 reported as "free").
>>
>> My other problem is none of the butttons work, except for left-click on
>> the
>> pen.  Does this device have a known status with the drivers?  (It looked
>> like it fell in the "other" category for supported Huion devices).
>>
>
> This is unlikely to be due to the tablet or driver behavior, but we can
> test
> that.
>
> Could you please send the output of this command:
>
>     sudo usbhid-dump -es -m 256c:006e
>
> while you scribble with the pen?
>
> This way we'll see the rate of incoming reports.
>
> Just in case this is caused by the driver, please also send the output of
> "evtest" for the pen interface, while doing the same. The pen interface
> will
> be the one which produces output while you move the pen.
>
> Thank you.
>
> Nick
>