Forums > MaxMSP

Max 5 UI and Wacom pad

April 23, 2008 | 12:45 pm

An issue I’ve just noticed, which affects gain~, slider and dial when
trying to change values using a Wacom pad and pen. (This wasn’t a
problem with Max 4)

The movement of the object doesn’t track pen movement properly. Eg the
slightest movement of the pen when clicked on the gain~ fader is
enough to send it shooting to the other end of its range. You can get
a control to a specific place/value by clicking exactly where you want
it to go, but then the slightest movement of the pen to adjust the
value sends the control zooming off to the end or start of its range.
It works ok using the track pad, but if you saw any of the recent
thread about RSI and alternative input devices, you’ll know that the
trackpad or mouse is not an option for some of us!

All of the other UI objects seem to be fine (miltislider, rslider,
function etc)

Is this fixable?

David

OSX10.5.2 MacBook Pro 2.33 Dual 2Gb


April 23, 2008 | 1:28 pm

Yes, noticed that here too. All UI elements are running on too much
coffee, and are uncontrollable using the wacom but fine with the
standard Mac mouse.

On Apr 23, 2008, at 1:45 PM, David Stevens wrote:
> An issue I’ve just noticed, which affects gain~, slider and dial
> when trying to change values using a Wacom pad and pen. (This
> wasn’t a problem with Max 4)
>
> The movement of the object doesn’t track pen movement properly. Eg
> the slightest movement of the pen when clicked on the gain~ fader
> is enough to send it shooting to the other end of its range. You
> can get a control to a specific place/value by clicking exactly
> where you want it to go, but then the slightest movement of the pen
> to adjust the value sends the control zooming off to the end or
> start of its range. It works ok using the track pad, but if you saw
> any of the recent thread about RSI and alternative input devices,
> you’ll know that the trackpad or mouse is not an option for some of
> us!
>
> All of the other UI objects seem to be fine (miltislider, rslider,
> function etc)
>
> Is this fixable?
>
> David
>
> OSX10.5.2 MacBook Pro 2.33 Dual 2Gb


April 23, 2008 | 1:50 pm

Yup, there’s a problem with number as well.

David

On 23 Apr 2008, at 14:28, evan.raskob [lists] wrote:

> Yes, noticed that here too. All UI elements are running on too much
> coffee, and are uncontrollable using the wacom but fine with the
> standard Mac mouse.
>
>
>
> On Apr 23, 2008, at 1:45 PM, David Stevens wrote:
>> An issue I’ve just noticed, which affects gain~, slider and dial
>> when trying to change values using a Wacom pad and pen. (This
>> wasn’t a problem with Max 4)
>>
>> The movement of the object doesn’t track pen movement properly. Eg
>> the slightest movement of the pen when clicked on the gain~ fader
>> is enough to send it shooting to the other end of its range. You
>> can get a control to a specific place/value by clicking exactly
>> where you want it to go, but then the slightest movement of the pen
>> to adjust the value sends the control zooming off to the end or
>> start of its range. It works ok using the track pad, but if you saw
>> any of the recent thread about RSI and alternative input devices,
>> you’ll know that the trackpad or mouse is not an option for some of
>> us!
>>
>> All of the other UI objects seem to be fine (miltislider, rslider,
>> function etc)
>>
>> Is this fixable?
>>
>> David
>>
>> OSX10.5.2 MacBook Pro 2.33 Dual 2Gb
>


April 23, 2008 | 4:28 pm

I’ve had this problem, too. It might be Wacom’s fault.

Just for the record, I’m running Wacom Driver 4.9.6-3 with OS 10.5.2

Are all of you running Leopard? What Driver version?

mz

