digimend-devel Mailing List for DIGImend
Brought to you by:
spb_nick
Menu
▾
▴
digimend-devel — Development matters
You can subscribe to this list here.
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(8) |
Jun
(27) |
Jul
(54) |
Aug
(54) |
Sep
(13) |
Oct
(20) |
Nov
(7) |
Dec
(4) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2013 |
Jan
(3) |
Feb
(3) |
Mar
(6) |
Apr
(1) |
May
(8) |
Jun
(5) |
Jul
(4) |
Aug
(10) |
Sep
(44) |
Oct
(12) |
Nov
(5) |
Dec
(14) |
| 2014 |
Jan
(16) |
Feb
(3) |
Mar
(3) |
Apr
(5) |
May
(2) |
Jun
(14) |
Jul
(38) |
Aug
(15) |
Sep
(15) |
Oct
(12) |
Nov
(38) |
Dec
(31) |
| 2015 |
Jan
(73) |
Feb
(71) |
Mar
(57) |
Apr
(36) |
May
(33) |
Jun
(20) |
Jul
(4) |
Aug
(5) |
Sep
(1) |
Oct
(11) |
Nov
(2) |
Dec
(6) |
| 2016 |
Jan
(7) |
Feb
(3) |
Mar
(6) |
Apr
(2) |
May
(7) |
Jun
(5) |
Jul
(3) |
Aug
(5) |
Sep
(5) |
Oct
(8) |
Nov
(13) |
Dec
|
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
|
1
|
2
|
3
|
4
|
5
|
6
|
7
|
|
8
(1) |
9
(3) |
10
(1) |
11
|
12
|
13
|
14
|
|
15
|
16
(1) |
17
|
18
|
19
(1) |
20
|
21
|
|
22
|
23
|
24
|
25
|
26
|
27
|
28
|
|
29
|
30
|
31
|
|
|
|
|
|
From: Nikolai Kondrashov <sp...@gm...> - 2016-05-16 13:12:03
|
Hi YAFU, On 05/16/2016 04:01 PM, YAFU wrote: > Hello, thanks for taking a look at this. > I had shared your answer with Blender developers and Bastien has made a new reply to the bug report. > https://developer.blender.org/T48204 I see. This is more specific now. You can try to reach Peter Hutterer <peter...@wh...> (the xf86-input-evdev author) regarding this bug, after verifying that your tablet is actually using his driver. Otherwise, please report an issue at https://github.com/DIGImend/digimend-kernel-drivers/issues/new so I don't forget to check it out when I have time. Nick On 05/16/2016 04:01 PM, YAFU wrote: > Hello, thanks for taking a look at this. > I had shared your answer with Blender developers and Bastien has made a new reply to the bug report. > https://developer.blender.org/T48204 > Thank you. > > 2016-05-10 18:01 GMT-03:00 Nikolai Kondrashov <sp...@gm... <mailto:sp...@gm...>>: > > On 05/09/2016 09:48 PM, YAFU wrote: > > It seems that I get something with "xinput --test-xi2" in Blender. Just in > case I also attach the file with the output drawing on Pinta app. Pinta does > not support pressure sensitivity, but I guess that information is present in > the xinput/evtest output anyway. > > > Thank you for the detailed diagnostics. So far from what I can see, Blender > gets seriously confused when at least lower-numbered evaluators are missing in > xinput reports. If you compare evtest, xinput and Blender output, you can see > that. > > Apparently Blender prints screen coordinates it receives, which are scaled as > compared to xinput and evdev output, but pressure values stay the same - you > can use them as the key for comparison. You can see basically one-to-one > correspondence between evdev report pieces between SYN_REPORT's and the xinput > RawMotion events. If you look up the same reports from Blender, you see that > when when lower-numbered valuators are missing (e.g. X), Blender reads pressure > as zero. > > Here's an example. You can forward this message to Blender developers. > > Blender output: > > handling tablet event: 0: 891; 1: 617; 2: 543; > Resulting tablet data: 0: 891; 1: 617; 2: 0.530792; 3: 0.000000; 4: 0.000000 > > handling tablet event: 1: 618; 2: 0; > Resulting tablet data: 0: 891; 1: 618; 2: 0.000000; 3: 0.000000; 4: 0.000000 > > handling tablet event: 1: 619; 2: 0; > Resulting tablet data: 0: 891; 1: 619; 2: 0.000000; 3: 0.000000; 4: 0.000000 > > handling tablet event: 1: 619; > Resulting tablet data: 0: 891; 1: 619; 2: 0.000000; 3: 0.000000; 4: 0.000000 > > handling tablet event: 1: 620; 2: 0; > Resulting tablet data: 0: 891; 1: 620; 2: 0.000000; 3: 0.000000; 4: 0.000000 > > handling tablet event: 0: 891; 1: 620; > Resulting tablet data: 0: 891; 1: 620; 2: 0.000000; 3: 0.000000; 4: 0.000000 > > handling tablet event: 1: 621; > Resulting tablet data: 0: 891; 1: 621; 2: 0.000000; 3: 0.000000; 4: 0.000000 > > handling tablet event: 1: 621; 2: 0; > Resulting tablet data: 0: 891; 1: 621; 2: 0.000000; 3: 0.000000; 4: 0.000000 > > handling tablet event: 1: 622; > Resulting tablet data: 0: 891; 1: 622; 2: 0.000000; 3: 0.000000; 4: 0.000000 > > handling tablet event: 0: 891; 1: 622; 2: 549; > Resulting tablet data: 0: 891; 1: 622; 2: 0.536657; 3: 0.000000; 4: 0.000000 > > Xinput output: > > EVENT type 17 (RawMotion) > device: 8 (8) > detail: 0 > valuators: > flags: > 0: 15219.00 (15219.00) > 1: 18769.00 (18769.00) > 2: 543.00 (543.00) > > EVENT type 17 (RawMotion) > device: 8 (8) > detail: 0 > valuators: > flags: > 1: 18790.00 (18790.00) > 2: 544.00 (544.00) > > EVENT type 17 (RawMotion) > device: 8 (8) > detail: 0 > valuators: > flags: > 1: 18810.00 (18810.00) > 2: 545.00 (545.00) > > EVENT type 17 (RawMotion) > device: 8 (8) > detail: 0 > valuators: > flags: > 1: 18827.00 (18827.00) > > EVENT type 17 (RawMotion) > device: 8 (8) > detail: 0 > valuators: > flags: > 1: 18839.00 (18839.00) > 2: 546.00 (546.00) > > EVENT type 17 (RawMotion) > device: 8 (8) > detail: 0 > valuators: > flags: > 0: 15222.00 (15222.00) > 1: 18847.00 (18847.00) > > EVENT type 17 (RawMotion) > device: 8 (8) > detail: 0 > valuators: > flags: > 1: 18864.00 (18864.00) > > EVENT type 17 (RawMotion) > device: 8 (8) > detail: 0 > valuators: > flags: > 1: 18876.00 (18876.00) > 2: 547.00 (547.00) > > EVENT type 17 (RawMotion) > device: 8 (8) > detail: 0 > valuators: > flags: > 1: 18892.00 (18892.00) > > EVENT type 17 (RawMotion) > device: 8 (8) > detail: 0 > valuators: > flags: > 0: 15219.00 (15219.00) > 1: 18909.00 (18909.00) > 2: 549.00 (549.00) > > Evtest output: > > Event: time 1462818916.523455, -------------- SYN_REPORT ------------ > Event: time 1462818916.531461, type 3 (EV_ABS), code 0 (ABS_X), value 15219 > Event: time 1462818916.531461, type 3 (EV_ABS), code 1 (ABS_Y), value 18769 > Event: time 1462818916.531461, type 3 (EV_ABS), code 24 (ABS_PRESSURE), value 543 > Event: time 1462818916.531461, -------------- SYN_REPORT ------------ > Event: time 1462818916.539463, type 3 (EV_ABS), code 1 (ABS_Y), value 18790 > Event: time 1462818916.539463, type 3 (EV_ABS), code 24 (ABS_PRESSURE), value 544 > Event: time 1462818916.539463, -------------- SYN_REPORT ------------ > Event: time 1462818916.547461, type 3 (EV_ABS), code 1 (ABS_Y), value 18810 > Event: time 1462818916.547461, type 3 (EV_ABS), code 24 (ABS_PRESSURE), value 545 > Event: time 1462818916.547461, -------------- SYN_REPORT ------------ > Event: time 1462818916.555483, type 3 (EV_ABS), code 1 (ABS_Y), value 18827 > Event: time 1462818916.555483, -------------- SYN_REPORT ------------ > Event: time 1462818916.563461, type 3 (EV_ABS), code 1 (ABS_Y), value 18839 > Event: time 1462818916.563461, type 3 (EV_ABS), code 24 (ABS_PRESSURE), value 546 > Event: time 1462818916.563461, -------------- SYN_REPORT ------------ > Event: time 1462818916.571485, type 3 (EV_ABS), code 0 (ABS_X), value 15222 > Event: time 1462818916.571485, type 3 (EV_ABS), code 1 (ABS_Y), value 18847 > Event: time 1462818916.571485, -------------- SYN_REPORT ------------ > Event: time 1462818916.579493, type 3 (EV_ABS), code 1 (ABS_Y), value 18864 > Event: time 1462818916.579493, -------------- SYN_REPORT ------------ > Event: time 1462818916.587484, type 3 (EV_ABS), code 1 (ABS_Y), value 18876 > Event: time 1462818916.587484, type 3 (EV_ABS), code 24 (ABS_PRESSURE), value 547 > Event: time 1462818916.587484, -------------- SYN_REPORT ------------ > Event: time 1462818916.595473, type 3 (EV_ABS), code 1 (ABS_Y), value 18892 > Event: time 1462818916.595473, -------------- SYN_REPORT ------------ > Event: time 1462818916.603483, type 3 (EV_ABS), code 0 (ABS_X), value 15219 > Event: time 1462818916.603483, type 3 (EV_ABS), code 1 (ABS_Y), value 18909 > Event: time 1462818916.603483, type 3 (EV_ABS), code 24 (ABS_PRESSURE), value 549 > Event: time 1462818916.603483, -------------- SYN_REPORT ------------ > > > Apparently the mailing list rejects messages with attached files, so I send > this mail to you. > > > Hmm, this is strange, I didn't get any administrator notifications about that. > > Nick > > On 05/09/2016 09:48 PM, YAFU wrote: > > It seems that I get something with "xinput --test-xi2" in Blender. Just in case I also attach the file with the output drawing on Pinta app. Pinta does not support pressure sensitivity, but I guess that information is present in the xinput/evtest output anyway. > > Apparently the mailing list rejects messages with attached files, so I send this mail to you. > Thank you. > > 2016-05-09 15:09 GMT-03:00 Nikolai Kondrashov <sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>>>: > > On 05/09/2016 08:58 PM, YAFU wrote: > > I'm having a weird behavior with xinput. I am using KDE (Kubuntu 14.04). I > can only get an output from "xinput -test 8" (8 is my pen id) when working > with the pen over GTK applications (Firefox for example). I do not get > outputs if I work with the pen over KDE/Qt applications or with Blender. How > could I get the output of "xinput -test" drawing on Blender, thus I could > send you the Blender, evtest and xinput output with the same draw/stroke > over Blender? > > > I suspect the pointer device is being taken over by Blender, but I'm not sure > how exactly that works. You might not be able to do it together with Blender. > > Try "xinput --test-xi2", perhaps that will work. > > Nick > > On 05/09/2016 08:58 PM, YAFU wrote: > > I'm having a weird behavior with xinput. I am using KDE (Kubuntu 14.04). I can only get an output from "xinput -test 8" (8 is my pen id) when working with the pen over GTK applications (Firefox for example). I do not get outputs if I work with the pen over KDE/Qt applications or with Blender. How could I get the output of "xinput -test" drawing on Blender, thus I could send you the Blender, evtest and xinput output with the same draw/stroke over Blender? > > 2016-05-09 13:42 GMT-03:00 Nikolai Kondrashov <sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>>>>: > > On 05/09/2016 03:51 PM, YAFU wrote: > > Now that I see, I assumed that "xinput test" was what I got from Blender. If > this is not so, how I can get "xinput test"? > > > I took a look and I don't see the issue in the "evtest" output. > I'd rather suspect Blender, but let's see "xinput test" output first. > > To get "xinput test" output you need the "xinput" tool (package should be > named the same). You'll need to run the "xinput list" command first to figure > out the ID of the device and then run "xinput test <ID>" with the found ID. > You might get several devices in "xinput list" output, the same as in "evtest" > output and you'll need to choose the one that reacts to the pen. > > Nick > > On 05/09/2016 03:51 PM, YAFU wrote: > > Now that I see, I assumed that "xinput test" was what I got from Blender. If this is not so, how I can get "xinput test"? > > 2016-05-09 9:00 GMT-03:00 Nikolai Kondrashov <sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>>>>>: > > Hi YAFU, > > On 05/08/2016 04:22 PM, YAFU wrote: > > I appreciate if you can take a look at this report and what developers discussed there: > https://developer.blender.org/T48204 > > > Thanks for the heads-up. The missing coordinate (X/Y) issues crop up in > userspace programs pretty often, get fixed, and then appear again. > > The missing coordinates are perfectly valid according to the xinput protocol, > although e.g. the xf86-input-wacom driver never does them, while > x86-input-evdev always does, and the latter is handling most of the non-Wacom > tablets. > > Now, I haven't seen the zero pressure issue before. The best course of action > would be to see if they appear in "evtest" output as compared to "xinput test" > output. If zero pressure appears in "xinput test" output, but not in "evtest" > output, then it's the xf86-input-evdev driver problem. > > If they appear in both, then the next step would be to look at the > /sys/kernel/debug/hid/*/events output. If they're not there, then it's the > kernel issue. Otherwise, it's likely a hardware issue. > > Nick > > > > > > > > |
|
From: Nikolai Kondrashov <sp...@gm...> - 2016-05-10 21:01:57
|
On 05/09/2016 09:48 PM, YAFU wrote: > It seems that I get something with "xinput --test-xi2" in Blender. Just in > case I also attach the file with the output drawing on Pinta app. Pinta does > not support pressure sensitivity, but I guess that information is present in > the xinput/evtest output anyway. Thank you for the detailed diagnostics. So far from what I can see, Blender gets seriously confused when at least lower-numbered evaluators are missing in xinput reports. If you compare evtest, xinput and Blender output, you can see that. Apparently Blender prints screen coordinates it receives, which are scaled as compared to xinput and evdev output, but pressure values stay the same - you can use them as the key for comparison. You can see basically one-to-one correspondence between evdev report pieces between SYN_REPORT's and the xinput RawMotion events. If you look up the same reports from Blender, you see that when when lower-numbered valuators are missing (e.g. X), Blender reads pressure as zero. Here's an example. You can forward this message to Blender developers. Blender output: handling tablet event: 0: 891; 1: 617; 2: 543; Resulting tablet data: 0: 891; 1: 617; 2: 0.530792; 3: 0.000000; 4: 0.000000 handling tablet event: 1: 618; 2: 0; Resulting tablet data: 0: 891; 1: 618; 2: 0.000000; 3: 0.000000; 4: 0.000000 handling tablet event: 1: 619; 2: 0; Resulting tablet data: 0: 891; 1: 619; 2: 0.000000; 3: 0.000000; 4: 0.000000 handling tablet event: 1: 619; Resulting tablet data: 0: 891; 1: 619; 2: 0.000000; 3: 0.000000; 4: 0.000000 handling tablet event: 1: 620; 2: 0; Resulting tablet data: 0: 891; 1: 620; 2: 0.000000; 3: 0.000000; 4: 0.000000 handling tablet event: 0: 891; 1: 620; Resulting tablet data: 0: 891; 1: 620; 2: 0.000000; 3: 0.000000; 4: 0.000000 handling tablet event: 1: 621; Resulting tablet data: 0: 891; 1: 621; 2: 0.000000; 3: 0.000000; 4: 0.000000 handling tablet event: 1: 621; 2: 0; Resulting tablet data: 0: 891; 1: 621; 2: 0.000000; 3: 0.000000; 4: 0.000000 handling tablet event: 1: 622; Resulting tablet data: 0: 891; 1: 622; 2: 0.000000; 3: 0.000000; 4: 0.000000 handling tablet event: 0: 891; 1: 622; 2: 549; Resulting tablet data: 0: 891; 1: 622; 2: 0.536657; 3: 0.000000; 4: 0.000000 Xinput output: EVENT type 17 (RawMotion) device: 8 (8) detail: 0 valuators: flags: 0: 15219.00 (15219.00) 1: 18769.00 (18769.00) 2: 543.00 (543.00) EVENT type 17 (RawMotion) device: 8 (8) detail: 0 valuators: flags: 1: 18790.00 (18790.00) 2: 544.00 (544.00) EVENT type 17 (RawMotion) device: 8 (8) detail: 0 valuators: flags: 1: 18810.00 (18810.00) 2: 545.00 (545.00) EVENT type 17 (RawMotion) device: 8 (8) detail: 0 valuators: flags: 1: 18827.00 (18827.00) EVENT type 17 (RawMotion) device: 8 (8) detail: 0 valuators: flags: 1: 18839.00 (18839.00) 2: 546.00 (546.00) EVENT type 17 (RawMotion) device: 8 (8) detail: 0 valuators: flags: 0: 15222.00 (15222.00) 1: 18847.00 (18847.00) EVENT type 17 (RawMotion) device: 8 (8) detail: 0 valuators: flags: 1: 18864.00 (18864.00) EVENT type 17 (RawMotion) device: 8 (8) detail: 0 valuators: flags: 1: 18876.00 (18876.00) 2: 547.00 (547.00) EVENT type 17 (RawMotion) device: 8 (8) detail: 0 valuators: flags: 1: 18892.00 (18892.00) EVENT type 17 (RawMotion) device: 8 (8) detail: 0 valuators: flags: 0: 15219.00 (15219.00) 1: 18909.00 (18909.00) 2: 549.00 (549.00) Evtest output: Event: time 1462818916.523455, -------------- SYN_REPORT ------------ Event: time 1462818916.531461, type 3 (EV_ABS), code 0 (ABS_X), value 15219 Event: time 1462818916.531461, type 3 (EV_ABS), code 1 (ABS_Y), value 18769 Event: time 1462818916.531461, type 3 (EV_ABS), code 24 (ABS_PRESSURE), value 543 Event: time 1462818916.531461, -------------- SYN_REPORT ------------ Event: time 1462818916.539463, type 3 (EV_ABS), code 1 (ABS_Y), value 18790 Event: time 1462818916.539463, type 3 (EV_ABS), code 24 (ABS_PRESSURE), value 544 Event: time 1462818916.539463, -------------- SYN_REPORT ------------ Event: time 1462818916.547461, type 3 (EV_ABS), code 1 (ABS_Y), value 18810 Event: time 1462818916.547461, type 3 (EV_ABS), code 24 (ABS_PRESSURE), value 545 Event: time 1462818916.547461, -------------- SYN_REPORT ------------ Event: time 1462818916.555483, type 3 (EV_ABS), code 1 (ABS_Y), value 18827 Event: time 1462818916.555483, -------------- SYN_REPORT ------------ Event: time 1462818916.563461, type 3 (EV_ABS), code 1 (ABS_Y), value 18839 Event: time 1462818916.563461, type 3 (EV_ABS), code 24 (ABS_PRESSURE), value 546 Event: time 1462818916.563461, -------------- SYN_REPORT ------------ Event: time 1462818916.571485, type 3 (EV_ABS), code 0 (ABS_X), value 15222 Event: time 1462818916.571485, type 3 (EV_ABS), code 1 (ABS_Y), value 18847 Event: time 1462818916.571485, -------------- SYN_REPORT ------------ Event: time 1462818916.579493, type 3 (EV_ABS), code 1 (ABS_Y), value 18864 Event: time 1462818916.579493, -------------- SYN_REPORT ------------ Event: time 1462818916.587484, type 3 (EV_ABS), code 1 (ABS_Y), value 18876 Event: time 1462818916.587484, type 3 (EV_ABS), code 24 (ABS_PRESSURE), value 547 Event: time 1462818916.587484, -------------- SYN_REPORT ------------ Event: time 1462818916.595473, type 3 (EV_ABS), code 1 (ABS_Y), value 18892 Event: time 1462818916.595473, -------------- SYN_REPORT ------------ Event: time 1462818916.603483, type 3 (EV_ABS), code 0 (ABS_X), value 15219 Event: time 1462818916.603483, type 3 (EV_ABS), code 1 (ABS_Y), value 18909 Event: time 1462818916.603483, type 3 (EV_ABS), code 24 (ABS_PRESSURE), value 549 Event: time 1462818916.603483, -------------- SYN_REPORT ------------ > Apparently the mailing list rejects messages with attached files, so I send > this mail to you. Hmm, this is strange, I didn't get any administrator notifications about that. Nick On 05/09/2016 09:48 PM, YAFU wrote: > It seems that I get something with "xinput --test-xi2" in Blender. Just in case I also attach the file with the output drawing on Pinta app. Pinta does not support pressure sensitivity, but I guess that information is present in the xinput/evtest output anyway. > > Apparently the mailing list rejects messages with attached files, so I send this mail to you. > Thank you. > > 2016-05-09 15:09 GMT-03:00 Nikolai Kondrashov <sp...@gm... <mailto:sp...@gm...>>: > > On 05/09/2016 08:58 PM, YAFU wrote: > > I'm having a weird behavior with xinput. I am using KDE (Kubuntu 14.04). I > can only get an output from "xinput -test 8" (8 is my pen id) when working > with the pen over GTK applications (Firefox for example). I do not get > outputs if I work with the pen over KDE/Qt applications or with Blender. How > could I get the output of "xinput -test" drawing on Blender, thus I could > send you the Blender, evtest and xinput output with the same draw/stroke > over Blender? > > > I suspect the pointer device is being taken over by Blender, but I'm not sure > how exactly that works. You might not be able to do it together with Blender. > > Try "xinput --test-xi2", perhaps that will work. > > Nick > > On 05/09/2016 08:58 PM, YAFU wrote: > > I'm having a weird behavior with xinput. I am using KDE (Kubuntu 14.04). I can only get an output from "xinput -test 8" (8 is my pen id) when working with the pen over GTK applications (Firefox for example). I do not get outputs if I work with the pen over KDE/Qt applications or with Blender. How could I get the output of "xinput -test" drawing on Blender, thus I could send you the Blender, evtest and xinput output with the same draw/stroke over Blender? > > 2016-05-09 13:42 GMT-03:00 Nikolai Kondrashov <sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>>>: > > On 05/09/2016 03:51 PM, YAFU wrote: > > Now that I see, I assumed that "xinput test" was what I got from Blender. If > this is not so, how I can get "xinput test"? > > > I took a look and I don't see the issue in the "evtest" output. > I'd rather suspect Blender, but let's see "xinput test" output first. > > To get "xinput test" output you need the "xinput" tool (package should be > named the same). You'll need to run the "xinput list" command first to figure > out the ID of the device and then run "xinput test <ID>" with the found ID. > You might get several devices in "xinput list" output, the same as in "evtest" > output and you'll need to choose the one that reacts to the pen. > > Nick > > On 05/09/2016 03:51 PM, YAFU wrote: > > Now that I see, I assumed that "xinput test" was what I got from Blender. If this is not so, how I can get "xinput test"? > > 2016-05-09 9:00 GMT-03:00 Nikolai Kondrashov <sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>>>>: > > Hi YAFU, > > On 05/08/2016 04:22 PM, YAFU wrote: > > I appreciate if you can take a look at this report and what developers discussed there: > https://developer.blender.org/T48204 > > > Thanks for the heads-up. The missing coordinate (X/Y) issues crop up in > userspace programs pretty often, get fixed, and then appear again. > > The missing coordinates are perfectly valid according to the xinput protocol, > although e.g. the xf86-input-wacom driver never does them, while > x86-input-evdev always does, and the latter is handling most of the non-Wacom > tablets. > > Now, I haven't seen the zero pressure issue before. The best course of action > would be to see if they appear in "evtest" output as compared to "xinput test" > output. If zero pressure appears in "xinput test" output, but not in "evtest" > output, then it's the xf86-input-evdev driver problem. > > If they appear in both, then the next step would be to look at the > /sys/kernel/debug/hid/*/events output. If they're not there, then it's the > kernel issue. Otherwise, it's likely a hardware issue. > > Nick > > > > > > |
|
From: Nikolai Kondrashov <sp...@gm...> - 2016-05-09 16:42:26
|
On 05/09/2016 03:51 PM, YAFU wrote: > Now that I see, I assumed that "xinput test" was what I got from Blender. If > this is not so, how I can get "xinput test"? I took a look and I don't see the issue in the "evtest" output. I'd rather suspect Blender, but let's see "xinput test" output first. To get "xinput test" output you need the "xinput" tool (package should be named the same). You'll need to run the "xinput list" command first to figure out the ID of the device and then run "xinput test <ID>" with the found ID. You might get several devices in "xinput list" output, the same as in "evtest" output and you'll need to choose the one that reacts to the pen. Nick On 05/09/2016 03:51 PM, YAFU wrote: > Now that I see, I assumed that "xinput test" was what I got from Blender. If this is not so, how I can get "xinput test"? > > 2016-05-09 9:00 GMT-03:00 Nikolai Kondrashov <sp...@gm... <mailto:sp...@gm...>>: > > Hi YAFU, > > On 05/08/2016 04:22 PM, YAFU wrote: > > I appreciate if you can take a look at this report and what developers discussed there: > https://developer.blender.org/T48204 > > > Thanks for the heads-up. The missing coordinate (X/Y) issues crop up in > userspace programs pretty often, get fixed, and then appear again. > > The missing coordinates are perfectly valid according to the xinput protocol, > although e.g. the xf86-input-wacom driver never does them, while > x86-input-evdev always does, and the latter is handling most of the non-Wacom > tablets. > > Now, I haven't seen the zero pressure issue before. The best course of action > would be to see if they appear in "evtest" output as compared to "xinput test" > output. If zero pressure appears in "xinput test" output, but not in "evtest" > output, then it's the xf86-input-evdev driver problem. > > If they appear in both, then the next step would be to look at the > /sys/kernel/debug/hid/*/events output. If they're not there, then it's the > kernel issue. Otherwise, it's likely a hardware issue. > > Nick > > |
|
From: YAFU <yaful...@gm...> - 2016-05-09 12:51:34
|
Now that I see, I assumed that "xinput test" was what I got from Blender. If this is not so, how I can get "xinput test"? 2016-05-09 9:00 GMT-03:00 Nikolai Kondrashov <sp...@gm...>: > Hi YAFU, > > On 05/08/2016 04:22 PM, YAFU wrote: > >> I appreciate if you can take a look at this report and what developers >> discussed there: >> https://developer.blender.org/T48204 >> > > Thanks for the heads-up. The missing coordinate (X/Y) issues crop up in > userspace programs pretty often, get fixed, and then appear again. > > The missing coordinates are perfectly valid according to the xinput > protocol, > although e.g. the xf86-input-wacom driver never does them, while > x86-input-evdev always does, and the latter is handling most of the > non-Wacom > tablets. > > Now, I haven't seen the zero pressure issue before. The best course of > action > would be to see if they appear in "evtest" output as compared to "xinput > test" > output. If zero pressure appears in "xinput test" output, but not in > "evtest" > output, then it's the xf86-input-evdev driver problem. > > If they appear in both, then the next step would be to look at the > /sys/kernel/debug/hid/*/events output. If they're not there, then it's the > kernel issue. Otherwise, it's likely a hardware issue. > > Nick > |
|
From: Nikolai Kondrashov <sp...@gm...> - 2016-05-09 12:00:24
|
Hi YAFU, On 05/08/2016 04:22 PM, YAFU wrote: > I appreciate if you can take a look at this report and what developers discussed there: > https://developer.blender.org/T48204 Thanks for the heads-up. The missing coordinate (X/Y) issues crop up in userspace programs pretty often, get fixed, and then appear again. The missing coordinates are perfectly valid according to the xinput protocol, although e.g. the xf86-input-wacom driver never does them, while x86-input-evdev always does, and the latter is handling most of the non-Wacom tablets. Now, I haven't seen the zero pressure issue before. The best course of action would be to see if they appear in "evtest" output as compared to "xinput test" output. If zero pressure appears in "xinput test" output, but not in "evtest" output, then it's the xf86-input-evdev driver problem. If they appear in both, then the next step would be to look at the /sys/kernel/debug/hid/*/events output. If they're not there, then it's the kernel issue. Otherwise, it's likely a hardware issue. Nick |
|
From: YAFU <yaful...@gm...> - 2016-05-08 13:22:59
|
Hello. I appreciate if you can take a look at this report and what developers discussed there: https://developer.blender.org/T48204 |
1 message has been excluded from this view by a project administrator.
Oh no! Some styles failed to load. 😵
Please try reloading this page