Does aka.wiiremote work in M4L?
Does aka.wiiremote work in M4L?
I'm trying to get aka.wiiremote working in M4. It seems to work beautifully in Max itself, and works in a M4L patch in the Max editor.
When I go back to Live after adding aka.wiiremote to a patch, Live crashes when I try to connect the Wii remote. Once a patch crashes like this, I can't add the patch to a track without having Live crash instantly (bug reports sent).
Has anyone had any luck with this, or have any ideas that I might try?
When I go back to Live after adding aka.wiiremote to a patch, Live crashes when I try to connect the Wii remote. Once a patch crashes like this, I can't add the patch to a track without having Live crash instantly (bug reports sent).
Has anyone had any luck with this, or have any ideas that I might try?
-
- Posts: 1135
- Joined: Mon May 31, 2010 12:36 pm
- Contact:
Re: Does aka.wiiremote work in M4L?
I'm also curious about this as I'm thinking of buying a wiimote.
There's a keystrokes combination to prevent a buggy patch to loadbang and crash everything when launching it but I cannot remember what it is. Have a search in the cycling forum and you'll find it.
But, are you sure that aka.wiiremote is guilty?
There's a keystrokes combination to prevent a buggy patch to loadbang and crash everything when launching it but I cannot remember what it is. Have a search in the cycling forum and you'll find it.
But, are you sure that aka.wiiremote is guilty?
Re: Does aka.wiiremote work in M4L?
it worked for me...but i haven't used it in a while. i'll try again.
-
- Posts: 230
- Joined: Sun Dec 11, 2005 8:52 pm
- Location: FRANCE
- Contact:
Re: Does aka.wiiremote work in M4L?
Hi,DirkMyers wrote:I'm trying to get aka.wiiremote working in M4. It seems to work beautifully in Max itself, and works in a M4L patch in the Max editor.
When I go back to Live after adding aka.wiiremote to a patch, Live crashes when I try to connect the Wii remote. Once a patch crashes like this, I can't add the patch to a track without having Live crash instantly (bug reports sent).
Has anyone had any luck with this, or have any ideas that I might try?
for wiimote I strongly suggest OSCulator instead of aka.
have a look at www.osculator.net, its perfect pairing system is 100% reliable and you can do a lot with it
I use it with OSC sent to m4L devices
olivier
MacBookPro17", mac OS 10.6.2/RME FF400 & FF800
http://www.olivierseb.com
Max for Live training sessions in Paris @
http://www.apaxxdesigns.com/
Max for Live training sessions in Rennes @
http://www.intouchmedia.fr
Re: Does aka.wiiremote work in M4L?
Thanks -- it turned out I simply didn't have the external in a path that M4L could find. I can now talk to the wiimote, but it's spiking the CPU; just toggling an LED on the wiimote to indicate the connection is spiking up above 200% (on a pretty new 15" macbook pro).
I'll try out osculator, thanks!
I'll try out osculator, thanks!
-
- Posts: 146
- Joined: Sat May 03, 2008 9:33 pm
- Location: ATX
- Contact:
Re: Does aka.wiiremote work in M4L?
Can aka.wiimote handle more than one wiimote? Thanks. And I will definitely second the reliability of OSCulator. Here's how I do: http://www.youtube.com/user/craypo
Re: Does aka.wiiremote work in M4L?
Don't know if aka.wiimote can handle more than one wiimote -- I don't see a way to do it in the help.
I'm curious about the way you're using OSCulator, though. It looks like you're using OSC. If so, do you have any problems with CPU? I'm still seeing CPU spikes with OSCulator if I use OSC. It's definitely better than aka.wiiremote, but still burns too much horsepower for what I'm trying to do. Using MIDI routing seems OK.
I'm using the accelerometers very heavily (in effect, throwing the wiimote around). I'm not using the buttons at all. This seems to easily generate more data than my machine can keep up with if I use OSC.
I'm curious about the way you're using OSCulator, though. It looks like you're using OSC. If so, do you have any problems with CPU? I'm still seeing CPU spikes with OSCulator if I use OSC. It's definitely better than aka.wiiremote, but still burns too much horsepower for what I'm trying to do. Using MIDI routing seems OK.
I'm using the accelerometers very heavily (in effect, throwing the wiimote around). I'm not using the buttons at all. This seems to easily generate more data than my machine can keep up with if I use OSC.
-
- Posts: 230
- Joined: Sun Dec 11, 2005 8:52 pm
- Location: FRANCE
- Contact:
Re: Does aka.wiiremote work in M4L?
Hinatecraypo wrote:Can aka.wiimote handle more than one wiimote? Thanks. And I will definitely second the reliability of OSCulator. Here's how I do: http://www.youtube.com/user/craypo
AFAIR aka.wiimote can handle more than one device, but I don't remember the "trick" to do so.
You will have to use one object for each wiimote of course then pair the devices one by one.
This is the worst part because pairing was always painful, that's the 1st reason I switched to Osculator.
I can use up to 5 wiimote on my macbookpro core2duo 2,3Ghz and 7 on the new one unibody corei7
Bluetooth bandwidth is the limit of course
MacBookPro17", mac OS 10.6.2/RME FF400 & FF800
http://www.olivierseb.com
Max for Live training sessions in Paris @
http://www.apaxxdesigns.com/
Max for Live training sessions in Rennes @
http://www.intouchmedia.fr
-
- Posts: 230
- Joined: Sun Dec 11, 2005 8:52 pm
- Location: FRANCE
- Contact:
Re: Does aka.wiiremote work in M4L?
i use many wiimotes with nunchuks and motion plus, % cpu is around 17 - 20% on core2 duo 2,33GhzDirkMyers wrote:Don't know if aka.wiimote can handle more than one wiimote -- I don't see a way to do it in the help.
I'm curious about the way you're using OSCulator, though. It looks like you're using OSC. If so, do you have any problems with CPU? I'm still seeing CPU spikes with OSCulator if I use OSC. It's definitely better than aka.wiiremote, but still burns too much horsepower for what I'm trying to do. Using MIDI routing seems OK.
I'm using the accelerometers very heavily (in effect, throwing the wiimote around). I'm not using the buttons at all. This seems to easily generate more data than my machine can keep up with if I use OSC.
just turn flashing lights and monitors off on Osculator, try to use packed datas instead of individual to save OSC bandwidth.
olivier
MacBookPro17", mac OS 10.6.2/RME FF400 & FF800
http://www.olivierseb.com
Max for Live training sessions in Paris @
http://www.apaxxdesigns.com/
Max for Live training sessions in Rennes @
http://www.intouchmedia.fr