Hi list.
I've got [wiimote] compiled and almost working with 0.43 vanilla...except that the accelerometer data doesn't seem to be working.
I've got (what I think is a) latest generation black wiimote with built-in Motion Plus, and my testing was without the nunchuck or anything attached.
I can discover the device and the help patch shows all the button presses and I can toggle the LEDs and vibrator using the help patch, but even after clicking the toggle the accelerator data is just absent.
I believe that an extra blank line shows up in the Pd console when I send the accel activation message, but aside from that there's just nothing.
I read the blurb in the [wiimote] readme about the problems with older versions of libcwiid, but I've got 0.6.00+svn201-2+b2 from debian sid, which I believe is pretty damn close to the latest...
Has anybody experienced this? Any suggestions other than compiling libcwiid myself and trying out the motionplus_sensitivity patch?
Thanks!
-jason http://noisybox.net
Hi Jason
A few people from this list worked on getting [wiimote] into Debian. Under unstable / sid it is already available as the package 'pd-wiimote'. I'd be glad, if you could try this one and report if it is working with your device.
Note: It depends on the meta-package 'pd' thus it will probably install 'puredata', although you have a Pd version already installed in /usr/local/. However, this shouldn't hurt at all. I just want to let you know, and also to take care to set proper paths for your locally installed Pd, since the 'pd-wiimote' will install into /usr/lib/pd/extra.
Roman
On Tue, 2011-04-12 at 00:02 -0700, Jason Plumb wrote:
Hi list.
I've got [wiimote] compiled and almost working with 0.43 vanilla...except that the accelerometer data doesn't seem to be working.
I've got (what I think is a) latest generation black wiimote with built-in Motion Plus, and my testing was without the nunchuck or anything attached.
I can discover the device and the help patch shows all the button presses and I can toggle the LEDs and vibrator using the help patch, but even after clicking the toggle the accelerator data is just absent.
I believe that an extra blank line shows up in the Pd console when I send the accel activation message, but aside from that there's just nothing.
I read the blurb in the [wiimote] readme about the problems with older versions of libcwiid, but I've got 0.6.00+svn201-2+b2 from debian sid, which I believe is pretty damn close to the latest...
Has anybody experienced this? Any suggestions other than compiling libcwiid myself and trying out the motionplus_sensitivity patch?
Thanks!
-jason http://noisybox.net
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Somewhat OT perhaps, but can you also try disis_wiimote which supports motion plus (compiled against latest SVN cwiid lib)? I just released new version earlier today that also fixes a few bugs and makes it even more xrun-proof.
You can find it on the L2Ork website at http://l2ork.music.vt.edu/main (then click Join the L2Orkmania->Software).
Best wishes,
Ico
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 04/13/2011 05:56 PM, Ivica Ico Bukvic wrote:
Somewhat OT perhaps, but can you also try disis_wiimote which supports motion plus (compiled against latest SVN cwiid lib)? I just released new version earlier today that also fixes a few bugs and makes it even more xrun-proof.
just to make sure: [wiimote] (which is packaged into debian/ubuntu), definitely does support the motionplus extension.
mgsdt IOhannes
On 04/13/2011 08:56 AM, Ivica Ico Bukvic wrote:
Somewhat OT perhaps, but can you also try disis_wiimote which supports motion plus (compiled against latest SVN cwiid lib)? I just released new version earlier today that also fixes a few bugs and makes it even more xrun-proof.
Hi Ico,
Thanks for the tip!
I was able to get [disis_wiimote] compiled and working after:
I haven't yet tried Roman's suggestion debian-sid flavor of [wiimote] with Pd, but will try to in the next few days.
One difference between the two -- [disis_wiimote] seems to use bang/metro based polling, but [wiimote] does not. Does [wiimote] just do the polling internally?
-jason http://noisybox.net
Hi Ico,
Thanks for the tip!
I was able to get [disis_wiimote] compiled and working after:
- Changing the #include not to assume extended (cuz I run vanilla)
- Adding -fPIC to the LINUXCFLAGS because I'm running 64-bit.
I haven't yet tried Roman's suggestion debian-sid flavor of [wiimote] with Pd, but will try to in the next few days.
One difference between the two -- [disis_wiimote] seems to use bang/metro based polling, but [wiimote] does not. Does [wiimote] just do the polling internally?
Yep, whenever cwiid sends its info to it which often breaks the Pd GUI since that message can arrive in the middle of updating gui queue, effectively crashing the gui (even though the engine continues to run, no further updates are possible to the tcl/tk gui), hence the original wiimote implementation (at least last time I checked it) is in this respect buggy. Likewise (again, last time I checked) it does not have threaded design as disis_wiimote has, which means any time you send rumble command or change LED command via the wiimote object, it will result in an xrun (at least it does on lower powered machines like netbooks).
Given that wiimote cannot send updates more than approx. 40 times a second, overburdening your patch with as-fast-as-possible output seems unnecessary, hence the metro implementation. In addition, disis_wiimote also outputs button data only when it actually changes to minimize redundant computation downstream. It also gives you a dedicated output for connection which can be conveniently used to automate things upon connection.
Hope this helps!