Masayuki Akamatsu

I uploaded aka.wiiremote 1.0B4 for Nintendo Wii Remote.

http://www.iamas.ac.jp/~aka/max/#aka_wiiremote

It supports multiple Wii Remotes in this version.

But I think it is still unstable on PowerPC-Mac.

I uploaded aka.wiiremote 1.0B4 for Nintendo Wii Remote.
http://www.iamas.ac.jp/~aka/max/#aka_wiiremote

It supports multiple Wii Remotes in this version.
But I think it is still unstable on PowerPC-Mac.

nintendo-wii-remote-object-1-0b4

This wii object is just great! I'm hoping some talented soul will translate the object to PC alos!!

I notice that you have to setup your computer for Wii Remote using 

"Bluetooth Setup Assistant" for the first time.

http://max.iamas.ac.jp:16080/modules/xeblog/?

In my experience with PowerBook G4, I have to configure my computer 

every time before I use Wii Remote. My object (and also other 

software, ex. DarwiinRemote) seems to work fine after the 

configuration. It needs just only once on Intel-Mac (MacBook Pro.

I notice that you have to setup your computer for Wii Remote using  
"Bluetooth Setup Assistant" for the first time.

http://max.iamas.ac.jp:16080/modules/xeblog/? 
action_xeblog_details=1&blog_id=67

In my experience with PowerBook G4, I have to configure my computer  
every time before I use Wii Remote.  My object (and also other  
software, ex. DarwiinRemote) seems to work fine after the  
configuration. It needs just only once on Intel-Mac (MacBook Pro.

I have tested the b4 version on a PPC. It has the same problem as the 

earlier version, I'm not able to get the leds lighting, vibrate or start 

monitoruing of ir after it has loaded. Bluetooth is set up as described 

in your blog post. Darwiin have the same behaviour. If it is working 

fine and reliable on an Intel-Mac, I suppose that it is an issue with 

PPC and either the wii framework or the bluetooth API. If anyone else 

have it working properly on PPC, please let me know.

Thanks for the object anyway, I hope to be able to get myself a new 

> I notice that you have to setup your computer for Wii Remote using 

> "Bluetooth Setup Assistant" for the first time.

http://max.iamas.ac.jp:16080/modules/xeblog/?action_xeblog_details=1&blog_id=67

> In my experience with PowerBook G4, I have to configure my computer 

> every time before I use Wii Remote. My object (and also other 

> software, ex. DarwiinRemote) seems to work fine after the 

> configuration. It needs just only once on Intel-Mac (MacBook Pro.

I have tested the b4 version on a PPC. It has the same problem as the 
earlier version, I'm not able to get the leds lighting, vibrate or start 
monitoruing of ir after it has loaded. Bluetooth is set up as described 
in your blog post. Darwiin have the same behaviour. If it is working 
fine and reliable on an Intel-Mac, I suppose that it is an issue with 
PPC and either the wii framework or the bluetooth API. If anyone else 
have it working properly on PPC, please let me know.

Thanks for the object anyway, I hope to be able to get myself a new 
laptop sometimes next year

Masayuki Akamatsu wrote:
> Hi,
>
> I notice that you have to setup your computer for Wii Remote using 
> "Bluetooth Setup Assistant" for the first time.
>
> http://max.iamas.ac.jp:16080/modules/xeblog/?action_xeblog_details=1&blog_id=67 
>
>
> In my experience with PowerBook G4, I have to configure my computer 
> every time before I use Wii Remote.  My object (and also other 
> software, ex. DarwiinRemote) seems to work fine after the 
> configuration. It needs just only once on Intel-Mac (MacBook Pro.
>
> Best,
> Masayuki 


I second that, same situation as before. Darwin has same behavior

first of all : Happy new year for all of you on this forum .

thanks Masayuki for that great patch, it was like a christmas gift ;-)

I have started working with it on my MacBook Pro and it works fine : I made a quick Makenote patch using the acceleration datas as velocity to control 3 midi instruments (one for each accelerometer axis) in Ableton Live : very cool ! The most abvious is the virtual maracas , but many more instruments are funny to control while dancing around ;-) .

I have in plan to use the Wii remote also in VJ stuff (in the OpenGL 3D space for example ), and please I have a question : 

- do you process in your code the raw data from the accelerometer, I mean scaling or any other treatment , or i sit as-i from the device ? 

- is it your choice to make the "acceleration" data behavior as it is , I mean if I understood well : 0 to 100 = negative acceleration, 100 to 155 = kind of angle report (X-axis and Y axis only) , 155 to 255 positive acceleration

- is it possible to make the stream of data from accelerometer more stable, I think U know what I mean, when Wii is in hand without any mouvement data should not change so quickly like if the hand is trembling .... I may do that treatment myself in the patch but I did'nt find any clue yet to do that ... if any one have an idea it will be welcome, may be it should be done in the code (object) to be more efficient, I don't know really .

I attach a piece of work-in-progress if someone is interested , it is not a grammy competitor but it can show (send wii_zooM and wii_zooB must be added and connected on an aka.wiiremote object at resp. "motion" and "button" outputs)

Hi Masayuki, Hi every body,
first of all : Happy new year for all of you on this forum .

thanks Masayuki for that great patch, it was like a christmas gift ;-) 

I have started working with it on my MacBook Pro and it works fine :  I made a quick Makenote patch using the acceleration datas as velocity to control 3 midi instruments (one for each accelerometer axis) in Ableton Live : very cool ! The most abvious is the virtual maracas , but many more instruments are funny to control while dancing around ;-) .

