<?xml version="1.0" encoding="UTF-8"?>
	<rss version="2.0"
		xmlns:content="http://purl.org/rss/1.0/modules/content/"
		xmlns:wfw="http://wellformedweb.org/CommentAPI/"
		xmlns:dc="http://purl.org/dc/elements/1.1/"
		xmlns:atom="http://www.w3.org/2005/Atom"

			>

	<channel>
		<title>Cycling 74  &#187;  Topic: Max 5 UI and Wacom pad</title>
		<atom:link href="http://cycling74.com/forums/topic/max-5-ui-and-wacom-pad/feed" rel="self" type="application/rss+xml" />
		<link>http://cycling74.com/forums/topic/max-5-ui-and-wacom-pad/feed</link>
		<description></description>
		<pubDate>Tue, 18 Jun 2013 21:50:59 +0000</pubDate>
		<generator>http://bbpress.org/?v=2.2.4</generator>
		<language></language>

		
														
					
				<item>
					<guid>http://cycling74.com/forums/topic/max-5-ui-and-wacom-pad/#post-37142</guid>
					<title><![CDATA[Max 5 UI and Wacom pad]]></title>
					<link>http://cycling74.com/forums/topic/max-5-ui-and-wacom-pad/#post-37142</link>
					<pubDate>Wed, 23 Apr 2008 12:45:45 +0000</pubDate>
					<dc:creator>david stevens</dc:creator>

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

					
					
				</item>

			
				<item>
					<guid>http://cycling74.com/forums/topic/max-5-ui-and-wacom-pad/#post-128033</guid>
					<title><![CDATA[Re: Max 5 UI and Wacom pad]]></title>
					<link>http://cycling74.com/forums/topic/max-5-ui-and-wacom-pad/#post-128033</link>
					<pubDate>Wed, 23 Apr 2008 13:28:17 +0000</pubDate>
					<dc:creator>lists@lowfrequency.or</dc:creator>

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

					
					
				</item>

			
				<item>
					<guid>http://cycling74.com/forums/topic/max-5-ui-and-wacom-pad/#post-128034</guid>
					<title><![CDATA[Re: Max 5 UI and Wacom pad]]></title>
					<link>http://cycling74.com/forums/topic/max-5-ui-and-wacom-pad/#post-128034</link>
					<pubDate>Wed, 23 Apr 2008 13:50:02 +0000</pubDate>
					<dc:creator>david stevens</dc:creator>

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

					
					
				</item>

			
				<item>
					<guid>http://cycling74.com/forums/topic/max-5-ui-and-wacom-pad/#post-128035</guid>
					<title><![CDATA[Re: Max 5 UI and Wacom pad]]></title>
					<link>http://cycling74.com/forums/topic/max-5-ui-and-wacom-pad/#post-128035</link>
					<pubDate>Wed, 23 Apr 2008 16:28:21 +0000</pubDate>
					<dc:creator>mzed</dc:creator>

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

					
					
				</item>

			
				<item>
					<guid>http://cycling74.com/forums/topic/max-5-ui-and-wacom-pad/#post-128036</guid>
					<title><![CDATA[Re: Max 5 UI and Wacom pad]]></title>
					<link>http://cycling74.com/forums/topic/max-5-ui-and-wacom-pad/#post-128036</link>
					<pubDate>Wed, 23 Apr 2008 17:42:20 +0000</pubDate>
					<dc:creator>jln</dc:creator>

					<description>
						<![CDATA[
						<p></p>
						]]>
					</description>

					
					
				</item>

			
				<item>
					<guid>http://cycling74.com/forums/topic/max-5-ui-and-wacom-pad/#post-128037</guid>
					<title><![CDATA[Re: Max 5 UI and Wacom pad]]></title>
					<link>http://cycling74.com/forums/topic/max-5-ui-and-wacom-pad/#post-128037</link>
					<pubDate>Wed, 23 Apr 2008 18:21:32 +0000</pubDate>
					<dc:creator>david stevens</dc:creator>

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

					
					
				</item>

			
				<item>
					<guid>http://cycling74.com/forums/topic/max-5-ui-and-wacom-pad/#post-128038</guid>
					<title><![CDATA[Re: Max 5 UI and Wacom pad]]></title>
					<link>http://cycling74.com/forums/topic/max-5-ui-and-wacom-pad/#post-128038</link>
					<pubDate>Wed, 23 Apr 2008 20:37:56 +0000</pubDate>
					<dc:creator>Andrew Benson</dc:creator>

					<description>
						<![CDATA[
						<p>Thanks everyone for your reports.</p>
<p>We are looking into it, and should hopefully have a fix soon.</p>
<p>Best,<br />
Andrew B.<br />
&#8211;<br />
Cycling &#8217;74 Support</p>
						]]>
					</description>

					
					
				</item>

			
				<item>
					<guid>http://cycling74.com/forums/topic/max-5-ui-and-wacom-pad/#post-128039</guid>
					<title><![CDATA[Re: Max 5 UI and Wacom pad]]></title>
					<link>http://cycling74.com/forums/topic/max-5-ui-and-wacom-pad/#post-128039</link>
					<pubDate>Wed, 23 Apr 2008 21:33:32 +0000</pubDate>
					<dc:creator>pelado</dc:creator>

					<description>
						<![CDATA[
						<p>I also have this problem and found that Ableton Live was always like this &#8211; making it just about unusable with the Wacom.  </p>
<p>pelado</p>
						]]>
					</description>

					
					
				</item>

			
				<item>
					<guid>http://cycling74.com/forums/topic/max-5-ui-and-wacom-pad/#post-128040</guid>
					<title><![CDATA[Re: Max 5 UI and Wacom pad]]></title>
					<link>http://cycling74.com/forums/topic/max-5-ui-and-wacom-pad/#post-128040</link>
					<pubDate>Wed, 23 Apr 2008 23:03:06 +0000</pubDate>
					<dc:creator>Joshua Kit Clayton</dc:creator>

					<description>
						<![CDATA[
						<p>
FWIW, thanks for the reports. We&#8217;re working on it.</p>
<p>-Joshua</p>
						]]>
					</description>

					
					
				</item>

			
				<item>
					<guid>http://cycling74.com/forums/topic/max-5-ui-and-wacom-pad/#post-128041</guid>
					<title><![CDATA[Re: Max 5 UI and Wacom pad]]></title>
					<link>http://cycling74.com/forums/topic/max-5-ui-and-wacom-pad/#post-128041</link>
					<pubDate>Wed, 23 Apr 2008 23:47:50 +0000</pubDate>
					<dc:creator>Axiom-Crux</dc:creator>

					<description>
						<![CDATA[
						<p>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</p>
						]]>
					</description>

					
					
				</item>

			
				<item>
					<guid>http://cycling74.com/forums/topic/max-5-ui-and-wacom-pad/#post-128042</guid>
					<title><![CDATA[Re: Max 5 UI and Wacom pad]]></title>
					<link>http://cycling74.com/forums/topic/max-5-ui-and-wacom-pad/#post-128042</link>
					<pubDate>Thu, 24 Apr 2008 00:36:07 +0000</pubDate>
					<dc:creator>MJ</dc:creator>

					<description>
						<![CDATA[
						<p>[OT]<br />
there is an option in prefences menu of cinema4d <br />
where you can select a graphic tablet</p>
<p>check attachment</p>
						]]>
					</description>

					
					
				</item>

			
				<item>
					<guid>http://cycling74.com/forums/topic/max-5-ui-and-wacom-pad/#post-128043</guid>
					<title><![CDATA[Re: Max 5 UI and Wacom pad]]></title>
					<link>http://cycling74.com/forums/topic/max-5-ui-and-wacom-pad/#post-128043</link>
					<pubDate>Thu, 24 Apr 2008 17:31:51 +0000</pubDate>
					<dc:creator>btovsky</dc:creator>

					<description>
						<![CDATA[
						<p>the talk of the ableton/cycling partnership and the wacom problems  <br />
had me worried, as i have been vociferously complaining to ableton  <br />
about their total lack of wacom support for years. they refuse to  <br />
address it, as it is something very tricky in their code base (so  <br />
they say.) do sexy gui&#8217;s mean no tablet?<br />
b</p>
<p>On Apr 23, 2008, at 5:33 PM, pelado wrote:</p>
<p>><br />
> I also have this problem and found that Ableton Live was always  <br />
> like this &#8211; making it just about unusable with the Wacom.<br />
><br />
> pelado<br />
> &#8211;<br />
> <a href="http://www.pelado.co.uk" rel="nofollow">http://www.pelado.co.uk</a></p>
<p>bruce tovsky<br />
<a href="http://www.skeletonhome.com" rel="nofollow">http://www.skeletonhome.com</a></p>
<p>&#8220;Sometimes the appropriate response to reality is to go insane.&#8221;<br />
Philip K. Dick</p>
						]]>
					</description>

					
					
				</item>

			
				<item>
					<guid>http://cycling74.com/forums/topic/max-5-ui-and-wacom-pad/#post-128044</guid>
					<title><![CDATA[Re: Max 5 UI and Wacom pad]]></title>
					<link>http://cycling74.com/forums/topic/max-5-ui-and-wacom-pad/#post-128044</link>
					<pubDate>Thu, 24 Apr 2008 17:49:21 +0000</pubDate>
					<dc:creator>lists@lowfrequency.or</dc:creator>

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

					
					
				</item>

			
				<item>
					<guid>http://cycling74.com/forums/topic/max-5-ui-and-wacom-pad/#post-128045</guid>
					<title><![CDATA[Re: Max 5 UI and Wacom pad]]></title>
					<link>http://cycling74.com/forums/topic/max-5-ui-and-wacom-pad/#post-128045</link>
					<pubDate>Thu, 24 Apr 2008 17:54:07 +0000</pubDate>
					<dc:creator>Andrew Benson</dc:creator>

					<description>
						<![CDATA[
						<p>This should be resolved in the upcoming incremental update.  Thanks to everyone for the reports.</p>
<p>AB</p>
						]]>
					</description>

					
					
				</item>

			
				<item>
					<guid>http://cycling74.com/forums/topic/max-5-ui-and-wacom-pad/#post-128046</guid>
					<title><![CDATA[Re: Max 5 UI and Wacom pad]]></title>
					<link>http://cycling74.com/forums/topic/max-5-ui-and-wacom-pad/#post-128046</link>
					<pubDate>Thu, 24 Apr 2008 18:07:06 +0000</pubDate>
					<dc:creator>Joshua Kit Clayton</dc:creator>

					<description>
						<![CDATA[
						<p>
On Apr 24, 2008, at 10:31 AM, Bruce Tovsky wrote:<br />
> the talk of the ableton/cycling partnership and the wacom problems  <br />
> had me worried, as i have been vociferously complaining to ableton  <br />
> about their total lack of wacom support for years. they refuse to  <br />
> address it, as it is something very tricky in their code base (so  <br />
> they say.) do sexy gui&#8217;s mean no tablet?</p>
<p>Hey there. You Wacom users can relax. We think we&#8217;ve fixed it for the  <br />
next incremental release (Friday or so). Thanks for the reports.</p>
<p>-Joshua</p>
						]]>
					</description>

					
					
				</item>

			
				<item>
					<guid>http://cycling74.com/forums/topic/max-5-ui-and-wacom-pad/#post-128047</guid>
					<title><![CDATA[Re: Max 5 UI and Wacom pad]]></title>
					<link>http://cycling74.com/forums/topic/max-5-ui-and-wacom-pad/#post-128047</link>
					<pubDate>Sun, 27 Apr 2008 10:06:30 +0000</pubDate>
					<dc:creator>dan shuta</dc:creator>

					<description>
						<![CDATA[
						<p>that&#8217;s great news, i was also disappointed with the wacky wacom  <br />
wesponse.  please share the secret of how you&#8217;ve managed to fix the  <br />
issue with ableton, since i also use my tablet nearly 100% of the time  <br />
for an input device.</p>
<p>.d</p>
<p>
On Apr 24, 2008, at 12:54 PM, Andrew Benson wrote:</p>
<p>><br />
> This should be resolved in the upcoming incremental update.  Thanks  <br />
> to everyone for the reports.<br />
><br />
> AB<br />
> &#8211;<br />
> Andrew B.<br />
> &#8211;<br />
> Cycling &#8217;74 Support</p>
						]]>
					</description>

					
					
				</item>

			
				<item>
					<guid>http://cycling74.com/forums/topic/max-5-ui-and-wacom-pad/#post-128048</guid>
					<title><![CDATA[Re: Max 5 UI and Wacom pad]]></title>
					<link>http://cycling74.com/forums/topic/max-5-ui-and-wacom-pad/#post-128048</link>
					<pubDate>Wed, 30 Apr 2008 08:20:33 +0000</pubDate>
					<dc:creator>ardisson</dc:creator>

					<description>
						<![CDATA[
						<p>Thanks for fixing this&#8230;but I&#8217;m still experiencing problems with  parts of the inspector &#8211; eg border size in panel.</p>
						]]>
					</description>

					
					
				</item>

			
				<item>
					<guid>http://cycling74.com/forums/topic/max-5-ui-and-wacom-pad/#post-128049</guid>
					<title><![CDATA[Re: Max 5 UI and Wacom pad]]></title>
					<link>http://cycling74.com/forums/topic/max-5-ui-and-wacom-pad/#post-128049</link>
					<pubDate>Wed, 30 Apr 2008 20:53:05 +0000</pubDate>
					<dc:creator>mzed</dc:creator>

					<description>
						<![CDATA[
						<p>Quote: ardisson wrote on Wed, 30 April 2008 01:20<br />
&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;-<br />
> Thanks for fixing this&#8230;but I&#8217;m still experiencing problems with  parts of the inspector &#8211; eg border size in panel.<br />
> <br />
> <br />
&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;-</p>
<p>me too.</p>
<p>mz</p>
						]]>
					</description>

					
					
				</item>

			
				<item>
					<guid>http://cycling74.com/forums/topic/max-5-ui-and-wacom-pad/#post-128050</guid>
					<title><![CDATA[Re: Max 5 UI and Wacom pad]]></title>
					<link>http://cycling74.com/forums/topic/max-5-ui-and-wacom-pad/#post-128050</link>
					<pubDate>Tue, 20 May 2008 23:21:33 +0000</pubDate>
					<dc:creator>Jackson</dc:creator>

					<description>
						<![CDATA[
						<p>me to Charlse ;)</p>
						]]>
					</description>

					
					
				</item>

			
				<item>
					<guid>http://cycling74.com/forums/topic/max-5-ui-and-wacom-pad/#post-128051</guid>
					<title><![CDATA[Re: Max 5 UI and Wacom pad]]></title>
					<link>http://cycling74.com/forums/topic/max-5-ui-and-wacom-pad/#post-128051</link>
					<pubDate>Wed, 21 May 2008 16:06:34 +0000</pubDate>
					<dc:creator>Axiom-Crux</dc:creator>

					<description>
						<![CDATA[
						<p>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.</p>
						]]>
					</description>

					
					
				</item>

			
				<item>
					<guid>http://cycling74.com/forums/topic/max-5-ui-and-wacom-pad/#post-128052</guid>
					<title><![CDATA[Re: Max 5 UI and Wacom pad]]></title>
					<link>http://cycling74.com/forums/topic/max-5-ui-and-wacom-pad/#post-128052</link>
					<pubDate>Wed, 21 May 2008 16:53:42 +0000</pubDate>
					<dc:creator>David Zicarelli</dc:creator>

					<description>
						<![CDATA[
						<p>> 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.</p>
<p>Just so you know, this is specific to the stupid Mac Wacom driver, which, if it were written properly, wouldn&#8217;t have had the problems it had originally. I&#8217;m pretty sure if you tried the same thing in 4.6 you&#8217;d see the same result. I&#8217;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.</p>
<p>David Z.</p>
						]]>
					</description>

					
					
				</item>

			
				<item>
					<guid>http://cycling74.com/forums/topic/max-5-ui-and-wacom-pad/#post-128053</guid>
					<title><![CDATA[Re: Max 5 UI and Wacom pad]]></title>
					<link>http://cycling74.com/forums/topic/max-5-ui-and-wacom-pad/#post-128053</link>
					<pubDate>Wed, 21 May 2008 17:32:08 +0000</pubDate>
					<dc:creator>wade</dc:creator>

					<description>
						<![CDATA[
						<p>What about having a checkbox in the preferences that would &#8220;switch on&#8221;<br />
Wacom-lameness workarounds. Obviously, this is a gross<br />
over-simplification but more in response to what David said about &#8220;how<br />
to work around Wacom lameness without destroying the experience for<br />
people who use other input devices&#8221; bit.</p>
<p>Maybe the checkbox could be titled &#8220;Wacom driver-lameness workarounds&#8221;.</p>
<p>> I&#8217;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.<br />
><br />
> David Z.</p>
						]]>
					</description>

					
					
				</item>

			
				<item>
					<guid>http://cycling74.com/forums/topic/max-5-ui-and-wacom-pad/#post-128054</guid>
					<title><![CDATA[Re: Max 5 UI and Wacom pad]]></title>
					<link>http://cycling74.com/forums/topic/max-5-ui-and-wacom-pad/#post-128054</link>
					<pubDate>Wed, 21 May 2008 18:23:37 +0000</pubDate>
					<dc:creator>Axiom-Crux</dc:creator>

					<description>
						<![CDATA[
						<p>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)</p>
						]]>
					</description>

					
					
				</item>

					
		
	</channel>
	</rss>

