Stefan

I know theres been another topic on this but it didnt quite answer my question.

Im trying to hook up my Kaoss pad so that the xy pad controls the xy position of the pictslider object so if i touch the top right hand corner of my kaoss pad the pictslider jumps to the top right hand corner - i want to do this so i understand the principle of how the midi data from my Kaoss pad is handled by Max.

I can get the pad to control the position from bottom left to top right but nothing else. How do i get full xy control?

Also, when i let go of the pad the pictslider resets itself (ie back to the bottom left). Is there anyway to "hold" the last midi data so that the pictslider stays in the same place when i let go of the kaoss pad?

Hope someone can help me - would be really useful to use this in a uni project im working on. Would get major kudos if i can get it working!

I know theres been another topic on this but it didnt quite answer my question. 

Im trying to hook up my Kaoss pad so that the xy pad controls the xy position of the pictslider object so if i touch the top right hand corner of my kaoss pad the pictslider jumps to the top right hand corner - i want to do this so i understand the principle of how the midi data from my Kaoss pad is handled by Max. 

kaoss-pad-as-pictslider-controller

send along your patch, otherwise we can only speculate.

On Oct 29, 2007, at 4:44 PM, Stefan Scheuregger wrote:

> I know theres been another topic on this but it didnt quite answer 

> Im trying to hook up my Kaoss pad so that the xy pad controls the 

> xy position of the pictslider object so if i touch the top right 

> hand corner of my kaoss pad the pictslider jumps to the top right 

> hand corner - i want to do this so i understand the principle of 

> how the midi data from my Kaoss pad is handled by Max.

> I can get the pad to control the position from bottom left to top 

> right but nothing else. How do i get full xy control?

> Also, when i let go of the pad the pictslider resets itself (ie 

> back to the bottom left). Is there anyway to "hold" the last midi 

> data so that the pictslider stays in the same place when i let go 

> Hope someone can help me - would be really useful to use this in a 

> uni project im working on. Would get major kudos if i can get it 

>
> I know theres been another topic on this but it didnt quite answer  
> my question.
>
> Im trying to hook up my Kaoss pad so that the xy pad controls the  
> xy position of the pictslider object so if i touch the top right  
> hand corner of my kaoss pad the pictslider jumps to the top right  
> hand corner - i want to do this so i understand the principle of  
> how the midi data from my Kaoss pad is handled by Max.
>
> I can get the pad to control the position from bottom left to top  
> right but nothing else. How do i get full xy control?
>
> Also, when i let go of the pad the pictslider resets itself (ie  
> back to the bottom left). Is there anyway to "hold" the last midi  
> data so that the pictslider stays in the same place when i let go  
> of the kaoss pad?
>
> Hope someone can help me - would be really useful to use this in a  
> uni project im working on. Would get major kudos if i can get it  
> working!
>
> Many thanks
>
> Stefan
>
>

well there's not really much of a patch as such. I just wanted to get the pictslider copying my movements on the kaoss pad - it's really just so i understand how MIDI data from my kaoss pad is handled.

Trouble is when i move my finger on the kaoss pad the pictslider does move but very erratically. If i have my finger in one corner i get a control value of 0 and the slightest of movements sends that value up to 127. Also, the controller numbers jump all over the place when i move my finger. Flickering between 1, 2, 13 and 93 by the looks of things!

Sorry if this is a silly topic to post but im a real newbie and it'd be useful for me to understand how and why the MIDI data is sent to different objects. It started out as me just messing about but now its a bit of an obsession and i wanna know how to get it working!

>well there's not really much of a patch as such. I just wanted to 

>get the pictslider copying my movements on the kaoss pad - it's 

>really just so i understand how MIDI data from my kaoss pad is 

>Trouble is when i move my finger on the kaoss pad the pictslider 

>does move but very erratically. If i have my finger in one corner i 

>get a control value of 0 and the slightest of movements sends that 

>value up to 127. Also, the controller numbers jump all over the 

>place when i move my finger. Flickering between 1, 2, 13 and 93 by 

>Sorry if this is a silly topic to post but im a real newbie and it'd 

>be useful for me to understand how and why the MIDI data is sent to 

>different objects. It started out as me just messing about but now 