I have in plan to use the Wii remote also in VJ stuff (in the OpenGL 3D space for example ), and please I have a question : 
 - do you process in your code the raw data from the accelerometer, I mean scaling or any other treatment , or i sit as-i from the device ? 
 - is it your choice to make the "acceleration" data behavior as it is , I mean if I understood well : 0 to 100 = negative acceleration, 100 to 155 = kind of angle report (X-axis and Y axis only) , 155 to 255 positive acceleration
 - is it possible to make the stream of data from accelerometer more stable, I think U know what I mean, when Wii is in hand without any mouvement data should not change so quickly like if the hand is trembling .... I may do that treatment myself in the patch but I did'nt find any clue yet to do that ... if any one have an idea it will be welcome, may be it should be done in the code (object) to be more efficient, I don't know really .

On 2007/01/03, at 4:28, ravelomanantsoa marc wrote:

> - do you process in your code the raw data from the accelerometer, 

> I mean scaling or any other treatment , or i sit as-i from the 

> - is it your choice to make the "acceleration" data behavior as it 

> is , I mean if I understood well : 0 to 100 = negative 

> acceleration, 100 to 155 = kind of angle report (X-axis and Y axis 

> only) , 155 to 255 positive acceleration

You can pseud-calibrate it. For example, put Wiiremote on the 

horizontal table and remember the values on the front-side up, right- 

side up and bottom-side up. They are the reference values of no 

