Toooo sensitive buttons for TouchOSC

mekon

push button on phone(android) is sending to much data, like its to sensitive.

print: /MIXER/push11 1
print: /MIXER/push11 1
print: /MIXER/push11 1
print: /MIXER/push11 0
print: /MIXER/push11 1
print: /MIXER/push11 1
print: /MIXER/push11 0
print: /MIXER/push11 1
print: /MIXER/push11 1
print: /MIXER/push11 0

for toggle button:
print: /MIXER/toggle14 0
print: /MIXER/toggle14 0
print: /MIXER/toggle14 0
print: /MIXER/toggle14 0
print: /MIXER/toggle14 1
print: /MIXER/fader17 1
print: /MIXER/fader17 1
print: /MIXER/fader17 1
print: /MIXER/fader17 1
print: /MIXER/fader17 1
print: /MIXER/fader17 1
print: /MIXER/toggle14 1
print: /MIXER/toggle14 1
print: /MIXER/toggle14 1
print: /MIXER/toggle14 1
print: /MIXER/toggle14 0
print: /MIXER/toggle14 0
print: /MIXER/toggle14 0
print: /MIXER/toggle14 0
print: /MIXER/toggle14 0
print: /MIXER/toggle14 1

CAN IT BE REDUCED? like this:

print: /MIXER/push11 1
print: /MIXER/push11 0
print: /MIXER/push11 1
print: /MIXER/push11 0
print: /MIXER/push11 1
print: /MIXER/push11 0

its problem with play/pause, because PLAY is starting for several time with one push of a button!

mekon

well i have 2days experience with pure data, can you be a little specific where to put change command

* 127
|
ctlout 1 1

mekon

anyone

Maelstorm

Right click an object to see its help file.

It really depends on your patch as to where the best place to put [change] is. Generally, the higher up in the chain you can get away with it is the best place. Based on what you provided:

[change]
|

mekon

patch is little bit messy
but its essential to make it work because its useless with this kind of repeating

routeOSC /push9
|
change
|
* 127
|
ctlout 9 1

??

Ive read help file and experiment with all that stuff but cant make the right one that will work.

Just need for buttons to be state 1 or 0.

http://www.pdpatchrepo.info/hurleur/traktor_4decks_4FX.pd

Maelstorm

I've never actually used TouchOSC, so I can't comment on the sensitivity, but [change] should get rid of repeating values. What's it printing now? I mean, if you just hold the push button, do you get 1's and 0's?

You should organize your patch into subpatchers ([pd mySubpatch] or whatever argument you want to name it). It will make it easier to read and debug. You also might want to make use of [send] and [receive] to keep it from being hidden by patch cords.

Maelstorm

Hmm... if you just want a 1 or 0 state for play/pause, should it be a toggle and not a push button? Again, haven't used TouchOSC, but I believe the idea of a push button is 1 if it's being pressed and 0 when not, whereas a toggle will change each time it is tapped.

mekon

first to thank you for trying to help me.

if I hold push button its like this:
print: /MIXER/push12 1 its receive PLAY
print: /MIXER/push12 1 PLAY
print: /MIXER/push12 1 PLAY
print: /MIXER/push12 1 PLAY
print: /MIXER/push12 1 PLAY
print: /MIXER/push12 1 PLAY
print: /MIXER/push12 0
if I just press it its with less 1s but i need only one 1 to get one PLAY.

if I press JUST ONCE toggle button:
print: /MIXER/toggle12 0
print: /MIXER/toggle12 0
print: /MIXER/toggle12 0
print: /MIXER/toggle12 0
print: /MIXER/toggle12 1
or
print: /MIXER/toggle11 0
print: /MIXER/toggle11 0
print: /MIXER/toggle11 1

so I need to put change to every button, regarding PUSH or TOGGLE.

can you PLEASEEEEE give me example where to put and how to put PATCH CHORDS for CHANGE object. Ive try everything I can think off. DO I NEED ONLY CHANGE OBJECT OR SOME OTHER STUFF(numbers above change) PLEASEEEEEE:

for organizing patch: I found out about pure data on Monday so its little bit early for that , but Ill try, it will be fun to optimize/organize this PD as much as I can.

Maelstorm

Calm down, you don't need to shout. You'll get through this.

All of your posts are showing a different push or toggle being printed in the Pd window, which makes me think you're being a little scattered with your debugging. Just test it with one button, and one button only.

[routeOSC /MIXER]
|
[roueOSC /push9]
|
[change]
|

|
[print] <-- this is where you want to see the change

If you're [print]ing from [unpackOSC], as you are now, you won't see the effect of [change]. You need it after the [change] in order to see that it is filtering and doing what you want.

That should work. And to be clear, you need the [change] object for every value to avoid repeating. So put a [change] after every outlet of [routeOSC] (except the last one, of course) and connect it to

or whatever you're doing.

- - etc.

mekon

oh Thank, I mean thank , youuuuu

everything is working perfect.

Now to reorganize everything.

Thanx again.