Which OS are you using? Can you send me an example of your patch? The joystick object sends both the button id and state for each button press event to avoid any ambiguity (or at least it is supposed to!). So I'm not sure why your patch is getting confused, but it might be that you (like any good Pd user) are assuming that the rightmost outlet fires before the second-to-the-rightmost outlet. The joystick object actually sends the button-id first and then the button-state. So what you want to do is use a "trigger" object and an "int" object to reverse the event ordering. Something like:

[ joystick ] |
| \ | [ t b f ] | / / | / / |/ / /| / / | | [ int ] | | / | / | / [ pack ] | [ route 1 2 3 4 ]

Here, the first four outlets of the "route" object should be the states of the first four buttons.

Hope this helps, Joe jsarlo@ucsd.edu

...

poil wrote:

...

Hi

I am using jsarlo's joystick extension on windows which sends
button-id number and a binary button-state for the whole pad on its
last two outlets respectively. I am currently using it with a pack and
a route to get my button presses into pd, however there are some
problems when multiple buttons are pressed simultaneously or one
button is not released before another is pressed.

So far I have just been careful when performing but when other people
play it they always seem to want to button-mash thus making my patch
do terrible and unexpected things!

-poil-

---

PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-

list