acceleration. (Of course, there is the acceleration of gravity if you 

I might be able to calibrate the Wiiremote internally in the future. 

But you should do it b yourself at this time.

> - is it possible to make the stream of data from accelerometer 

> more stable, I think U know what I mean, when Wii is in hand 

> without any mouvement data should not change so quickly like if the 

> hand is trembling .... I may do that treatment myself in the patch 

> but I did'nt find any clue yet to do that ... if any one have an 

> idea it will be welcome, may be it should be done in the code 

> (object) to be more efficient, I don't know really .

aka.wiiremote communicates Wiiremote automatically and outputs the 

values when it receives a bang message. I'll check the unstability 

that you mentioned but it might be a Wiiremote's internal behavior.

>  - do you process in your code the raw data from the accelerometer,  
> I mean scaling or any other treatment , or i sit as-i from the  
> device ?

>  - is it your choice to make the "acceleration" data behavior as it  
> is , I mean if I understood well : 0 to 100 = negative  
> acceleration, 100 to 155 = kind of angle report (X-axis and Y axis  
> only) , 155 to 255 positive acceleration

You can pseud-calibrate it. For example, put Wiiremote on the  
horizontal table and remember the values on the front-side up, right- 
side up and bottom-side up. They are the reference values of no  
acceleration. (Of course, there is the acceleration of gravity if you  
are on the earth.)

I might be able to calibrate the Wiiremote internally in the future.  
But you should do it b yourself at this time.

>  - is it possible to make the stream of data from accelerometer  
> more stable, I think U know what I mean, when Wii is in hand  
> without any mouvement data should not change so quickly like if the  
> hand is trembling .... I may do that treatment myself in the patch  
> but I did'nt find any clue yet to do that ... if any one have an  
> idea it will be welcome, may be it should be done in the code  
> (object) to be more efficient, I don't know really .

aka.wiiremote communicates Wiiremote automatically and outputs the  
values when it receives a bang message. I'll check the unstability  
that you mentioned but it might be a  Wiiremote's internal behavior.

> You can pseud-calibrate it. For example, put Wiiremote on the 

> horizontal table and remember the values on the front-side up, 

> right-side up and bottom-side up. They are the reference values of no 

> acceleration. (Of course, there is the acceleration of gravity if you 

> I might be able to calibrate the Wiiremote internally in the future. 

> But you should do it b yourself at this time.

I would prefer that nothing extra is done inside the external. It is not 

difficult to find workarounds smoothing the data to your needs, and 

there is a lot more flexibility in terms of how to do so if it is done 

in a Max patch instead of inside the external.

>> - is it possible to make the stream of data from accelerometer more 

>> stable, I think U know what I mean, when Wii is in hand without any 

>> mouvement data should not change so quickly like if the hand is 

>> trembling .... I may do that treatment myself in the patch but I 

>> did'nt find any clue yet to do that ... if any one have an idea it 

>> will be welcome, may be it should be done in the code (object) to be 

If you want data to be more stable, you should low-pass filter it one 

way or another. Some possibilities would be to use slide, or calculate 

the average of the last nth values. The Litter object lp.stacey in 

> aka.wiiremote communicates Wiiremote automatically and outputs the 

> values when it receives a bang message. I'll check the unstability 

> that you mentioned but it might be a Wiiremote's internal behavior.

> It depends on a "calibration".
>
> You can pseud-calibrate it. For example, put Wiiremote on the 
> horizontal table and remember the values on the front-side up, 
> right-side up and bottom-side up. They are the reference values of no 
> acceleration. (Of course, there is the acceleration of gravity if you 
> are on the earth.)
>
> I might be able to calibrate the Wiiremote internally in the future. 
> But you should do it b yourself at this time.

I would prefer that nothing extra is done inside the external. It is not 
difficult to find workarounds smoothing the data to your needs, and 
there is a lot more flexibility in terms of how to do so if it is done 
in a Max patch instead of inside the external.

>>  - is it possible to make the stream of data from accelerometer more 
>> stable, I think U know what I mean, when Wii is in hand without any 
>> mouvement data should not change so quickly like if the hand is 
>> trembling .... I may do that treatment myself in the patch but I 
>> did'nt find any clue yet to do that ... if any one have an idea it 
>> will be welcome, may be it should be done in the code (object) to be 
>> more efficient, I don't know really .

If you want data to be more stable, you should low-pass filter it one 
way or another. Some possibilities would be to use slide, or calculate 
the average of the last nth values. The Litter object lp.stacey in 
running mode is good for this.
> aka.wiiremote communicates Wiiremote automatically and outputs the 
> values when it receives a bang message. I'll check the unstability 
> that you mentioned but it might be a  Wiiremote's internal behavior.

your app makes max crash as soon as i click on "connect" message

will you fix it for macosx PowerpC users?

and best compliments also from this part.

i can confirm you that with powerPC
your app makes max crash as soon as i click on "connect" message

:-(
will you fix it for macosx PowerpC users?

thanx
and best compliments also from this part.

> your app makes max crash as soon as i click on "connect" message

In my experience with PowerBook G4, my object works.

I know some users reported the unstablities on PowerPC but I've not 

In my experience with PowerBook G4, my object works.
Please check my FAQ.

http://max.iamas.ac.jp:16080/modules/xeblog/? 
action_xeblog_details=1&blog_id=60

I know some users reported the unstablities on PowerPC but I've not  
pinpointed the cause yet.

Can you post a crashlog? might give more hints as to waht the problem is.

> will you fix it for macosx PowerpC users?

> and best compliments also from this part.

tommy wrote:
> i can confirm you that with powerPC
> your app makes max crash as soon as i click on "connect" message
>
>
> :-(
> will you fix it for macosx PowerpC users?
>
> thanx
> and best compliments also from this part.
>
> tom


Oh well i may say I'm sorry because it was just my fault.

I was not at home and trying to use your object without a blutooth system on my computer and without the wii.

The reason of the crash might be that as soon as i clicked the "connnect" button, without having set up bluetooth, it would crash the application.

Path: /Applications/MaxMSP 4.6/MaxMSP.app/Contents/MacOS/MaxMSP

Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x0000000a

0 libobjc.A.dylib     0x90a3f100 objc_msgSend + 32

1 com.apple.Bluetooth     0x952e8938 IOBluetoothDeviceSearchCreate + 440

2 com.apple.Bluetooth     0x953271e4 -[IOBluetoothDeviceInquiry startSearch] + 124

3 com.apple.Bluetooth     0x95326dd8 -[IOBluetoothDeviceInquiry start] + 196

4 com.apple.Bluetooth     0x95327cf4 IOBluetoothDeviceInquiryStart + 140

5 com.cycling74.MaxMSP46     0x00044be0 typedmess_fun + 3288 (message.c:694)

6 com.cycling74.MaxMSP46     0x0014a8ac outlet_anything + 536 (inletoutlet.c:960)

7 com.cycling74.MaxMSP46     0x00044874 typedmess_fun + 2412 (message.c:631)

8 com.cycling74.MaxMSP46     0x00044e2c typedmess + 104 (message.c:399)

9 com.cycling74.MaxMSP46     0x00045ef4 aeval + 1804 (message.c:1061)

10 com.cycling74.MaxMSP46     0x0000bbfc atombuf_eval + 216 (atombuf.c:234)

11 com.cycling74.MaxMSP46     0x00106258 vmessage_bang(_vmessage*) + 84 (vmessage.c:58)

12 com.cycling74.MaxMSP46     0x00108270 vmessage_click(_vmessage*) + 504 (vmessage.c:238)

13 com.cycling74.MaxMSP46     0x0001574c box_click + 224 (box.c:123)

14 com.cycling74.MaxMSP46     0x0004d37c patcher_boxclick + 652 (patcher.c:2175)

15 com.cycling74.MaxMSP46     0x0004ff6c patcher_click + 1692 (patcher.c:2424)

16 com.cycling74.MaxMSP46     0x00099b28 wind_click + 212 (window.c:1118)

17 com.cycling74.MaxMSP46     0x000a0e40 wind_event + 644 (window.c:818)

18 com.cycling74.MaxMSP46     0x00038f2c app_eventhandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 1512 (main.c:1597)

19 com.apple.HIToolbox     0x93207554 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 692

20 com.apple.HIToolbox     0x93206cac SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 372

21 com.apple.HIToolbox     0x9320da60 SendEventToEventTarget + 40

22 com.apple.HIToolbox     0x93299d48 HandleMouseEventForWindow(OpaqueWindowPtr*, OpaqueEventRef*, unsigned short) + 236

23 com.apple.HIToolbox     0x932992c0 HandleMouseEvent(OpaqueEventRef*) + 368

24 com.apple.HIToolbox     0x9320ddcc ToolboxEventDispatcherHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 496

25 com.apple.HIToolbox     0x932077a4 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1284

26 com.apple.HIToolbox     0x93206cac SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 372

27 com.apple.HIToolbox     0x9320da60 SendEventToEventTarget + 40

28 com.apple.HIToolbox     0x9324e7a0 ToolboxEventDispatcher + 92

29 com.apple.HIToolbox     0x9324e72c HLTBEventDispatcher + 16

30 com.apple.HIToolbox     0x9324cce4 RunApplicationEventLoop + 148

31 com.cycling74.MaxMSP46     0x0003859c app_run + 96 (main.c:1458)

32 com.cycling74.MaxMSP46     0x00038870 main + 704 (main.c:415)

33 com.cycling74.MaxMSP46     0x00001f5c _start + 340 (crt.c:272)

34 com.cycling74.MaxMSP46     0x00001e04 start + 60

0 libSystem.B.dylib     0x90054ae8 semaphore_timedwait_signal_trap + 8

1 libSystem.B.dylib     0x90071168 pthread_cond_timedwait_relative_np + 556

2 ...ple.CoreServices.CarbonCore     0x90bf5500 TSWaitOnSemaphoreCommon + 176

3 ...ple.CoreServices.CarbonCore     0x90bfd49c TimerThread + 60

4 libSystem.B.dylib     0x9002b508 _pthread_body + 96

0 libSystem.B.dylib     0x9000ab48 mach_msg_trap + 8

1 libSystem.B.dylib     0x9000aa9c mach_msg + 60

2 com.apple.audio.midi.CoreMIDI     0x970c7ac8 XServerMachPort::ReceiveMessage(int&, void*, int&) + 84

3 com.apple.audio.midi.CoreMIDI     0x970bac80 MIDIInPortThread::Run() + 64

4 com.apple.audio.midi.CoreMIDI     0x970bef44 XThread::RunHelper(void*) + 28

5 com.apple.audio.midi.CoreMIDI     0x970c887c CAPThread::Entry(CAPThread*) + 96

6 libSystem.B.dylib     0x9002b508 _pthread_body + 96

2 com.apple.CoreFoundation     0x907dcb78 __CFRunLoopRun + 832

3 com.apple.CoreFoundation     0x907dc47c CFRunLoopRunSpecific + 268

4 com.apple.audio.CoreAudio     0x9145563c HALRunLoop::OwnThread(void*) + 264

5 com.apple.audio.CoreAudio     0x914553dc CAPThread::Entry(CAPThread*) + 96

2 libjvm.dylib     0x9653ed2c operator new(unsigned long) + 7580

3 libjvm.dylib     0x9653ecc0 operator new(unsigned long) + 7472

4 libjvm.dylib     0x9653ec44 operator new(unsigned long) + 7348

5 libSystem.B.dylib     0x9002b508 _pthread_body + 96

2 libjvm.dylib     0x9658f578 jio_snprintf + 290832

3 libjvm.dylib     0x9658fb7c jio_snprintf + 292372

4 libjvm.dylib     0x9658f7d0 jio_snprintf + 291432

5 libjvm.dylib     0x9658f324 jio_snprintf + 290236

6 libjvm.dylib     0x9653ec44 operator new(unsigned long) + 7348

7 libSystem.B.dylib     0x9002b508 _pthread_body + 96

2 libjvm.dylib     0x9658f4bc jio_snprintf + 290644

3 libjvm.dylib     0x9659bf50 JVM_MonitorWait + 1984

4 libjvm.dylib     0x9659ba64 JVM_MonitorWait + 724

5 libjvm.dylib     0x9659b898 JVM_MonitorWait + 264

10 libjvm.dylib     0x965906fc jio_snprintf + 295316

11 libjvm.dylib     0x965905a4 jio_snprintf + 294972

12 libjvm.dylib     0x9659b5d8 JVM_StartThread + 2564

13 libjvm.dylib     0x9659b4bc JVM_StartThread + 2280

14 libjvm.dylib     0x9659b444 JVM_StartThread + 2160

15 libjvm.dylib     0x9659b2d8 JVM_StartThread + 1796

16 libjvm.dylib     0x9653ec44 operator new(unsigned long) + 7348

17 libSystem.B.dylib     0x9002b508 _pthread_body + 96

11 libjvm.dylib     0x965906fc jio_snprintf + 295316

12 libjvm.dylib     0x965905a4 jio_snprintf + 294972

Nintendo Wii Remote Object 1.0B4