Pads: preventing accidental presses?

Discuss Lemur and share techniques.
Post Reply
Ozymandias
Newbie
Posts: 18
Joined: 18 Nov 2014 17:47

Pads: preventing accidental presses?

Post by Ozymandias »

Hi all,

I'm using a Pads object with the following OSC output, where the address of each pad is taken from a string array (v):

Code: Select all

//On Expression: x goes from 0 to positive
oscout(0,'/'+v[firstof(x)],1);
Everything works as expected. The trouble is I'm using them to trigger DAW actions, so, if I happen to touch a neighboring pad I can trigger unwanted actions. How can I prevent additional messages being sent whilst one pad is already held?

Thanks for any help. :)
ndivuyo
Regular
Posts: 278
Joined: 23 May 2014 00:24

Re: Pads: preventing accidental presses?

Post by ndivuyo »

so you want to have it that while you are touching one pad, no other pad can send out data correct?
if so, here is a pad lock. I didn't think about too quickly, so maybe there is a better way. You could also show/hide a no touch canvas on the press and release of x, anyway this is a different way using an expression as a gate.
hope this is what you wanted, let me know.
Attachments
padLock.jzlib
(3.87 KiB) Downloaded 38 times
Ozymandias
Newbie
Posts: 18
Joined: 18 Nov 2014 17:47

Re: Pads: preventing accidental presses?

Post by Ozymandias »

That's perfect, ndivuyo - thank you!
Post Reply