>its a bit of an obsession and i wanna know how to get it working!

actually i have used the kaoss quite a lot (versions 1 and version 2, 

now tey are at version 4 so it might be different)

your problem could be that you don't use the right CC numbers - 

contrary to what one might think the kaoss does not output only 2 CC 

(the x and y) but much more - some of them only covering a portion 

try detecting all the CC's the kaoss is outputting, and select 

between those the ones which are x and y - it should work

in the kaoss itself you can also change the cc numbers (and the midi channels)

then you have on the kaoss the setting if, when you stop touching it, 

it stays at the last received value or goes back to 0 (this is also 

>well there's not really much of a patch as such. I just wanted to 
>get the pictslider copying my movements on the kaoss pad - it's 
>really just so i understand how MIDI data from my kaoss pad is 
>handled.
>
>Trouble is when i move my finger on the kaoss pad the pictslider 
>does move but very erratically. If i have my finger in one corner i 
>get a control value of 0 and the slightest of movements sends that 
>value up to 127. Also, the controller numbers jump all over the 
>place when i move my finger. Flickering between 1, 2, 13 and 93 by 
>the looks of things!
>
>Sorry if this is a silly topic to post but im a real newbie and it'd 
>be useful for me to understand how and why the MIDI data is sent to 
>different objects. It started out as me just messing about but now 
>its a bit of an obsession and i wanna know how to get it working!
>

actually i have used the kaoss quite a lot (versions 1 and version 2, 
now tey are at version 4 so it might be different)

your problem could be that you don't use the right CC numbers - 
contrary to what one might think the kaoss does not output only 2 CC 
(the x and y) but much more  - some of them only covering a portion 
of the pad itself

try detecting all the  CC's the kaoss is outputting, and select 
between those the ones which are x and y - it should work

then you have on the kaoss the setting if, when you stop touching it, 
it stays at the last received value or goes back to 0 (this is also 
not too difficult to set up in max)

kasper
-- 
  Kasper T. Toeplitz
noise, composition, bass, computer
http://www.sleazeArt.com

haven't used this in a bit, but i assume it's still correct:

Quote: robtherich wrote on Tue, 30 October 2007 19:12

----------------------------------------------------

> haven't used this in a bit, but i assume it's still correct:

> #P comment 173 81 84 196617 Touchpad On/Off;

> #P number 173 132 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;

> #P number 477 132 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;

> #P number 78 134 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;

> #P number 283 132 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;

> #P number 30 132 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;

> #P number 375 132 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;

> #P comment 77 80 91 196617 FX Depth (volume);

> #P message 30 61 141 196617 port "YOUR MIDI PORT HERE";

Sorry for being stupid but i dont understand your post? What is this all referring to?

Really appreciate all the replies to my queston.

Quote: robtherich wrote on Tue, 30 October 2007 19:12
----------------------------------------------------
> haven't used this in a bit, but i assume it's still correct:
>
> #P inlet 30 35 15 0;
> #P window setfont "Sans Serif" 9.;
> #P window linecount 1;
> #P comment 173 81 84 196617 Touchpad On/Off;
> #P number 173 132 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
> #P newex 173 110 53 196617 ctlin 92 1;
> #P number 477 132 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
> #P newex 477 110 53 196617 ctlin 13 1;
> #P comment 477 81 39 196617 Y-axis;
> #P comment 283 81 31 196617 Mute;
> #P number 78 134 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
> #P newex 78 110 53 196617 ctlin 94 1;
> #P number 283 132 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
> #P newex 283 110 53 196617 ctlin 95 1;
> #P number 30 132 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
> #P newex 30 110 44 196617 pgmin 1;
> #P number 375 132 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
> #P newex 375 110 53 196617 ctlin 12 1;
> #P comment 77 80 91 196617 FX Depth (volume);
> #P comment 375 81 39 196617 X-axis;
> #P message 30 61 141 196617 port "YOUR MIDI PORT HERE";
> #P fasten 0 0 5 0 35 84 35 84;
> #P fasten 0 0 9 0 35 97 83 97;
> #P fasten 0 0 15 0 35 97 178 97;
> #P fasten 0 0 7 0 35 97 288 97;
> #P fasten 0 0 3 0 35 97 380 97;
> #P fasten 0 0 13 0 35 97 482 97;
> #P connect 18 0 0 0;
> #P connect 13 0 14 0;
> #P connect 3 0 4 0;
> #P connect 7 0 8 0;
> #P connect 15 0 16 0;
> #P connect 9 0 10 0;
> #P connect 5 0 6 0;
> #P window clipboard copycount 19;
>
----------------------------------------------------

Sorry for being stupid but i dont understand your post? What is this all referring to? 

pardon the assumption that you're not familiar with using patches 

from the list: copy the text with all the "#P" and in max you'll find 

"new from clipboard" in the file menu. voila.

On Oct 31, 2007, at 3:26 PM, Stefan Scheuregger wrote:

> Quote: robtherich wrote on Tue, 30 October 2007 19:12

> ----------------------------------------------------

>> haven't used this in a bit, but i assume it's still correct:

>> #P comment 173 81 84 196617 Touchpad On/Off;

>> #P number 173 132 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;

>> #P newex 173 110 53 196617 ctlin 92 1;

>> #P number 477 132 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;

>> #P newex 477 110 53 196617 ctlin 13 1;

>> #P number 78 134 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;

>> #P number 283 132 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;

>> #P newex 283 110 53 196617 ctlin 95 1;

>> #P number 30 132 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;

>> #P number 375 132 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;

>> #P newex 375 110 53 196617 ctlin 12 1;

>> #P comment 77 80 91 196617 FX Depth (volume);

>> #P message 30 61 141 196617 port "YOUR MIDI PORT HERE";

> Sorry for being stupid but i dont understand your post? What is 

> Really appreciate all the replies to my queston.

"Reality is whatever refuses to go away when I stop believing in it.."

pardon the assumption that you're not familiar with using patches  
from the list: copy the text with all the "#P" and in max you'll find  
"new from clipboard" in the file menu. voila.
cheers
bruce

>
> Quote: robtherich wrote on Tue, 30 October 2007 19:12
> ----------------------------------------------------
>> haven't used this in a bit, but i assume it's still correct:
>>
>> #P inlet 30 35 15 0;
>> #P window setfont "Sans Serif" 9.;
>> #P window linecount 1;
>> #P comment 173 81 84 196617 Touchpad On/Off;
>> #P number 173 132 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
>> #P newex 173 110 53 196617 ctlin 92 1;
>> #P number 477 132 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
>> #P newex 477 110 53 196617 ctlin 13 1;
>> #P comment 477 81 39 196617 Y-axis;
>> #P comment 283 81 31 196617 Mute;
>> #P number 78 134 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
>> #P newex 78 110 53 196617 ctlin 94 1;
>> #P number 283 132 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
>> #P newex 283 110 53 196617 ctlin 95 1;
>> #P number 30 132 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
>> #P newex 30 110 44 196617 pgmin 1;
>> #P number 375 132 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
>> #P newex 375 110 53 196617 ctlin 12 1;
>> #P comment 77 80 91 196617 FX Depth (volume);
>> #P comment 375 81 39 196617 X-axis;
>> #P message 30 61 141 196617 port "YOUR MIDI PORT HERE";
>> #P fasten 0 0 5 0 35 84 35 84;
>> #P fasten 0 0 9 0 35 97 83 97;
>> #P fasten 0 0 15 0 35 97 178 97;
>> #P fasten 0 0 7 0 35 97 288 97;
>> #P fasten 0 0 3 0 35 97 380 97;
>> #P fasten 0 0 13 0 35 97 482 97;
>> #P connect 18 0 0 0;
>> #P connect 13 0 14 0;
>> #P connect 3 0 4 0;
>> #P connect 7 0 8 0;
>> #P connect 15 0 16 0;
>> #P connect 9 0 10 0;
>> #P connect 5 0 6 0;
>> #P window clipboard copycount 19;
>>
> ----------------------------------------------------
>
> Sorry for being stupid but i dont understand your post? What is  
> this all referring to?
>
> Really appreciate all the replies to my queston.
>
> Many thanks
>
> Stefan

"Reality is whatever refuses to go away when I stop believing in it.."
Philip K. Dick


Kaoss pad as pictslider controller