Wacom Tablets in Max6 on OSX
Is there any way to get data out of a Wacom tablet (intuos4 large) with max6 on Mac? i have tried the wacom external, but as far as I can tell it is either not compatible with max6 or OSX 10.6. has anyone had success with the wacom object in 6?maybe the hi object?
I think this one works:
http://metason.cnrs-mrs.fr/Resultats/MaxMSP/s2m.wacomtouch.zip
No Luck, unfortunately when I try to open the help or trigger a menu for the object it crashes max
I got it figured out, there is an object that puts out the tablet data:
http://metason.cnrs-mrs.fr/Resultats/MaxMSP/s2m.wacom.zip
and one that outputs touch data for the newer tablets with multitouch:
http://metason.cnrs-mrs.fr/Resultats/MaxMSP/s2m.wacomtouch.zip
the second only works if you have a touch tablet on your system, and both only work for max6 on OSX 10.6 and ^
turns out I needed the first object for my tablet but users with newer tablets will want both
Here you find the app IoR that I made with max5 that allows you to read wacom (and other) data and send it to any app as osc data. It's not an answer to your initial question, but maybe it helps.
turns out I needed the first object for my tablet but users with newer tablets will want both
[s2m.wacom] should work with newer tablets. but if you use it with a pen.
the purpose of [s2m.wacomtouch] is to output fingers data. so you'll need both objects only if you want to support both 'pen' and 'fingers' data.
Hi All,
Just spent some time playing with [s2m.wacomtouch], and wrote a small proof-of-concept JS that is similar to [poly] in function, so as to be able to target specific voices of a [poly~] regardless of the increasing Finger IDs that [s2m.wacomtouch] generates.
If you're interested I've attached some demo files here... Would be easy to extend to all data that [s2m.wacomtouch] provides. Should perhaps make an MXJ... No voice stealing (simply ignores more than maxVoices variable in script), but would be easy to build in.
Cheers,
Jules
hi,
Here attached is a small abstraction to renumber the Fingers IDs, so that there are not anymore "ever-increasing", but kept as low as possible.
It is the same abstraction as the one that jm pelletier did for [cv.jit.touches] (cf http://jmpelletier.com/using-cv-jit-touches-recycling-index-values/ ), I just adapted it to [s2m.wacomtouch].
To use it, just input it the fingers data (i.e, connect the left outlet of s2m.wacomtouch to it), and you'll have the same data out of it, but with renumbered fingers IDs.
BTW, s2m.wacomtouch has been updated a few days ago (see http://metason.cnrs-mrs.fr/Resultats/MaxMSP/index.html ), and a windows version of it is now available.
note that the 2nd outlet does not output a bang anymore, but a list. So you may have to add a [t b] in your previous patches. hope it won't be to much troubles for you.
Hmm I am looking for a windows version of the original Wacom object, but having trouble. I had it before but in reinstalling lost it and cannot remember where I found it! Does anyone know where I can find it online? I found a patcher from CNMAT (UCal Berkeley) that uses the wacom object to make use of its data, but it did not include the actual object anywhere I looked.
Any help? Or maybe I can build a translator myself? I have no idea how, but I'm pretty good at teaching myself such things, might be a useful skill to have.
We never had a windows version at CNMAT. I'd suggest using the s2m.wacom objects above.
there's a link to an old wacom object for windows in the last post of that thread :
there's indeed a windows version of s2m.wacom, but it might not be what you're looking for (it only works with touch tablets, and won't give you the pen data).
Hello S2M, i'm trying to use the s2m.wacom object inside a m4l device with an old (3 years?) bamboo touch. it works fine in max, but when i switch on the nopointer flag in m4l i get crazy lag and the data becomes unusable. any idea what's going on?
oh, and is there a way to get the state of the 4 side buttons from s2m.wacom? thanks! r
great abstraction, thanks!
Hi S2M,
I would like to have data from two points from my touchscreen simultaneously. When I use s2m.wacomtouch with double touch it shows data from one point only at the time. Can you tell me how to use it to have simultaneous double touch data?
hum.. are you using the s2m.wacomtouch.maxhelp patch? you should definitely see all your fingers at the same time.
What is your tablet model, your os and wacom driver version?
thanks for fast reply :) yes, I'm using s2m.wacomtouch.maxhelp patch. My tablet is wacom cintiq 22HD, OS is 10.9.2, and drivers of wacom 6.3.6-4. I believe that when I touch I should see circles on the lcd, right? Now it only changes colors of whole lcd in some random way. Maybe'm doing some stupid mistake. Also there are outlets only for one x and y at the same time. Can I have coordinates of both fingers?
ok.
That's surely not the main issue, but in the [p drawLCD] subpatch, you can already change the two [* 0.625] by [* 0.5625] (that's ratio for your tablet), so that the display will be better.
Note that in the help patch the fingers will be drawn correctly only in 'logical' mode (see 'xyrange' attribute). Are you in that mode ? otherwise you have to change the drawLCD subpatch, as it is only doing a quick scaling from 0-1 to the [lcd] size.
In the help patch there is a number box commented 'fingerCount'. Do you see the correct number of fingers in there?
If you are in logical mode and still don't see well all the fingers, then there's something
else that is wrong.
What are the x-y coordinates of your finger along the tablet when you are in 'logical'?
Are they spanning the full 0-1 range along the x and y axis? how much are the 'width' and 'height' values approximately?
another thing : are you're using the tablet as a second screen?
if so try to set it up in 'clone' mode and see if it works.
> Also there are outlets only for one x and y at the same time. Can I have coordinates of both fingers?
the left outlet outputs the data for each finger successively. It's a list starting with the fingerIndex.
So if you want to see all the coordinates at the same time you could route that list to different number boxes depending on the fingerId (with [routepass] for instance)
I'm in the logical mode, but it shows coordinates x:0-1280 and y:0-800, so the resolution of my screen. Number of fingers is ok if we start from 0. I also cloned my screen. Still don't see fingers, but thanks to your advice I see coordinates of both fingers placed at the same time. For now this is enough for me, but It would be nice to figure out, how to make fingers visible.
sounds like there's a real bug then.
Can you please send the message "getinfo" to [s2m.wacomtouch] and send me what's printed in the max window?
It says:
infos: version 3
infos: deviceID 0
infos: type 1
infos: logicalOriginX 0.
infos: logicalOriginY 0.
infos: logicalWidth 1280.
infos: logicalHeight 800.
infos: physicalSizeX 475.200012
infos: physicalSizeY 267.299988
infos: reportedSizeX 4752
infos: reportedSizeY 2673
infos: scanSizeX 122
infos: scanSizeY 70
infos: fingerMax 10
infos: blobMax 10
infos: blobPointsMax 500
infos: capabilityFlags 0
In a meantime...I extremely appreciate your help!
thanks! I found the bug, I'll try to release a new version that fixes it asap.
charles
pd : just for information, this bug is only present on screen tablets.
Wow. It would be awesome:) thanks again!
ok, I had a look and thought about it.
In fact what is mainly wrong and that I will change is just the documentation in the help patch which says that in "logical mode" the "coordinates will be between 0 and 1."
but I will not make any change to the "logical" coordinates :
- It's in fact the expected behaviour : Wacom defines the logical coordinates to be 0. to 1. for opaque devices, and in pixels for 'integrated devices'.
and way more importantly :
- It could break existing patches
So that's up to the user to scale the coordinates as he wants. you got all the infos you need out of the 3rd inlet for that.
However I'll make a new help patch with the info updated and which displays the fingers correctly, and I will fix the "physical" coordinates.
maculka, can you give me your mail address?
or send me a mail through the bug-report link at the bottom of this page :
http://metason.cnrs-mrs.fr/Resultats/MaxMSP/index.html
thanks
haven't heard from you maculka, so not sure you're following that thread, but just in case, FYI, there's an update here :
let me know if you've got any issue with it!
(to all : please read readme.txt before reporting bugs)