New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for mapping all Cintiq 12WX Auxiliary buttons #3222
Comments
@Megalomaniak could you test the action build here please? Downloads are at the bottom. Source code is available in #3241 and #3242 if you would like to see or compile the changes yourself. |
@jamesbt365 Since I'm on linux I presume I need both the linux build and the udev rules? Or is the build alone enough? |
Aaa I love the website on mobile jumping around! If you are keeping a packaged version of OTD installed you dont need to download the rules, if you are compiling a packaged build they'll come included,if you dont have OTD installed yes, youll need the rules. |
OK, I'm normally using OTD-git from Aur so I guess I just need the binary then, now if only I could find some install instructions for this. Or maybe I really should try git pull and build... |
I'm highly against the usage of OTD-git, there is absolutely no benefits of using it over a release build and it only brings more issues to the table, it runs on a different codebase which is way more unstable and lacking features as of right now, alongside a bunch of regressions & other bugs. Here is a file you can directly install with If you don't trust the package i sent, you can build one yourself by running the scripts Then move the created tar.gz next to a pkgbuild with the source set to If you are insistent on using a build based off |
I see, good to know I suppose tho I have to admit 7.0/OTD-git has been working decently for me where previously I couldn't even get 6.x to work(admittedly I was trying to install it after being away from linux for a decade, may have just lucked out with OTD-git/7.0). |
You likely never could get it to work because you already had 0.7 settings, which are not compatible with 0.6.x, remove the ~/.config/OpenTabletDriver directory. |
No I meant I had tried 0.6.x before I found the aur for 0.7. Anyways, installed the above package and time for restart... |
|
May bad, uploaded the wrong file and instead gave you a release build. |
The parsing and pipeline is functionally the same as 0.7, so nothing different should be happening here, could you check the tablet > tablet debugger to see if its happening there? if it isn't, its probably a bug with krita because OTDs virtual tablet is nothing different to a real tablet without any passthrough. |
Are we certain it is the correct one this time. As in should I rename this latest one to |
Its the right one this time. |
I asked because the tarball is missing package metadata so |
I... uh, renamed and uploaded the wrong file... Why do they have to be called such similar things, shame on me for not double checking. |
So far seems to be the same as the first one you uploaded. I made sure to download the newlinked one as And only 8 Aux buttons show up to be clear. |
Well then I either fucked up for 1000th time at 1am with my 1000 folders named OpenTabletDriver which is very likely or its something else. You are welcome to attempt this yourself with the PKGBUILD from the aur and building off the backport PR, or just running off the tarball in the action builds. I'll look at this thread when I wake up. |
Yeah.... I've been suspecting for a while now that since you tried to upload a file with the same exact name it(that being github) decided to drop the file upload and instead attached a link to the exact same file in that latest post. If that makes sense... If you ctrl+F to check it's the exact same file name in both comment posts. Github is probably trying to be a good boi and not waste daddy microsofts money on hosting duplicates of the same file. Anyways, I'm not actually in a hurry either so I'll just wish you good night for now and check back in tomorrow. I'm actually surprised someone chose to look into resolving this issue ticket as soon as you did, and I genuinely do appreciate it. I'll try and explore the PKGBUILD idea from the aur if I can figure out how to obtain it(probably not too complicated, right? Just got to look in the right place), but if you happen to try and upload with a different file name again maybe I'll be proven right about my above theory. Could be good to know just to avoid the same issue elsewhere in the future. |
OK, I've copied the PKGBUILD from the aur:
Replaced the SHA256sums with SKIP, but other than that, how to actually get the exact branch and pull request needed from github is still a mystery to me. |
Manufacturer
Wacom
Product Name
DTZ-1200W
Device Width
No response
Device Height
No response
Pressure Levels
No response
Lines per Inch (LPI)
No response
Additional Information
The Wacom Cintiq 12 WX currently falls back to using Intuos 3 Configuration best that I can tell. Which mostly works, except unlike the Intuos 3 which has only 8 Auxiliary buttons total (4 on each side) the Cintiq 12 WX features 10 total, 5 on each side.
Opening the Debugger and pressing the 2 missing buttons I see a change in RAW values so I recon it should be possible to support them?
Whether to resolve this by adding the configurability of the 2 additional buttons via the Intuos 3 config or by giving the Cintiq 12 WX it's own unique config I'm not sure. Intuition says latter would be more appropriate however since the devices are so similar perhaps the former makes more sense in terms of technical debt.
RAW values for the 2 missing buttons
Report Type: OpenTabletDriver.Configurations.Parsers.Wacom.Intuos3.Intuos3Aux-Report
and as an example of Aux button that is mappable, rest of the buttons on right:
While at it perhaps it's also worth a mention that similar to Intuos 3 the 12WX has touch strips on each side and I can see value changes in debugger also from their input.
Touchstrip RAW value ranges
Report Type: OpenTabletDriver.Configurations.Parsers.Wacom.Intuos3.Intuos3Aux-Report
Values are obtained by sliding the finger over the strip from top to bottom, 1 state per line
Left touch strip values
And same but 2 column positions over to the right for right strip
Right touch strip values
I'm mostly concerned with the buttons however I can see the value in being able to use the touch strips in something like krita for brush size or canvas rotation for an example. But mapping these functions to the strips should probably be done in the respective application settings rather than the driver config since it's application specific. So that might have to be a feature request for a tracker elsewhere I'm guessing. Woe unto me, Krita is part of KDE family and they use a common bugzilla instance for all of them. Ugh.
Let me know if I can provide any extra feedback.
Diagnostic Information
File is too large for github so I've created a public gist:
https://gist.github.com/Megalomaniak/b93383301b8dc589ca4ce59da0fef054
Acknowledgements
The text was updated successfully, but these errors were encountered: