Brecht

I'm trying some stuff out with a wacom graphire tablet in Max5, and am running into some bumps;

I use the 'wacom' object, which works fine in 4.6. 5 gives me an 'Wacom driver too old version' error. 

It works regardless, but I need to reinitialise the object fairly often, especially after switching between applications. 

An other strange behavior occurs when in fullscreen, the wacom runs fine, but when I use the keyboard in the meanwhile (to change some settings in the patch), it tends to loose it's connection or something. Going out of fullscreen and back in, solves the problem.

Is any one else experiencing any of this, is there a workaround or perhaps a newer version of the object? I couldn't find anything then what I have on the maxobjects.com site

I'm trying some stuff out with a wacom graphire tablet in Max5, and am running into some bumps; 

I use the 'wacom' object, which works fine in 4.6. 5 gives me an 'Wacom driver too old version' error. 
It works regardless, but I need to reinitialise the object fairly often, especially after switching between applications. 
An other strange behavior occurs when in fullscreen, the wacom runs fine, but when I use the keyboard in the meanwhile (to change some settings in the patch), it tends to loose it's connection or something. Going out of fullscreen and back in, solves the problem. 

Is any one else experiencing any of this, is there a workaround or perhaps a newer version of the object? I couldn't find anything then what I have on the maxobjects.com site


wacom-trouble-max5-fullscreen

i have had similar problems with the wacom object, using newest 

versions of max and leopard, as well as the wacom drivers.

On Aug 7, 2008, at 10:09 PM, Brecht wrote:

> I'm trying some stuff out with a wacom graphire tablet in Max5, and 

> I use the 'wacom' object, which works fine in 4.6. 5 gives me an 

> It works regardless, but I need to reinitialise the object fairly 

> often, especially after switching between applications.

> An other strange behavior occurs when in fullscreen, the wacom runs 

> fine, but when I use the keyboard in the meanwhile (to change some 

> settings in the patch), it tends to loose it's connection or 

> something. Going out of fullscreen and back in, solves the problem.

> Is any one else experiencing any of this, is there a workaround or 

> perhaps a newer version of the object? I couldn't find anything then 

i have had similar problems with the wacom object, using newest  
versions of max and leopard, as well as the wacom drivers.

>
> Hi there,
>
> I'm trying some stuff out with a wacom graphire tablet in Max5, and  
> am running into some bumps;
>
> I use the 'wacom' object, which works fine in 4.6. 5 gives me an  
> 'Wacom driver too old version' error.
> It works regardless, but I need to reinitialise the object fairly  
> often, especially after switching between applications.
> An other strange behavior occurs when in fullscreen, the wacom runs  
> fine, but when I use the keyboard in the meanwhile (to change some  
> settings in the patch), it tends to loose it's connection or  
> something. Going out of fullscreen and back in, solves the problem.
>
> Is any one else experiencing any of this, is there a workaround or  
> perhaps a newer version of the object? I couldn't find anything then  
> what I have on the maxobjects.com site
>
>


On Fri, Aug 8, 2008 at 8:12 AM, joshua goldberg wrote:

> i have had similar problems with the wacom object, using newest versions of

> max and leopard, as well as the wacom drivers.

Yes, I believe the wacom drivers under Leopard are the problem. A few months

back I was working with the wacom sdk and experienced similar problems on

Leopard. I had some email contact with them and this was one of their

Thanks. It seemed to work for a bit, but not completely. It shows the same

> problem I was experiencing earlier with a Wacom plugin under Leopard.

> If you disconnect the tablet from the mouse, and make the window go out of

> focus, when you come back the mouse is moving again and there seems no way

> to change it anymore. Option-1 doesn't work after that.

Unfortunately, that is a known bug. We have a fix, but it isn't released

yet. If your app goes into the background, destroy the context and then

recreate it when you come to the foreground.

This was 27/03/2008, so things might have changed since then. If anyone has

news on this I'd love to hear about it too... mzed?

On Fri, Aug 8, 2008 at 8:12 AM, joshua goldberg  wrote:

> i have had similar problems with the wacom object, using newest versions of
> max and leopard, as well as the wacom drivers.
>
>
Yes, I believe the wacom drivers under Leopard are the problem. A few months
back I was working with the wacom sdk and experienced similar problems on
Leopard. I had some email contact with them and this was one of their
replies:

Thanks. It seemed to work for a bit, but not completely. It shows the same
> problem I was experiencing earlier with a Wacom plugin under Leopard.
> (Max/MSP wacom external):
>
> If you disconnect the tablet from the mouse, and make the window go out of
> focus, when you come back the mouse is moving again and there seems no way
> to change it anymore. Option-1 doesn't work after that.
>

Unfortunately, that is a known bug.  We have a fix, but it isn't released
yet.  If your app goes into the background, destroy the context and then
recreate it when you come to the foreground.

This was 27/03/2008, so things might have changed since then. If anyone has
news on this I'd love to hear about it too... mzed?

Wacom trouble Max5 / fullscreen