Hey there! The friendly guy at sojamo.de provided us with a version of the darwiinremote for processing.

Unfortunately, I can't even get the examples to work, maybe just because of not knowing which address and which port to choose...

************************************
import processing.opengl.*;

import oscP5.*;
import netP5.*;

WiiController wiiController;

void setup() {
 size(400,400,OPENGL);
 frameRate(25);
 noStroke();
 smooth();
 wiiController = new WiiController();
}

void mousePressed() {
 // check the battery level of the wii controller
 wiiController.oscP5.send("/wii/batterylevel",new Object[] {},"192.168.1.34",5601);
 // turn force feedback of the wii controller off
 wiiController.oscP5.send("/wii/forcefeedback",new Object[] {new Integer(0)},"192.168.1.34",5601);
}

void keyPressed() {
 // turn forc feedback of the wii controller on
 wiiController.oscP5.send("/wii/forcefeedback",new Object[] {new Integer(1)},"192.168.1.34",5601);
}


void draw() {
 background(0);
 if(wiiController.buttonB) {fill(255); } else {fill(255,0,0);}
 pushMatrix();
   translate(100,100,0);
   rotateY(wiiController.roll/40.0);
   rotateX(wiiController.pitch/40.0);
   rect(0,0,100,100);
 popMatrix();
 rect(wiiController.x/4.0,wiiController.y/4.0,40,40);
}
******************************************************

So, how can I find out which settings to use instead of ""192.168.1.34",5601"?

Thanks a lot!

Is there a PC Version of DarwiinRemote, too? Could only find the OSX files...

And: Can the port be skipped when running it local only, or does it have to stay 5601?

I found one strange version that works with MIDI on this site

http://www.byteofinnovation.net/index.php?2007/10/27/17-wiimote-runs-in-processing

I have impression that is a little bit slower over MIDI but it works very fine.

hi,
messages passed to a plugged method dont need to be in an PApplet extended class, works for any class.
the message you get may be the result of some errors that occurred within the plugged function itself, in your case buttonEvent.
if you comment out everything in this function and just put in
Code:

println("got a button Event");
 

here, you shouldn't be getting the error anymore, and the oddities may be in the code that is commented.
hope this helps.

on another note, i guess you are working on the gesture lib. since there is another wiimote library for processing, i would like to suggest that you may consider to implement an interface to access the wii parameters from that library as well?

best,
andi

yep, wrj5P5 i was referring to. with the interface i was mentioning earlier i meant, maybe it would be good if one could forward his own input values e.g.

Code:

    theWiimoteGestureAnalyzer.setInputX(theX);

    theWiimoteGestureAnalyzer.setInputY(theY);

 

then, whenever you receive an input e.g. from darwiinosc you call these methods. just a rough thought.

advantage:
this way any input(-device) could be analyzed
the lib doesnt have to depend on oscP5 in this case

downside:
in case of darwiinosc you would need to do the osc parsing in each sketch individually since it wouldnt be handled by the gesture lib.

anyhow, looking forward to the lib.
update on darwiinosc: i added nunchuk and IR sensor support in the latest version.

best,
andi

Hey Andi,

Thanks for the advice, I actually already have a more general "GestureAnalyzer" which just accepts Points as input. The WiimoteGestureAnalyzer is just an out-of-the-box child class that automatically plugs into the osc messages from darwiinosc. About dependence on oscP5, it's not really a big concern to me, it's a pretty popular library

And here's the link to the gesture lib.

Cheers,

if you download darwiinosc from code.google/darwiinosc, a processing example using the WiiController class is provided in the p5/wiiControllerExample folder.

.mac only [[0]]-[[@]]