Quote: david stevens wrote on Wed, 23 April 2008 06:50
—————————————————-
> Yup, there’s a problem with number as well.
>
> David
>
> On 23 Apr 2008, at 14:28, evan.raskob [lists] wrote:
>
> > Yes, noticed that here too. All UI elements are running on too much
> > coffee, and are uncontrollable using the wacom but fine with the
> > standard Mac mouse.
> >
> >
> >
> > On Apr 23, 2008, at 1:45 PM, David Stevens wrote:
> >> An issue I’ve just noticed, which affects gain~, slider and dial
> >> when trying to change values using a Wacom pad and pen. (This
> >> wasn’t a problem with Max 4)
> >>
> >> The movement of the object doesn’t track pen movement properly. Eg
> >> the slightest movement of the pen when clicked on the gain~ fader
> >> is enough to send it shooting to the other end of its range. You
> >> can get a control to a specific place/value by clicking exactly
> >> where you want it to go, but then the slightest movement of the pen
> >> to adjust the value sends the control zooming off to the end or
> >> start of its range. It works ok using the track pad, but if you saw
> >> any of the recent thread about RSI and alternative input devices,
> >> you’ll know that the trackpad or mouse is not an option for some of
> >> us!
> >>
> >> All of the other UI objects seem to be fine (miltislider, rslider,
> >> function etc)
> >>
> >> Is this fixable?
> >>
> >> David
> >>
> >> OSX10.5.2 MacBook Pro 2.33 Dual 2Gb
> >
>
>
—————————————————-



jln
April 23, 2008 | 5:42 pm


April 23, 2008 | 6:21 pm

OSX 10.5.2 , Wacom driver 6.0.5-3

There’s long been a similar problem in some (but not all) vst plugins
- the Omhforce ones for example. But there’s never been a problem with
Max before, that’s new.

David

On 23 Apr 2008, at 17:28, mzed wrote:

>
>
> I’ve had this problem, too. It might be Wacom’s fault.
>
> Just for the record, I’m running Wacom Driver 4.9.6-3 with OS 10.5.2
>
> Are all of you running Leopard? What Driver version?
>
> mz
>
>
>
>
>
> Quote: david stevens wrote on Wed, 23 April 2008 06:50
> —————————————————-
>> Yup, there’s a problem with number as well.
>>
>> David
>>
>> On 23 Apr 2008, at 14:28, evan.raskob [lists] wrote:
>>
>>> Yes, noticed that here too. All UI elements are running on too much
>>> coffee, and are uncontrollable using the wacom but fine with the
>>> standard Mac mouse.
>>>
>>>
>>>
>>> On Apr 23, 2008, at 1:45 PM, David Stevens wrote:
>>>> An issue I’ve just noticed, which affects gain~, slider and dial
>>>> when trying to change values using a Wacom pad and pen. (This
>>>> wasn’t a problem with Max 4)
>>>>
>>>> The movement of the object doesn’t track pen movement properly. Eg
>>>> the slightest movement of the pen when clicked on the gain~ fader
>>>> is enough to send it shooting to the other end of its range. You
>>>> can get a control to a specific place/value by clicking exactly
>>>> where you want it to go, but then the slightest movement of the pen
>>>> to adjust the value sends the control zooming off to the end or
>>>> start of its range. It works ok using the track pad, but if you saw
>>>> any of the recent thread about RSI and alternative input devices,
>>>> you’ll know that the trackpad or mouse is not an option for some of
>>>> us!
>>>>
>>>> All of the other UI objects seem to be fine (miltislider, rslider,
>>>> function etc)
>>>>
>>>> Is this fixable?
>>>>
>>>> David
>>>>
>>>> OSX10.5.2 MacBook Pro 2.33 Dual 2Gb
>>>
>>
>>
> —————————————————-
>
>
> –
> || michael f. zbyszynski — molecular gastronimist
> || http://www.cnmat.berkeley.edu/
> || http://www.mikezed.com/
>
>
>


April 23, 2008 | 8:37 pm

Thanks everyone for your reports.

We are looking into it, and should hopefully have a fix soon.

Best,
Andrew B.

