Thread: [DIGImend-users] Monoprice MP1060-HA60
Brought to you by:
spb_nick
From: Matt H. <mat...@gm...> - 2013-02-13 05:35:44
|
Hi All- Recently purchased the Monoprice HA60. It works on MacOS, pressure sensitivity works with the driver config software (not with gimp nor mypaint). On Ubuntu 12-10 with a 3.7 kernel it somewhat works: - Gimp 2.8.2 - Stops drawing after a while - Intermittently draws lines to left, top or left/top corner - Some semblance of pressure sensitivity (though first two issues make it hard to tell) - Inkscape - In the "File->Input Devices" box, after activating the device in the "Configuration" tab, I can see pressure register in the 3rd axis down in the "Hardware" "Test Area". I'm not sure how to make the calligraphy pen or other pens take advantage of pressure - Intermittently draws lines to left, top or left/top corner - MyPaint 1.1 - Not sure how to configure/test pressure - Intermittently draws lines to left, top or left/top corner Am willing to provide any more info that is needed. Would like to have this work consistently. Thanks for your hard work! cheers, -matt |
From: Nikolai K. <sp...@gm...> - 2013-02-13 09:23:46
|
Hi Matt, On 02/13/2013 07:35 AM, Matt Harrison wrote: > Recently purchased the Monoprice HA60. It works on MacOS, pressure > sensitivity works with the driver config software (not with gimp nor > mypaint). > > On Ubuntu 12-10 with a 3.7 kernel it somewhat works: > > - Gimp 2.8.2 > - Stops drawing after a while > - Intermittently draws lines to left, top or left/top corner > - Some semblance of pressure sensitivity (though first two issues > make it hard to tell) > > - Inkscape > - In the "File->Input Devices" box, after activating the device in > the "Configuration" tab, I can see pressure register in the 3rd axis > down in the "Hardware" "Test Area". I'm not sure how to make the > calligraphy pen or other pens take advantage of pressure > - Intermittently draws lines to left, top or left/top corner > > - MyPaint 1.1 > - Not sure how to configure/test pressure > - Intermittently draws lines to left, top or left/top corner > > Am willing to provide any more info that is needed. Would like to have > this work consistently. Thanks for your hard work! Do you use a multi-monitor setup in Ubuntu? Sincerely, Nick |
From: Matt H. <mat...@gm...> - 2013-02-13 14:00:18
|
On Wed, Feb 13, 2013 at 2:23 AM, Nikolai Kondrashov <sp...@gm...> wrote: > Hi Matt, > > > On 02/13/2013 07:35 AM, Matt Harrison wrote: >> >> Recently purchased the Monoprice HA60. It works on MacOS, pressure >> sensitivity works with the driver config software (not with gimp nor >> mypaint). >> >> On Ubuntu 12-10 with a 3.7 kernel it somewhat works: >> >> - Gimp 2.8.2 >> - Stops drawing after a while >> - Intermittently draws lines to left, top or left/top corner >> - Some semblance of pressure sensitivity (though first two issues >> make it hard to tell) >> >> - Inkscape >> - In the "File->Input Devices" box, after activating the device in >> the "Configuration" tab, I can see pressure register in the 3rd axis >> down in the "Hardware" "Test Area". I'm not sure how to make the >> calligraphy pen or other pens take advantage of pressure >> - Intermittently draws lines to left, top or left/top corner >> >> - MyPaint 1.1 >> - Not sure how to configure/test pressure >> - Intermittently draws lines to left, top or left/top corner >> >> Am willing to provide any more info that is needed. Would like to have >> this work consistently. Thanks for your hard work! > > > Do you use a multi-monitor setup in Ubuntu? > Yes, but I see the same behavior with the external monitor disconnected. -matt > Sincerely, > Nick |
From: Nikolai K. <sp...@gm...> - 2013-02-13 14:04:25
|
On 02/13/2013 04:00 PM, Matt Harrison wrote: >> Do you use a multi-monitor setup in Ubuntu? > > Yes, but I see the same behavior with the external monitor disconnected. Could you please show output of "xinput list" and "xinput list-props ID", where "ID" is the ID of your tablet input device as seen in "xinput list" output? Thank you. Sincerely, Nick |
From: Matt H. <mat...@gm...> - 2013-02-13 14:09:39
|
On Wed, Feb 13, 2013 at 7:04 AM, Nikolai Kondrashov <sp...@gm...> wrote: > > Could you please show output of "xinput list" and "xinput list-props ID", > where "ID" is the ID of your tablet input device as seen in "xinput list" > output? > I'm assuming that "HA60S" appearing as both a "core pointer" and a "core keyboard" is not a problem? matt@t61:~$ xinput list ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ HA60S id=9 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=12 [slave pointer (2)] ⎜ ↳ TPPS/2 IBM TrackPoint id=13 [slave pointer (2)] ⎣ Virtual core keyboard id=3 [master keyboard (2)] ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)] ↳ Power Button id=6 [slave keyboard (3)] ↳ Video Bus id=7 [slave keyboard (3)] ↳ Sleep Button id=8 [slave keyboard (3)] ↳ HA60S id=10 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=11 [slave keyboard (3)] ↳ ThinkPad Extra Buttons id=14 [slave keyboard (3)] matt@t61:~$ xinput list-props 9 Device 'HA60S': Device Enabled (134): 1 Coordinate Transformation Matrix (136): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000 Device Accel Profile (258): 0 Device Accel Constant Deceleration (259): 1.000000 Device Accel Adaptive Deceleration (260): 1.000000 Device Accel Velocity Scaling (261): 10.000000 Device Product ID (251): 21827, 1921 Device Node (252): "/dev/input/event8" Evdev Axis Inversion (262): 0, 0 Evdev Axis Calibration (263): <no items> Evdev Axes Swap (264): 0 Axis Labels (265): "Abs X" (255), "Abs Y" (256), "Abs Pressure" (257) Button Labels (266): "Button Unknown" (254), "Button Unknown" (254), "Button Unknown" (254), "Button Wheel Up" (140), "Button Wheel Down" (141), "Button Horiz Wheel Left" (142), "Button Horiz Wheel Right" (143) Evdev Middle Button Emulation (267): 0 Evdev Middle Button Timeout (268): 50 Evdev Third Button Emulation (269): 0 Evdev Third Button Emulation Timeout (270): 1000 Evdev Third Button Emulation Button (271): 3 Evdev Third Button Emulation Threshold (272): 20 Evdev Wheel Emulation (273): 0 Evdev Wheel Emulation Axes (274): 0, 0, 4, 5 Evdev Wheel Emulation Inertia (275): 10 Evdev Wheel Emulation Timeout (276): 200 Evdev Wheel Emulation Button (277): 4 Evdev Drag Lock Buttons (278): 0 matt@t61:~$ xinput list-props 10 Device 'HA60S': Device Enabled (134): 1 Coordinate Transformation Matrix (136): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000 Device Product ID (251): 21827, 1921 Device Node (252): "/dev/input/event9" -matt |
From: Nikolai K. <sp...@gm...> - 2013-02-13 17:15:38
|
On 02/13/2013 04:09 PM, Matt Harrison wrote: > I'm assuming that "HA60S" appearing as both a "core pointer" and a > "core keyboard" is not a problem? No, it's not a problem. The pointer device is for the pen and the keyboard device is for the buttons on the frame. The xinput output looks fine. It could be another X.org or evdev issue. Could you please capture some "evtest" output for the pen device (the one that produces output on pen movement), long enough to have possible "jumps" occur. It may work in X, but if evtest says that the device is grabbed, you will need to run it from the console. Thank you. Sincerely, Nick |
From: Matt H. <mat...@gm...> - 2013-02-14 05:16:42
|
Atta On Wed, Feb 13, 2013 at 10:15 AM, Nikolai Kondrashov <sp...@gm...> wrote: > On 02/13/2013 04:09 PM, Matt Harrison wrote: >> >> I'm assuming that "HA60S" appearing as both a "core pointer" and a >> "core keyboard" is not a problem? > > > No, it's not a problem. The pointer device is for the pen and the keyboard > device is for the buttons on the frame. > > The xinput output looks fine. It could be another X.org or evdev issue. > > Could you please capture some "evtest" output for the pen device (the one > that > produces output on pen movement), long enough to have possible "jumps" > occur. > > It may work in X, but if evtest says that the device is grabbed, you will > need > to run it from the console. > > Thank you. > > Sincerely, > Nick Hmmmm, I tried running evtest for a while (a quick python script to parse it shows that it probably didn't jump). But am attaching a gimp screenie to prove I'm not completely delusional. advice? -matt |
From: Nikolai K. <sp...@gm...> - 2013-02-14 07:00:19
|
Hi Matt, On 02/14/2013 07:16 AM, Matt Harrison wrote: > Hmmmm, I tried running evtest for a while (a quick python script to > parse it shows that it probably didn't jump). But am attaching a gimp > screenie to prove I'm not completely delusional. > > advice? Thank you. This is as I suspected. This suggests that kernel reports correct coordinates, but either xf86-input-evdev or X.org input subsystem mess it up somewhere. I'll have to try to debug it myself. Still, "xinput test" output for the pen device, while it jumps, might be useful. Sincerely, Nick |
From: Matt H. <mat...@gm...> - 2013-02-14 13:39:00
Attachments:
ev8-ink2.txt
ink-jump.jpg
|
On Thu, Feb 14, 2013 at 12:00 AM, Nikolai Kondrashov <sp...@gm...> wrote: > Hi Matt, > > > On 02/14/2013 07:16 AM, Matt Harrison wrote: >> >> Hmmmm, I tried running evtest for a while (a quick python script to >> parse it shows that it probably didn't jump). But am attaching a gimp >> screenie to prove I'm not completely delusional. >> >> advice? > > > Thank you. This is as I suspected. This suggests that kernel reports correct > coordinates, but either xf86-input-evdev or X.org input subsystem mess it up > somewhere. > > I'll have to try to debug it myself. > > Still, "xinput test" output for the pen device, while it jumps, might be > useful. > Ok, here's evtest output (I assume you meant that instead of "xinput test"?) when it jumped during inkscape. Also screenie of jumping. cheers, -matt |
From: Nikolai K. <sp...@gm...> - 2013-02-14 13:46:16
|
On 02/14/2013 03:38 PM, Matt Harrison wrote: > Ok, here's evtest output (I assume you meant that instead of "xinput > test"?) when it jumped during inkscape. Also screenie of jumping. Thanks, this can also help, but I meant "xinput test ID" output, where ID is the ID of the tablet pen device. Sincerely, Nick |
From: Matt H. <mat...@gm...> - 2013-02-14 13:50:29
Attachments:
xinput13-ink.txt
|
On Thu, Feb 14, 2013 at 6:46 AM, Nikolai Kondrashov <sp...@gm...> wrote: > On 02/14/2013 03:38 PM, Matt Harrison wrote: >> >> Ok, here's evtest output (I assume you meant that instead of "xinput >> test"?) when it jumped during inkscape. Also screenie of jumping. > > > Thanks, this can also help, but I meant "xinput test ID" output, where ID is > the ID of the tablet pen device. Here you go (output with inkscape jump to upper left corner). -matt |
From: Matt H. <mat...@gm...> - 2013-02-16 01:18:50
|
I have confirmed that my waltop penpad works fine with gimp and my paint. Apparently I am too dense to figure out hour to make pressure work with inks cape. Regardless there is no jumping to top or left with that device. On Feb 14, 2013 6:50 AM, "Matt Harrison" <mat...@gm...> wrote: > On Thu, Feb 14, 2013 at 6:46 AM, Nikolai Kondrashov <sp...@gm...> > wrote: > > On 02/14/2013 03:38 PM, Matt Harrison wrote: > >> > >> Ok, here's evtest output (I assume you meant that instead of "xinput > >> test"?) when it jumped during inkscape. Also screenie of jumping. > > > > > > Thanks, this can also help, but I meant "xinput test ID" output, where > ID is > > the ID of the tablet pen device. > > Here you go (output with inkscape jump to upper left corner). > > -matt > |
From: Nikolai K. <sp...@gm...> - 2013-02-19 09:09:53
|
Hi Matt, On 02/16/2013 03:18 AM, Matt Harrison wrote: > I have confirmed that my waltop penpad works fine with gimp and my paint. > Apparently I am too dense to figure out hour to make pressure work with inks > cape. Regardless there is no jumping to top or left with that device. The jumps shouldn't be there, regardless the setup. The setup is only needed for pressure sensitivity usually. I suspect that PenPad gets handled by xf86-input-wacom driver, which reports pen coordinates in a way that don't trigger the bug seen with xf86-input-evdev. Could you please show "xinput list-props" output for the PenPad? Thank you. Sincerely, Nick |
From: Matt H. <mat...@gm...> - 2013-02-19 14:16:09
|
On Tue, Feb 19, 2013 at 2:09 AM, Nikolai Kondrashov <sp...@gm...> wrote: > Hi Matt, > > > On 02/16/2013 03:18 AM, Matt Harrison wrote: >> >> I have confirmed that my waltop penpad works fine with gimp and my paint. >> Apparently I am too dense to figure out hour to make pressure work with >> inks >> cape. Regardless there is no jumping to top or left with that device. > > > The jumps shouldn't be there, regardless the setup. The setup is only needed > for pressure sensitivity usually. > > I suspect that PenPad gets handled by xf86-input-wacom driver, which reports > pen coordinates in a way that don't trigger the bug seen with > xf86-input-evdev. > > Could you please show "xinput list-props" output for the PenPad? > Thank you. > You are correct it appears to be using the Wacom driver. $ xinput list-props 12 Device ' WALTOP Tablet stylus': Device Enabled (134): 1 Coordinate Transformation Matrix (136): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000 Device Accel Profile (258): 0 Device Accel Constant Deceleration (259): 1.000000 Device Accel Adaptive Deceleration (260): 1.000000 Device Accel Velocity Scaling (261): 10.000000 Device Node (252): "/dev/input/event8" Wacom Tablet Area (642): 0, 0, 12288, 9216 Wacom Rotation (643): 0 Wacom Pressurecurve (644): 0, 0, 100, 100 Wacom Serial IDs (645): 55, 0, 2, 0, 0 Wacom Serial ID binding (646): 0 Wacom Pressure Threshold (647): 27 Wacom Sample and Suppress (648): 2, 4 Wacom Enable Touch (649): 0 Wacom Hover Click (650): 1 Wacom Enable Touch Gesture (651): 0 Wacom Touch Gesture Parameters (652): 0, 0, 250 Wacom Tool Type (653): "STYLUS" (641) Wacom Button Actions (654): "Wacom button action 0" (655), "Wacom button action 1" (656), "Wacom button action 2" (657) Wacom button action 0 (655): 1572865 Wacom button action 1 (656): 1572866 Wacom button action 2 (657): 1572867 Device Product ID (251): 5935, 55 Wacom Debug Levels (658): 0, 0 |
From: Matt H. <mat...@gm...> - 2013-02-20 03:53:01
|
On Tue, Feb 19, 2013 at 7:15 AM, Matt Harrison <mat...@gm...> wrote: > On Tue, Feb 19, 2013 at 2:09 AM, Nikolai Kondrashov <sp...@gm...> wrote: >> Hi Matt, >> >> >> On 02/16/2013 03:18 AM, Matt Harrison wrote: >>> >>> I have confirmed that my waltop penpad works fine with gimp and my paint. >>> Apparently I am too dense to figure out hour to make pressure work with >>> inks >>> cape. Regardless there is no jumping to top or left with that device. >> >> >> The jumps shouldn't be there, regardless the setup. The setup is only needed >> for pressure sensitivity usually. >> >> I suspect that PenPad gets handled by xf86-input-wacom driver, which reports >> pen coordinates in a way that don't trigger the bug seen with >> xf86-input-evdev. >> >> Could you please show "xinput list-props" output for the PenPad? >> Thank you. >> > > You are correct it appears to be using the Wacom driver. > I disabled wacom support for Waltop devices by commenting out the following lines in the file /usr/share/X11/xorg.conf.d/50-wacom.conf : # Waltop tablets # Section "InputClass" # Identifier "Waltop class" # MatchProduct "WALTOP" # MatchIsTablet "on" # MatchDevicePath "/dev/input/event*" # Driver "wacom" # EndSection I then created the directory/file /etc/X11/xorg.conf.d/52-tablet.conf : Section "InputClass" Identifier "Waltop class" MatchProduct "WALTOP" MatchDriver "evdev" MatchIsPointer "on" MatchDevicePath "/dev/input/event*" # Apply custom Options below. EndSection After restarting X I confirmed that evdev was being used in my Waltop tablet. It appears to work equally well to the wacom driver ie no stuttering, pressure support in Gimp/Mypaint and ability to draw long lines in Gimp. I'll take it from that that my applications appear to be ok (still no pressure support in inkscape). -matt |
From: Matt H. <mat...@gm...> - 2013-02-20 05:36:24
Attachments:
mypaint.png
|
On Tue, Feb 19, 2013 at 8:52 PM, Matt Harrison <mat...@gm...> wrote: > On Tue, Feb 19, 2013 at 7:15 AM, Matt Harrison > <mat...@gm...> wrote: >> On Tue, Feb 19, 2013 at 2:09 AM, Nikolai Kondrashov <sp...@gm...> wrote: >>> Hi Matt, >>> >>> >>> On 02/16/2013 03:18 AM, Matt Harrison wrote: >>>> >>>> I have confirmed that my waltop penpad works fine with gimp and my paint. >>>> Apparently I am too dense to figure out hour to make pressure work with >>>> inks >>>> cape. Regardless there is no jumping to top or left with that device. >>> >>> >>> The jumps shouldn't be there, regardless the setup. The setup is only needed >>> for pressure sensitivity usually. >>> >>> I suspect that PenPad gets handled by xf86-input-wacom driver, which reports >>> pen coordinates in a way that don't trigger the bug seen with >>> xf86-input-evdev. >>> >>> Could you please show "xinput list-props" output for the PenPad? >>> Thank you. >>> >> >> You are correct it appears to be using the Wacom driver. >> > > I disabled wacom support for Waltop devices by commenting out the > following lines in the file /usr/share/X11/xorg.conf.d/50-wacom.conf : > > # Waltop tablets > # Section "InputClass" > # Identifier "Waltop class" > # MatchProduct "WALTOP" > # MatchIsTablet "on" > # MatchDevicePath "/dev/input/event*" > # Driver "wacom" > # EndSection > > I then created the directory/file /etc/X11/xorg.conf.d/52-tablet.conf : > > Section "InputClass" > Identifier "Waltop class" > MatchProduct "WALTOP" > MatchDriver "evdev" > MatchIsPointer "on" > MatchDevicePath "/dev/input/event*" > # Apply custom Options below. > EndSection > > After restarting X I confirmed that evdev was being used in my Waltop > tablet. It appears to work equally well to the wacom driver ie no > stuttering, pressure support in Gimp/Mypaint and ability to draw long > lines in Gimp. > > I'll take it from that that my applications appear to be ok (still no > pressure support in inkscape). > > -matt I spoke too soon. Waltop is also "jumping" with evdev. See screenie. -matt |