Page 1 of 1
Kaoss Pad 2 template
Posted: 31 Aug 2014 11:51
by ivobol
I am working on a template trying to imitate exactly the Kaoss Pad 2. I need to control 6 midi CC (not just X Y Z but also X for bottom half, for top half, and just a CC that sends out a value of 127 whenever you touch the surface) with 1 finger, I cannot figure out how to do it. Any suggestions are highly appreciated!
cheers,
Re: Kaoss Pad 2 template
Posted: 05 Sep 2014 14:29
by Softcore
What object? multiball? Can you also provide the specific CCs that you want used?
Re: Kaoss Pad 2 template
Posted: 05 Sep 2014 14:56
by Joe Soap
I think you'd robably need to use a custom-scripted Canvas object to achieve this degree of articulation actually - failing that it'll take some clever work building a 'compound-object' (module built from several Lemur Objects + scripting).
Re: Kaoss Pad 2 template
Posted: 05 Sep 2014 16:41
by Traxus
^^
maybe a pad or switch array, off color of black? what is the grid size of the kaoss pad?
Re: Kaoss Pad 2 template
Posted: 06 Sep 2014 15:56
by Joe Soap
No idea, is it even grid-based?
Re-reading the OP I'm having a hard time visualising the requirements, doing the maths . . . the description doesn't seem to add up to six CCs?
Is the template multi or single-touch?
Why are we here? What does it all mean???
Re: Kaoss Pad 2 template
Posted: 06 Sep 2014 21:01
by Traxus
Not sure but this dosen't look incredibly complicated; maybe even just a multiball...
https://www.youtube.com/watch?v=7Z73lfm9p6c
I got excited and was confusing it with the Kaossilator, which also seems do able but a bit more complicated (the grid is 8x8)
https://www.youtube.com/watch?v=wAXAJiYLoZg
Re: Kaoss Pad 2 template
Posted: 06 Sep 2014 23:04
by Joe Soap
No, it doesn't look complicated at all - but the description in the OP seems to be. Also . . . possibly a little confused about the 'z' var?
ie: x, y, z . . . three variables. But also 'x for the bottom half, and again for the top half' - so separate 'x' vars, split across zones . . . but no corresponding 'y' var split across the same zones? Again we have 'just a CC that sends out a value of 127 whenever you touch the surface) with 1 finger' . . . which would obviously(?) be assigned to the 'z' . . . but as per the OP the 'z' is already in use?
I just can't quite grok the reqs, and am wondering if it's just me being dense, or if the OP hasn't quite described the reqs adequately.
Re: Kaoss Pad 2 template
Posted: 09 Sep 2014 17:49
by Traxus
Yeah a little dense. After a re read, and assuming this is a multiball:
just a CC that sends out a value of 127 whenever you touch the surface
Use a script that fires on expression z:
Code: Select all
if (z==1) {
//-----midi out on cc for 127
} else {
//-----midi out on cc for 0
}
but also X for bottom half, for top half
on expression {x,y} something like
Code: Select all
decl v = 0;
//-----bottom half
if (y <= 0.5) {
v = range(x,0,127)
//-----v is your midi out value for the other cc for the bottom half of x
}
for top half
again on {x,y}
Code: Select all
decl v = 0;
//-----top half
decl v = 0;
if (y > 0.5) {
v = range(x,0,127)
//-----v is your midi out value for whichever cc for the top half of x
}
but no corresponding 'y' var split across the same zones
so, lets setup another on execution script, this time for y:
Code: Select all
decl v = 0;
v = range(y, 0, 127);
//-----v is the midi out value for your cc for y
best I can do without further clarification
Re: Kaoss Pad 2 template
Posted: 09 Sep 2014 18:30
by Joe Soap
Well, quite - the problem as I see it is my point-by-point breakdown of the OP probably doesn't actually match the actual requirements to emulate the KP2 . . . if you get what I mean.
As noted, further clarification needed, preferably from someone who has (used) a KP2 - because as you ably demonstrated, it's not technical difficulty that's the barrier here, just relating the functionality of the Korg hardware to Lemur capabilities.
The OP seems pretty reluctant to join the conversation though.
Re: Kaoss Pad 2 template
Posted: 09 Sep 2014 19:16
by Traxus
yeah i dont see where they have the dual x parameters either... and seems like you'd want to split it into quadrants if you were going to split it?