Reply to topic

Graphics Tablet assign to one monitor of dual display setup

User avatar orbmiser
Registered Member
Posts
93
Karma
1
Yep run dual monitors and have a Huion H610 graphics tablet. 6 months ago.
And didn't run in Krita pre-2.8 Linux side but worked in Windows 7 side.

Fast forward to present and 2.9.1 works great in both OS'es But on Linux tablet spans both monitors.
And don't see a setting for limiting Krita to one monitor. Or a way to assign the Action keys to actions.
As stands now active area on tablet covers both monitors. Can draw only using 1st half of area.

Image

Any help on this? As don't see any linux based tablet apps like windows.
Where you can in windows setup calibration and assign my 8 keys to Krita actions.
Assign stylus buttons actions and switch it to left-handed drawing.

Anything in the works? 3rd party? Hacks or solutions to this situation?

Thanks any help insights into this is greatly appreciated. As have to boot to Windows 7 side to use tablet to it's fullest.

.


User avatar halla
KDE Developer
Posts
5037
Karma
20
OS
If it were a wacom, I'd say you need to use the xsetwacom commandline utility. Looking at the faq, I think that you should be able to do this with xinput_calibrator.
User avatar orbmiser
Registered Member
Posts
93
Karma
1
I was afraid of that as more a general hack than a solution. As found the instructions on Krita FAQ.

For this, first you need to install xinput-calibrator (check in your package manager it may be named a bit differently, with – or _ in the middle…)

Now, you’ll need the name or ID of your device, so list devices with this command line:

xinput_calibrator --list | grep H610

Then I noticed the huion report two different devices with the same name, just different ID. So to find out which is the one corresponding to the actual stylus tablet area, get devices values with this command line:

xinput_calibrator --device 10

(adapt id number the the values you found on previous step…)

It will open a sort of calibration window, don’t click the crosses, just press any key to abort. Then you can see the default values of the device appeared in the console. One devices has much bigger max values (0 40000 0 25000), this is the one you should get the ID number. (in my case here was ID 10 )

Then calculate the values to set the active area to the same ratio as screen..
For example, for a 1920×1080 screen, I did this operation: 40000*1080/1920=22500

And finally set the calibration values (TopX BottomX TopY BottomY) like this:
xinput set-prop 10 “Evdev Axis Calibration” 0 40000 0 22500


Guess I'll have to deal with it and try fiddling with.

.


User avatar Aduah
Registered Member
Posts
15
Karma
1
OS
I'm having this same problem however I am using a wacom tablet and I use windows 7 x64 Professional. I'm using the Wacom Intuos Pro touch. Krita completely ignores the fact that I only have the tablet limited to one of the 2 monitors. I am not having this problem on any other program. As soon as the Krita program is selected, it starts ignoring the the bounds and makes my tablet surface span the entirety of both of my monitors. Please help!

Also, please note I am not savy with code or anything like that. I'm just an artist so I dont really know anything about command line features and stuff like that. x.x
User avatar orbmiser
Registered Member
Posts
93
Karma
1
Sorry don't have issue using my Huion with Krita in Windows 7 as the installed huion software dialog allowed me to choose which monitor and works as expected. Using version 2.9.1 as earlier versions I did have issues. So if opening up your Wacom software and have the right monitor chosen where Krita opens on selected. Don't know what else I can think of that will help.

.


User avatar Aduah
Registered Member
Posts
15
Karma
1
OS
This is too bad. Thanks for the reply anyways. I'm not sure what to do. I have even tried updating my Wacom drivers. It doesn't make any difference at all. I tried assigning different screens, or even using a portion of the monitor instead. Nothing effects it at all. Unfortunately since this is problem that only is effecting Krita I can't find any solutions anywhere. I am unable to determine if this is a unique problem to just me or if others are having the same issue.
enjalu
Registered Member
Posts
2
Karma
0
Probably this a solution for you:
xinput set-prop 10 --type=float "Coordinate Transformation Matrix" 0.5 0 0.5 0 1 0 0 0 1

or:
xinput set-prop 10 --type=float "Coordinate Transformation Matrix" 0.5 0 0 0 1 0 0 0 1
hthorsteinsson
Registered Member
Posts
1
Karma
0
Enjalu is correct, this is normal default behaviour for the xinput system -- it maps the pointer device to the entire extended desktop.
You can reset the range by hand as enjalu suggests, but it got a bit annoying for me and a colleague so we started developing a simple GUI called PTXConf. It would be helpful if people would try it out and see if it is useful, see instructions here:

http://wenhsinjen.github.io/ptxconf/

All you should have to do is select your input pen or touch device and then select which monitor you want to map it too, all graphical.
Maybe some Linux distros already have such a GUI tool... we don't know... but Ubuntu at least messed it up by only supporting Wacom pen devices for this... quite silly we think, because xorg xinput already supports this reconfiguration for many years.
Anyway please try it, we need some input on how it works with your devices and screen setup.
User avatar timotimo
Registered Member
Posts
72
Karma
1
OS
Wow, why are all these methods so darn complicated?

I find this much easier:

Code: Select all
$ xinput  # get the IDs for all relevant pieces of my tablet.
⎡ Virtual core pointer                       id=2   [master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer                 id=4   [slave  pointer  (2)]
[...]
⎜   ↳ Wacom Bamboo 16FG 4x5 Pen stylus           id=17   [slave  pointer  (2)]
⎜   ↳ Wacom Bamboo 16FG 4x5 Pen eraser           id=20   [slave  pointer  (2)]
⎜   ↳ Wacom Bamboo 16FG 4x5 Pad pad              id=21   [slave  pointer  (2)]
⎜   ↳ Wacom Bamboo 16FG 4x5 Finger               id=22   [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)]
    ↳ Power Button                               id=7   [slave  keyboard (3)]
    ↳ Microsoft Microsoft® Nano Transceiver v2.1   id=13   [slave  keyboard (3)]
[...]
$ xrandr  # get the names of my displays
Screen 0: minimum 8 x 8, current 3840 x 1200, maximum 16384 x 16384
DVI-I-0 disconnected (normal left inverted right x axis y axis)
[...]
DVI-I-3 connected 1920x1200+1920+0 (normal left inverted right x axis y axis) 546mm x 352mm
   1920x1200     59.95*+
   1920x1080     60.00 
   1680x1050     59.95 
[...]
DP-1 connected 1920x1200+0+0 (normal left inverted right x axis y axis) 546mm x 352mm
   1920x1200     59.95*+
   1920x1080     60.00    59.99    59.94    50.00    60.05    60.00    50.04 
   1680x1050     59.95 
[...]
$ xinput map-to-output 17 DVI-I-3
$ xinput map-to-output 20 DVI-I-3
$ xinput map-to-output 21 DVI-I-3
$ xinput map-to-output 22 DVI-I-3


No calculations necessary! No weird xinput_calibrator necessary! hooray!

 
Reply to topic

Bookmarks



Who is online

Registered users: Alexa [Bot], Baidu [Spider], Bing [Bot], claydoh, Google [Bot], jtracker, Majestic-12 [Bot], Massimiliano, rachelpayne, Sogou [Bot], Yahoo [Bot]