On Fri, Jan 14, 2011 at 1:06 PM, AndrewP <[email protected]> wrote: > in isdv4-debugger shows maximum of 255 when I apply considerable force, and > pressure increases gradually. > while in xinput it seems to be overly sensitive and very limited in range, > although it is scaled to 2048 anyway. > > I miss earlier, that in the beginning isdv4-debugger reports: > > TABLET: version: 992 > TABLET: x max: 26312 y max 16520 > TABLET: tilt_x max: 0 tilt_y max 0 > TABLET: pressure max: 127 > > which means, what I did was insufficient, when put "common -> wcmMaxZ = > 255;" in wcmISVD4.c
Right. So as long as common->wcmMaxZ is allowed to be 127, xf86-input-wacom will think your apply twice the pressure you really are. So at 50% pressure, it will read 2048 in xinput. Hardcoding to 255 in wcmISDV4.c and giving a higher wcmThreshold should resolve a lot of your false clicks. But you were getting some "bursts" of high pressures in the other log (50% pressure almost) before touching the tablet. I do not know how to resolve that issue. Chris > > here's rest of the isdv4-debugger output: http://dpaste.org/FzTo/ > > I noticed one more thing, when I get "false" clicks, except increasing > pressure and letter "p", letter "t" also appears. > I guess it means "touch"? so driver registers touch event, on my pen only > tablet. > > > > On Fri, Jan 14, 2011 at 19:09, Chris Bagwell <[email protected]> wrote: >> >> Please forgive if you've mentioned this aready... we follow lots of >> different issues and on lots of different projects so its easy to loss >> information. >> >> Can you be specific on how isdv4-debugger indicates no issues? >> >> Do you mean it reports pressure ranges 0-255? I think your log files >> showed that was basically being received with xf86-input-wacom as >> well. In this case, one of problems is simply scaling from expected >> 127 values up to 2048 will obviously give you inflated pressure values >> if hardware is really sending 255 values. Telling it to scale from >> 255 to 2048 will require more pressure before you get the click. >> >> Or are you saying that isdv4-debugger reports a maximum pressure of >> 255 yet xf86-input-wacom reports only 127? They both use extremely >> similar code and sequences so I suspect by both report maximum of 127. >> >> Chris >> >> On Fri, Jan 14, 2011 at 9:46 AM, AndrewP <[email protected]> wrote: >> > It didn't help to my senses. But tell me why tempering with ISDV4 could >> > help >> > if isdv4-debugger indicates no apparent troubles? >> > >> > On Fri, Jan 14, 2011 at 17:31, Chris Bagwell <[email protected]> >> > wrote: >> >> >> >> You might try modifying the wcmISDV4.c file and force the setting of >> >> common->wcmMaxZ to be 256 and play around with the tablet to see if it >> >> works better for you. >> >> >> >> These values are coming straight from tablet so not sure why it would >> >> be reporting 127 is its max but giving you values above that range. >> >> >> >> If forcing it to 256 doesn't help your usability then it may not be >> >> worth continuing. >> >> >> >> If it does help then we could do some sort of tablet version detection >> >> and hard code in software I guess. It should help at least a little >> >> because it won't scale up to 2048 pressure range quite so fast. >> >> >> >> Chris >> >> >> >> On Thu, Jan 13, 2011 at 10:12 PM, AndrewP <[email protected]> wrote: >> >> > Also my top priority is pressure level's range. This pen got only 256 >> >> > level >> >> > which are displayed in isdv4-debugger properly. And I have only half >> >> > of >> >> > it >> >> > in X. As you probably remember xinput maxed to 2048, when >> >> > isdv4-debugger >> >> > showed around 100. >> >> > I mean isdv4-debugger shows sense to me, so why it should be a >> >> > hardware >> >> > issue? >> >> > if we deal with just that I would be mostly happy, because this >> >> > "false >> >> > click", I guess, appear because some noise is scaled and goes beyond >> >> > a >> >> > threshold. Even in this case I don't see the much, and using tablet >> >> > as >> >> > my >> >> > only mouse on this PC. >> >> > So it is mostly usable as mouse input. Tablet input is unusable for >> >> > me. >> >> > >> >> > On Fri, Jan 14, 2011 at 04:00, AndrewP <[email protected]> wrote: >> >> >> >> >> >> Peter, it might be default, but in Gentoo here, I use my own USE >> >> >> flags >> >> >> to >> >> >> compile everything with different settings. >> >> >> >> >> >> Chris, seems I didn't make it clear, but in this log I tried to show >> >> >> several cases: >> >> >> 1. false clicks >> >> >> a. when I move the tip close but don't touch (there are about 1-2mm >> >> >> left) >> >> >> b. when I tilt the pen very steeply (as I would do with crayon) and >> >> >> get >> >> >> it close >> >> >> 2. usual strokes >> >> >> 3. and similar with eraser >> >> >> a. false when just touch without any actual pressure >> >> >> b. usual stroke >> >> >> >> >> >> >> >> >> Ping,I understand why you implying that hardware has some issues, >> >> >> I've >> >> >> begun to think so myself, because >> >> >> I didn't really tried the tablet in Windows in the beginning. And >> >> >> when >> >> >> I >> >> >> checked it there it was kind of a huge relief, >> >> >> because I got that problem from the first day I've got this Tablet >> >> >> PC, >> >> >> and >> >> >> I'm talking about brand new PC out of the box. >> >> >> I never actually used the tablet here, because I can't work with it >> >> >> considering the issues. >> >> >> I mean I have new pen, and I've already tried changing tips (even >> >> >> from >> >> >> my >> >> >> Intuos pen, to a one with spring in it), so it mustn't be >> >> >> wear or dust. >> >> >> >> >> >> >> >> >> On Fri, Jan 14, 2011 at 02:21, Peter Hutterer >> >> >> <[email protected]> >> >> >> wrote: >> >> >>> >> >> >>> On Thu, Jan 13, 2011 at 07:33:00PM +0000, AndrewP wrote: >> >> >>> > I get this messages when trying >> >> >>> > >> >> >>> > xsetwacom set stylus debuglevel 12 >> >> >>> > Property 'Wacom Debug Levels' does not exist on device. >> >> >>> > >> >> >>> > xsetwacom set stylus commondbg 12 >> >> >>> > Property 'Wacom Debug Levels' does not exist on device. >> >> >>> > >> >> >>> > how come debug isn't available? >> >> >>> >> >> >>> ./configure --enable-debug --<other options you used> >> >> >>> >> >> >>> though this should be default now. also, I recommend to always use >> >> >>> device >> >> >>> names instead of device IDs. the ids may change, names stay the >> >> >>> same >> >> >>> across >> >> >>> reboots. >> >> >>> >> >> >>> Cheers, >> >> >>> Peter >> >> >>> >> >> >>> > On Thu, Jan 13, 2011 at 19:16, Ping Cheng <[email protected]> >> >> >>> > wrote: >> >> >>> > >> >> >>> > > On Mon, Jan 10, 2011 at 1:52 PM, AndrewP <[email protected]> >> >> >>> > > wrote: >> >> >>> > > > Happened to boot to Win7 again, and must notice it is wholly >> >> >>> > > > different >> >> >>> > > > experience there. Any luck with our driver? >> >> >>> > > >> >> >>> > > I found another pen only serial tablet PC (another Toshiba >> >> >>> > > system). I >> >> >>> > > installed Fedora 13 on it. Then I upgraded xf86-input-wacom to >> >> >>> > > the >> >> >>> > > git >> >> >>> > > repo. I still do not see the issue you are seeing. >> >> >>> > > >> >> >>> > > Since we are using different hardwares, I would wish it is a >> >> >>> > > hardware >> >> >>> > > issue if you didn't try it on Windows. >> >> >>> > > >> >> >>> > > Can you turn the debug on ("xsetwacom set stylus debuglevel 12" >> >> >>> > > and >> >> >>> > > "xsetwacom set stylus commondbg 12") and trace the log messages >> >> >>> > > in >> >> >>> > > /var/log/Xorg.0.log to see if there is anything suspecious? >> >> >>> > > >> >> >>> > > I didn't give up. I just have no clue where your problem lies. >> >> >>> > > >> >> >>> > > Ping >> >> >>> > > >> >> >>> >> >> >>> > >> >> >>> > >> >> >>> > >> >> >>> > ------------------------------------------------------------------------------ >> >> >>> > Protect Your Site and Customers from Malware Attacks >> >> >>> > Learn about various malware tactics and how to avoid them. >> >> >>> > Understand >> >> >>> > malware threats, the impact they can have on your business, and >> >> >>> > how >> >> >>> > you >> >> >>> > can protect your company and customers by using code signing. >> >> >>> > http://p.sf.net/sfu/oracle-sfdevnl >> >> >>> >> >> >>> > _______________________________________________ >> >> >>> > Linuxwacom-devel mailing list >> >> >>> > [email protected] >> >> >>> > https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel >> >> >>> >> >> >> >> >> >> >> >> > >> >> > >> > >> > > > ------------------------------------------------------------------------------ Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ Linuxwacom-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
