Hey guys, having a little problem with trying to restrict the messages from the Wiimote (from the pitch).

Basically, I'm trying to allow the user to go through 8 degrees of a pentatonic scale, so from A up to the D above the octave.

I have the number box from the pitch data coming from the Wii being *100 (just to get some whole numbers), and then being fed to moses 20, for example. Then it will bang out to midi note 57 (A) if it is below 20, and midi note 60 (C) if it's above 20. So that's grand. This continues for moses 30, moses 40, etc. all banging different degrees of the scale gong upwards. This all worked fine when I was getting the sounds inside PD with some simple additive synthesis. I didn't mind that there was a continuous sound at each note.

However, I wanted to route the data out to Reason, just to control some nicer sounding synths and it basically bangs incessantly, hitting the note over and over again. I'm guessing it's taking every slight change in in the pitch of Wii and banging each time. I've tried using the select object to get more specific, the onebang object, but it still seems to be sending the note non-stop.

Sorry for the mouthful there now, but just wondering if any of you have used the Wii with PD a bit and can help out in some way. Thanks

I think the [change] object is what you're looking for. It only outputs the input value if it is different from the last.

[speedlim] could also help on restricting the incoming data flow (and then of course time resolution, but you can find a good tradeoff), to restrict cpu load

Thanks very much guys. I'm messing with it all day. I'll have a look at the [change] object now. I use the [speedlimit] object but never thought of using it to restrict the data flow in that sense.

Thanks again.

I'm not sure what the output values of the wii accelerometer are but if it's anything like the iPhone it'll be from -1 to 1 on all axes.

I've found it's best to have a combination of both [change] (to stop repeated bangs) and a speed limiter to limit the values from fluttering around a change.

I've attached a simple patch that demonstrates this. You might be able to hook the Wii values directly into it. Hope it's helpful.

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

@Jwif said:

I'm not sure what the output values of the wii accelerometer are but if it's anything like the iPhone it'll be from -1 to 1 on all axes.

I've found it's best to have a combination of both [change] (to stop repeated bangs) and a speed limiter to limit the values from fluttering around a change.

I've attached a simple patch that demonstrates this. You might be able to hook the Wii values directly into it. Hope it's helpful.

This must be the most helpful forum I've ever come across. Thanks so much. I'm a bit of a beginner really, having only took one module in PD, but I'm working my way through your patch making sense of each part. Really appreciate the help. It's fairly central to my thesis so thanks again. I'll let you know how I get on anyway.

Rather than using speedlim, which is just going to limit your timing accuracy, I would scale the output of the wiimote to the number of steps you need (ie , then stick on a _object to eliminate everything after the decimal, then the change object.

So it would look something like this:

[wiimote] (assuming 0 to 1 output)
|

• |
  _
  |
  [change]

You could also then use just the decimal values to control something else.

Like so:

[wiimote]
|

• |
  [t f f]
  | |
  _|
  | \ |
  | [- ] <----control value
  |
  [change] <--note value

Also, since the control value above is just another 0 to 1 value, you could make another copy of this little abstraction and feed it that control value to do
harmonies.___

Oops, the inputs on the subtract object are backward in my previous post.
But I'm sure you get the idea.
Just subtract the int value from the float value to get the decimal.

[wiimote]
|

• |
  [t f f]
  | |
  | _
  | / |
  [- ] [change]
  | |_

Yeah, check out the patch I attached. It does exactly that.

Lol, sorry, I was lazy and didn't download the patch.