Cycling ’74 Support


April 23, 2008 | 9:33 pm

I also have this problem and found that Ableton Live was always like this – making it just about unusable with the Wacom.

pelado


April 23, 2008 | 11:03 pm

FWIW, thanks for the reports. We’re working on it.

-Joshua


April 23, 2008 | 11:47 pm

Id like to note that a few other apps have this behavior, especially cinema 4d and fruityloops. Whenever I try to move somethin in cinema it moves faster then a speeding bullet



MJ
April 24, 2008 | 12:36 am

[OT]
there is an option in prefences menu of cinema4d
where you can select a graphic tablet

check attachment


April 24, 2008 | 5:31 pm

the talk of the ableton/cycling partnership and the wacom problems
had me worried, as i have been vociferously complaining to ableton
about their total lack of wacom support for years. they refuse to
address it, as it is something very tricky in their code base (so
they say.) do sexy gui’s mean no tablet?
b

On Apr 23, 2008, at 5:33 PM, pelado wrote:

>
> I also have this problem and found that Ableton Live was always
> like this – making it just about unusable with the Wacom.
>
> pelado
> –
> http://www.pelado.co.uk

bruce tovsky
http://www.skeletonhome.com

"Sometimes the appropriate response to reality is to go insane."
Philip K. Dick


April 24, 2008 | 5:49 pm

OSX 10.4.11, Wacom 6.0.5-3
No issues in Max 4.6.3

On Apr 23, 2008, at 7:21 PM, David Stevens wrote:
> OSX 10.5.2 , Wacom driver 6.0.5-3
>
> There’s long been a similar problem in some (but not all) vst
> plugins – the Omhforce ones for example. But there’s never been a
> problem with Max before, that’s new.
>
> David
>
> On 23 Apr 2008, at 17:28, mzed wrote:
>
>>
>>
>> I’ve had this problem, too. It might be Wacom’s fault.
>>
>> Just for the record, I’m running Wacom Driver 4.9.6-3 with OS 10.5.2
>>
>> Are all of you running Leopard? What Driver version?
>>
>> mz
>>
>>
>>
>>
>>
>> Quote: david stevens wrote on Wed, 23 April 2008 06:50
>> —————————————————-
>>> Yup, there’s a problem with number as well.
>>>
>>> David
>>>
>>> On 23 Apr 2008, at 14:28, evan.raskob [lists] wrote:
>>>
>>>> Yes, noticed that here too. All UI elements are running on too
>>>> much
>>>> coffee, and are uncontrollable using the wacom but fine with the
>>>> standard Mac mouse.
>>>>
>>>>
>>>>
>>>> On Apr 23, 2008, at 1:45 PM, David Stevens wrote:
>>>>> An issue I’ve just noticed, which affects gain~, slider and dial
>>>>> when trying to change values using a Wacom pad and pen. (This
>>>>> wasn’t a problem with Max 4)
>>>>>
>>>>> The movement of the object doesn’t track pen movement properly. Eg
>>>>> the slightest movement of the pen when clicked on the gain~ fader
>>>>> is enough to send it shooting to the other end of its range. You
>>>>> can get a control to a specific place/value by clicking exactly
>>>>> where you want it to go, but then the slightest movement of the
>>>>> pen
>>>>> to adjust the value sends the control zooming off to the end or
>>>>> start of its range. It works ok using the track pad, but if you
>>>>> saw
>>>>> any of the recent thread about RSI and alternative input devices,
>>>>> you’ll know that the trackpad or mouse is not an option for
>>>>> some of
>>>>> us!
>>>>>
>>>>> All of the other UI objects seem to be fine (miltislider, rslider,
>>>>> function etc)
>>>>>
>>>>> Is this fixable?
>>>>>
>>>>> David
>>>>>
>>>>> OSX10.5.2 MacBook Pro 2.33 Dual 2Gb
>>>>
>>>
>>>
>> —————————————————-
>>
>>
>> –
>> || michael f. zbyszynski — molecular gastronimist
>> || http://www.cnmat.berkeley.edu/
>> || http://www.mikezed.com/
>>
>>
>>
>


