Hey everyone,

I am having some technical difficulties getting my patch to work the way I want it to. Maybe somebody can help me out. I would truly appreciate it.

Essentially, I am using OSCulator to send OSC messages from my Wii remote into PD. I have built a patch that receives the accelerometer information and forwards it to a subpatch. Essentially, I coded this so that playback begins when the accelerometer reaches equal to or great than 0.7.

However, when I flick my wrist with the remote to get a value equal to or greater than 0.7, I keep receiving nonstop bangs. I want to code this in a way so that every time I bang once, I can't bang again for a specific amount of time. For example, only one bang is allowed to be receive every 3 seconds. This way, I won't be receiving tons of continuous data. After all, when I flick my wrist, it bangs for every value between 0.7 and everything up. Ideas?

Here is a picture of my patch so far:

I have heard that it might be useful to use either the [change] object or the [speedlim] object. Being new to PD, I am still trying to figure certain components. Help would be massively appreciated about how to actually do this. I may be overcomplicating it.

Thank you everyone!

@lunacyfringe

tglhelp.pd

@lunacyfringe said:

This is a similar problem with MIDI that I haven't figured out yet. If you want to use a note on a controller as a start and stop, you get both a 1 and a 0. Any ideas?

Check out [stripnote], which strips off noteoff messages from incoming midi data. You can then implement the same math that I used above to achieve a "midi toggle"

@rjp9 Thanks for your help!

The patch you provided is really helpul. However, it doesn't actually seem to work with the Wii remote. I sent in a message for the bang (at the top) to receive, but the issue is still the same. The bottom toggle still acts the same way as before.

Your patch seems to work if you use a mouse to click on that bang. However, when I use the Wii remote and press the A button, the bottom-most toggle activates, and when I release it, it deactivates.

@lunacyfringe use everything from [select 1] down. The other stuff was just for testing

@rjp9 Oh! My bad! It works! I thought I might have overlooked something. Thanks again!

@lunacyfringe Cool. Let me know if I can explain anything better. I am a math and computer noob and it took me a while to figure out what the heck "modulo" even meant

@rjp9 Thanks again! I'll be sure to let you know.

@lunacyfringe If you are having trouble with a patch that just refuses to do what you have designed it to do then the best tools are [print] and especially [rawprint] and very especially the "magic glass" that you will find under the "edit" menu at the top of your window.
"magic glass" allows you to see what is passing through the connection cords, and the print objects can "print" the output of an object (when connected to it)........to the terminal window.
If you have a live input to your patch then these tools are all you need, but if not then you will have to feed your patch with a "test" input using (probably) a [metro] to bang in "bangs" or "symbols" or "lists" etc.
When you have time you should read this........... (or even if you don't have time because....... it will save you a lot of time in the long run!)..........http://puredata.info/docs/manuals/pd/x2.htm
David.

@whale-av Thanks for the great info! I'll be sure to look into it.