April 24, 2008 | 5:54 pm

This should be resolved in the upcoming incremental update. Thanks to everyone for the reports.

AB


April 24, 2008 | 6:07 pm

On Apr 24, 2008, at 10:31 AM, Bruce Tovsky wrote:
> the talk of the ableton/cycling partnership and the wacom problems
> had me worried, as i have been vociferously complaining to ableton
> about their total lack of wacom support for years. they refuse to
> address it, as it is something very tricky in their code base (so
> they say.) do sexy gui’s mean no tablet?

Hey there. You Wacom users can relax. We think we’ve fixed it for the
next incremental release (Friday or so). Thanks for the reports.

-Joshua


April 27, 2008 | 10:06 am

that’s great news, i was also disappointed with the wacky wacom
wesponse. please share the secret of how you’ve managed to fix the
issue with ableton, since i also use my tablet nearly 100% of the time
for an input device.

.d

On Apr 24, 2008, at 12:54 PM, Andrew Benson wrote:

>
> This should be resolved in the upcoming incremental update. Thanks
> to everyone for the reports.
>
> AB
> –
> Andrew B.
> –
> Cycling ’74 Support


April 30, 2008 | 8:20 am

Thanks for fixing this…but I’m still experiencing problems with parts of the inspector – eg border size in panel.


April 30, 2008 | 8:53 pm

Quote: ardisson wrote on Wed, 30 April 2008 01:20
—————————————————-
> Thanks for fixing this…but I’m still experiencing problems with parts of the inspector – eg border size in panel.
>
>
—————————————————-

me too.

mz


May 20, 2008 | 11:21 pm

me to Charlse ;)


May 21, 2008 | 4:06 pm

one other small issue I noticed is that when I am controlling a UI object that used to be affected by the wacom error, and I get to the top or bottom of the wacom tablet (IE a dial or number-box placed near the top or bottom of the screen) turn it a tiny bit and as soon as my pen hits the border of the tablet it goes to max or minimum value respectively. This is a bit irritating, is there a way that the values can be capped when one hits the border of the tablet? so rather then going to min or max it just stays where it is.


May 21, 2008 | 4:53 pm

> is there a way that the values can be capped when one hits the border of the tablet? so rather then going to min or max it just stays where it is.

Just so you know, this is specific to the stupid Mac Wacom driver, which, if it were written properly, wouldn’t have had the problems it had originally. I’m pretty sure if you tried the same thing in 4.6 you’d see the same result. I’m pretty much out of ideas about how to work around Wacom lameness without destroying the experience for people who use other input devices with properly written drivers.

David Z.


May 21, 2008 | 5:32 pm

What about having a checkbox in the preferences that would "switch on"
Wacom-lameness workarounds. Obviously, this is a gross
over-simplification but more in response to what David said about "how
to work around Wacom lameness without destroying the experience for
people who use other input devices" bit.

Maybe the checkbox could be titled "Wacom driver-lameness workarounds".

> I’m pretty much out of ideas about how to work around Wacom lameness without destroying the experience for people who use other input devices with properly written drivers.
>
> David Z.


May 21, 2008 | 6:23 pm

when I use the mouse I notice that it holds the mouse location in place when turning the dial or number box. Is this not able to be implemented in wacom? My apologies if these wacom problems are irritating, I feel the same way. Its just that with a wacom or tablet screen, I can accomplish direct control over my patches in a somewhat lemur like manner, which provides much faster interaction during jams and live performances. Alternatively, is it possible to interface with the people at wacom and ask for a driver update for compatibility. I know alot of other softwares would benefit as well (hopefully ableton as others suggested)


Viewing 23 posts - 1 through 23 (of 23 total)