Gregory Taylor

I'm running 10.4.11 on this MacBook Pro and have a question

that's come my way from a recent workshop. In a nutshell, it's

I've got a nice little Wii here. I open the aka.wiiremote

help file in the most recent version of Max 5 and simply

click on the toggle above the "expansion $1" message box.

Max 5 quits. The crashlog suggests that there's an

Objective C problem (see the top of the log below), 

which might indicate that this isn't a Max problem 

Clicking on that box with a Wii remote nearby is all

I need. No "hit the 1 and 2 button" needed. In fact,

I can also kill it 100% of the time by turning off

the "motion" message box set with the loadbang.

One thing it occurs to me to wonder about besides

whether or not this is what everyone sees [besides

the nice person who brought this to my attention in

the first place] is whether or not it's a Panther

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

Codes: KERN_INVALID_ADDRESS (0x0001) at 0x7473696c

0 libobjc.A.dylib     0x90a594b8 objc_msgSend + 8

1 org.akamatsu.aka.wiiremote     0x19897e68 wiiremote_disconnect + 276

2 org.akamatsu.aka.wiiremote     0x19897f94 sendCommand + 163

3 org.akamatsu.aka.wiiremote     0x1989825f requestUpdates + 193

4 org.akamatsu.aka.wiiremote     0x1989835e wiiremote_motionsensor + 26

5 org.akamatsu.aka.wiiremote     0x19896e21 akawiiremote_motionsensor + 28

6 com.cycling74.MaxMSP     0x00018781 typedmess_fun + 1283

7 com.cycling74.MaxMSP     0x0005c2e4 outlet_anything + 510

8 com.cycling74.MaxMSP     0x0001858c typedmess_fun + 782

9 com.cycling74.MaxMSP     0x00018abd typedmess + 83

10 com.cycling74.MaxMSP     0x00019141 aeval + 917

11 com.cycling74.MaxMSP     0x00005766 atombuf_eval + 152

12 com.cycling74.MaxAPI     0x019d017c atombuf_eval + 60

13 com.cycling74.message     0x198cf0f1 jmessage_atombuf_eval + 429

14 com.cycling74.message     0x198cf429 jmessage_int + 130

15 com.cycling74.MaxMSP     0x0005b61f outlet_int + 529

16 com.cycling74.MaxAPI     0x019c3cc3 outlet_int + 38

17 com.cycling74.toggle     0x198c631a jtoggle_int + 45

18 com.cycling74.MaxMSP     0x000ac003 object_method + 901

19 com.cycling74.MaxMSP     0x000fc18d BoxComponent::sendMouseMessage(juce::MouseEvent const&, symbol*, double, double) + 265

20 com.cycling74.MaxMSP     0x000fefcc BoxComponent::mouseDown(juce::MouseEvent const&) + 234

21 com.cycling74.MaxMSP     0x002dbb3a juce::Component::internalMouseDown(int, int) + 506

22 com.cycling74.MaxMSP     0x00413200 juce::ComponentPeer::handleMouseDown(int, int, long long) + 432

23 com.cycling74.MaxMSP     0x0029c95c juce::HIViewComponentPeer::handleMouseEvent(OpaqueEventHandlerCallRef*, OpaqueEventRef*) + 1244

24 com.cycling74.MaxMSP     0x0029d2f5 juce::HIViewComponentPeer::handleWindowEvent(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 277

25 com.apple.HIToolbox     0x92df04d7 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1093

26 com.apple.HIToolbox     0x92defb7c SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 304

27 com.apple.HIToolbox     0x92df6f7c SendEventToEventTarget + 56

28 com.apple.HIToolbox     0x92df740f ToolboxEventDispatcherHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 1169

29 com.apple.HIToolbox     0x92df088e DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 2044

30 com.apple.HIToolbox     0x92defb7c SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 304

31 com.apple.HIToolbox     0x92df6f7c SendEventToEventTarget + 56

32 com.cycling74.MaxMSP     0x002944aa juce::juce_dispatchNextMessageOnSystemQueue(bool) + 234

33 com.cycling74.MaxMSP     0x002a3043 juce::MessageManager::runDispatchLoop() + 131

34 com.cycling74.MaxMSP     0x0029e94f juce::JUCEApplication::main(juce::String&, juce::JUCEApplication*) + 415

35 com.cycling74.MaxMSP     0x0029eb7a juce::JUCEApplication::main(int, char**, juce::JUCEApplication*) + 90

36 com.cycling74.MaxMSP     0x001c411c main + 76

37 com.cycling74.MaxMSP     0x00002972 _start + 216

38 com.cycling74.MaxMSP     0x00002899 start + 41

0 libSystem.B.dylib     0x90047dd7 semaphore_timedwait_signal_trap + 7

1 ...ple.CoreServices.CarbonCore     0x90ce1da5 TSWaitOnSemaphoreCommon + 163

2 ...ple.CoreServices.CarbonCore     0x90ce8d8d TimerThread + 87

3 libSystem.B.dylib     0x90024227 _pthread_body + 84

I'm running 10.4.11 on this MacBook Pro and have a question
that's come my way from a recent workshop. In a nutshell, it's
the following:

I've got a nice little Wii here. I open the aka.wiiremote
help file in the most recent version of Max 5 and simply
click on the toggle above the "expansion $1" message box.

Max 5 quits. The crashlog suggests that there's an
Objective C problem (see the top of the log below), 
which might indicate that this isn't a Max problem 
at all [might not, of course].

Clicking on that box with a Wii remote nearby is all
I need. No "hit the 1 and 2 button" needed. In fact,
I can also kill it 100% of the time by turning off
the "motion" message box set with the loadbang.

One thing it occurs to me to wonder about besides
whether or not this is what everyone sees [besides
the nice person who brought this to my attention in
the first place] is whether or not it's a Panther
vs. Leopard problem.

___the top of the log___
Date/Time:      2008-05-28 23:24:35.055 -0500
OS Version:     10.4.11 (Build 8S2167)
Report Version: 4

Command: MaxMSP
Path:    /Applications/Max5/MaxMSP.app/Contents/MacOS/MaxMSP
Parent:  WindowServer [215]

Exception:  EXC_BAD_ACCESS (0x0001)
Codes:      KERN_INVALID_ADDRESS (0x0001) at 0x7473696c

Thread 0 Crashed:
0   libobjc.A.dylib                	0x90a594b8 objc_msgSend + 8
1   org.akamatsu.aka.wiiremote     	0x19897e68 wiiremote_disconnect + 276
2   org.akamatsu.aka.wiiremote     	0x19897f94 sendCommand + 163
3   org.akamatsu.aka.wiiremote     	0x1989825f requestUpdates + 193
4   org.akamatsu.aka.wiiremote     	0x1989835e wiiremote_motionsensor + 26
5   org.akamatsu.aka.wiiremote     	0x19896e21 akawiiremote_motionsensor + 28
6   com.cycling74.MaxMSP           	0x00018781 typedmess_fun + 1283
7   com.cycling74.MaxMSP           	0x0005c2e4 outlet_anything + 510
8   com.cycling74.MaxMSP           	0x0001858c typedmess_fun + 782
9   com.cycling74.MaxMSP           	0x00018abd typedmess + 83
10  com.cycling74.MaxMSP           	0x00019141 aeval + 917
11  com.cycling74.MaxMSP           	0x00005766 atombuf_eval + 152
12  com.cycling74.MaxAPI           	0x019d017c atombuf_eval + 60
13  com.cycling74.message          	0x198cf0f1 jmessage_atombuf_eval + 429
14  com.cycling74.message          	0x198cf429 jmessage_int + 130
15  com.cycling74.MaxMSP           	0x0005b61f outlet_int + 529
16  com.cycling74.MaxAPI           	0x019c3cc3 outlet_int + 38
17  com.cycling74.toggle           	0x198c631a jtoggle_int + 45
18  com.cycling74.MaxMSP           	0x000ac003 object_method + 901
19  com.cycling74.MaxMSP           	0x000fc18d BoxComponent::sendMouseMessage(juce::MouseEvent const&, symbol*, double, double) + 265
20  com.cycling74.MaxMSP           	0x000fefcc BoxComponent::mouseDown(juce::MouseEvent const&) + 234
21  com.cycling74.MaxMSP           	0x002dbb3a juce::Component::internalMouseDown(int, int) + 506
22  com.cycling74.MaxMSP           	0x00413200 juce::ComponentPeer::handleMouseDown(int, int, long long) + 432
23  com.cycling74.MaxMSP           	0x0029c95c juce::HIViewComponentPeer::handleMouseEvent(OpaqueEventHandlerCallRef*, OpaqueEventRef*) + 1244
24  com.cycling74.MaxMSP           	0x0029d2f5 juce::HIViewComponentPeer::handleWindowEvent(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 277
25  com.apple.HIToolbox            	0x92df04d7 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1093
26  com.apple.HIToolbox            	0x92defb7c SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 304
27  com.apple.HIToolbox            	0x92df6f7c SendEventToEventTarget + 56
28  com.apple.HIToolbox            	0x92df740f ToolboxEventDispatcherHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 1169
29  com.apple.HIToolbox            	0x92df088e DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 2044
30  com.apple.HIToolbox            	0x92defb7c SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 304
31  com.apple.HIToolbox            	0x92df6f7c SendEventToEventTarget + 56
32  com.cycling74.MaxMSP           	0x002944aa juce::juce_dispatchNextMessageOnSystemQueue(bool) + 234
33  com.cycling74.MaxMSP           	0x002a3043 juce::MessageManager::runDispatchLoop() + 131
34  com.cycling74.MaxMSP           	0x0029e94f juce::JUCEApplication::main(juce::String&, juce::JUCEApplication*) + 415
35  com.cycling74.MaxMSP           	0x0029eb7a juce::JUCEApplication::main(int, char**, juce::JUCEApplication*) + 90
36  com.cycling74.MaxMSP           	0x001c411c main + 76
37  com.cycling74.MaxMSP           	0x00002972 _start + 216
38  com.cycling74.MaxMSP           	0x00002899 start + 41

Thread 1:
0   libSystem.B.dylib              	0x90047dd7 semaphore_timedwait_signal_trap + 7
1   ...ple.CoreServices.CarbonCore 	0x90ce1da5 TSWaitOnSemaphoreCommon + 163
2   ...ple.CoreServices.CarbonCore 	0x90ce8d8d TimerThread + 87
3   libSystem.B.dylib              	0x90024227 _pthread_body + 84


aka-wiiremote-and-max-5

No time to debug right now...maybe tomorrow if the author doesn't get 

On May 28, 2008, at 9:27 PM, Gregory Taylor wrote:

> I'm running 10.4.11 on this MacBook Pro and have a question

> that's come my way from a recent workshop. In a nutshell, it's

> I've got a nice little Wii here. I open the aka.wiiremote

> help file in the most recent version of Max 5 and simply

> click on the toggle above the "expansion $1" message box.

> Max 5 quits. The crashlog suggests that there's an

> Objective C problem (see the top of the log below),

> which might indicate that this isn't a Max problem

> Clicking on that box with a Wii remote nearby is all

> I need. No "hit the 1 and 2 button" needed. In fact,

> I can also kill it 100% of the time by turning off

> the "motion" message box set with the loadbang.

> One thing it occurs to me to wonder about besides

> whether or not this is what everyone sees [besides

> the nice person who brought this to my attention in

> the first place] is whether or not it's a Panther

> Do any of you see that behavior in 10.5?

> Date/Time: 2008-05-28 23:24:35.055 -0500

> Path: /Applications/Max5/MaxMSP.app/Contents/MacOS/MaxMSP

> Codes: KERN_INVALID_ADDRESS (0x0001) at 0x7473696c

> 0 libobjc.A.dylib     0x90a594b8 objc_msgSend + 8

> 1 org.akamatsu.aka.wiiremote     0x19897e68 wiiremote_disconnect 

> 2 org.akamatsu.aka.wiiremote     0x19897f94 sendCommand + 163

> 3 org.akamatsu.aka.wiiremote     0x1989825f requestUpdates + 193

No time to debug right now...maybe tomorrow if the author doesn't get  
to it first...

>
> I'm running 10.4.11 on this MacBook Pro and have a question
> that's come my way from a recent workshop. In a nutshell, it's
> the following:
>
> I've got a nice little Wii here. I open the aka.wiiremote
> help file in the most recent version of Max 5 and simply
> click on the toggle above the "expansion $1" message box.
>
> Max 5 quits. The crashlog suggests that there's an
> Objective C problem (see the top of the log below),
> which might indicate that this isn't a Max problem
> at all [might not, of course].
>
> Clicking on that box with a Wii remote nearby is all
> I need. No "hit the 1 and 2 button" needed. In fact,
> I can also kill it 100% of the time by turning off
> the "motion" message box set with the loadbang.
>
> One thing it occurs to me to wonder about besides
> whether or not this is what everyone sees [besides
> the nice person who brought this to my attention in
> the first place] is whether or not it's a Panther
> vs. Leopard problem.
>
> Do any of you see that behavior in 10.5?
>
> ___the top of the log___
> Date/Time:      2008-05-28 23:24:35.055 -0500
> OS Version:     10.4.11 (Build 8S2167)
> Report Version: 4
>
> Command: MaxMSP
> Path:    /Applications/Max5/MaxMSP.app/Contents/MacOS/MaxMSP
> Parent:  WindowServer [215]
>
> Version: 5.0.2 (34989) (5.0.2)
>
> PID:    479
> Thread: 0
>
> Exception:  EXC_BAD_ACCESS (0x0001)
> Codes:      KERN_INVALID_ADDRESS (0x0001) at 0x7473696c
>
> Thread 0 Crashed:
> 0   libobjc.A.dylib                	0x90a594b8 objc_msgSend + 8
> 1   org.akamatsu.aka.wiiremote     	0x19897e68 wiiremote_disconnect  
> + 276
> 2   org.akamatsu.aka.wiiremote     	0x19897f94 sendCommand + 163
> 3   org.akamatsu.aka.wiiremote     	0x1989825f requestUpdates + 193
> 4   org.akamatsu.aka.wiiremote     	0x1989835e  
> wiiremote_motionsensor + 26
> 5   org.akamatsu.aka.wiiremote     	0x19896e21  
> akawiiremote_motionsensor + 28
> 6   com.cycling74.MaxMSP           	0x00018781 typedmess_fun + 1283
> 7   com.cycling74.MaxMSP           	0x0005c2e4 outlet_anything + 510
> 8   com.cycling74.MaxMSP           	0x0001858c typedmess_fun + 782
> 9   com.cycling74.MaxMSP           	0x00018abd typedmess + 83
> 10  com.cycling74.MaxMSP           	0x00019141 aeval + 917
> 11  com.cycling74.MaxMSP           	0x00005766 atombuf_eval + 152
> 12  com.cycling74.MaxAPI           	0x019d017c atombuf_eval + 60
> 13  com.cycling74.message          	0x198cf0f1 jmessage_atombuf_eval  
> + 429
> 14  com.cycling74.message          	0x198cf429 jmessage_int + 130
> 15  com.cycling74.MaxMSP           	0x0005b61f outlet_int + 529
> 16  com.cycling74.MaxAPI           	0x019c3cc3 outlet_int + 38
> 17  com.cycling74.toggle           	0x198c631a jtoggle_int + 45
> 18  com.cycling74.MaxMSP           	0x000ac003 object_method + 901
> 19  com.cycling74.MaxMSP           	0x000fc18d  
> BoxComponent::sendMouseMessage(juce::MouseEvent const&, symbol*,  
> double, double) + 265
> 20  com.cycling74.MaxMSP           	0x000fefcc  
> BoxComponent::mouseDown(juce::MouseEvent const&) + 234
> 21  com.cycling74.MaxMSP           	0x002dbb3a  
> juce::Component::internalMouseDown(int, int) + 506
> 22  com.cycling74.MaxMSP           	0x00413200  
> juce::ComponentPeer::handleMouseDown(int, int, long long) + 432
> 23  com.cycling74.MaxMSP           	0x0029c95c  
> juce 
> ::HIViewComponentPeer::handleMouseEvent(OpaqueEventHandlerCallRef*,  
> OpaqueEventRef*) + 1244
> 24  com.cycling74.MaxMSP           	0x0029d2f5  
> juce 
> ::HIViewComponentPeer::handleWindowEvent(OpaqueEventHandlerCallRef*,  
> OpaqueEventRef*, void*) + 277
> 25  com.apple.HIToolbox            	0x92df04d7  
> DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*,  
> HandlerCallRec*) + 1093
> 26  com.apple.HIToolbox            	0x92defb7c  
> SendEventToEventTargetInternal(OpaqueEventRef*,  
> OpaqueEventTargetRef*, HandlerCallRec*) + 304
> 27  com.apple.HIToolbox            	0x92df6f7c  
> SendEventToEventTarget + 56
> 28  com.apple.HIToolbox            	0x92df740f  
> ToolboxEventDispatcherHandler(OpaqueEventHandlerCallRef*,  
> OpaqueEventRef*, void*) + 1169
> 29  com.apple.HIToolbox            	0x92df088e  
> DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*,  
> HandlerCallRec*) + 2044
> 30  com.apple.HIToolbox            	0x92defb7c  
> SendEventToEventTargetInternal(OpaqueEventRef*,  
> OpaqueEventTargetRef*, HandlerCallRec*) + 304
> 31  com.apple.HIToolbox            	0x92df6f7c  
> SendEventToEventTarget + 56
> 32  com.cycling74.MaxMSP           	0x002944aa  
> juce::juce_dispatchNextMessageOnSystemQueue(bool) + 234
> 33  com.cycling74.MaxMSP           	0x002a3043  
> juce::MessageManager::runDispatchLoop() + 131
> 34  com.cycling74.MaxMSP           	0x0029e94f  
> juce::JUCEApplication::main(juce::String&, juce::JUCEApplication*) +  
> 415
> 35  com.cycling74.MaxMSP           	0x0029eb7a  
> juce::JUCEApplication::main(int, char**, juce::JUCEApplication*) + 90
> 36  com.cycling74.MaxMSP           	0x001c411c main + 76
> 37  com.cycling74.MaxMSP           	0x00002972 _start + 216
> 38  com.cycling74.MaxMSP           	0x00002899 start + 41
>
> Thread 1:
> 0   libSystem.B.dylib              	0x90047dd7  
> semaphore_timedwait_signal_trap + 7
> 1   ...ple.CoreServices.CarbonCore 	0x90ce1da5  
> TSWaitOnSemaphoreCommon + 163
> 2   ...ple.CoreServices.CarbonCore 	0x90ce8d8d TimerThread + 87
> 3   libSystem.B.dylib              	0x90024227 _pthread_body + 84
> --
> knowledge is not enough/science is not enough/Love is dreaming this  
> equation


Quote: Gregory Taylor wrote on Wed, 28 May 2008 21:27

----------------------------------------------------

> Objective C problem (see the top of the log below), 

> which might indicate that this isn't a Max problem 

I'm getting a similar crash with Max 5 + OS 10.5.3, and my wiiremote is not even in the room.

Quote: Gregory Taylor wrote on Wed, 28 May 2008 21:27
----------------------------------------------------
> I'm running 10.4.11 on this MacBook Pro and have a question
> that's come my way from a recent workshop. In a nutshell, it's
> the following:
>
> I've got a nice little Wii here. I open the aka.wiiremote
> help file in the most recent version of Max 5 and simply
> click on the toggle above the "expansion $1" message box.
>
> Max 5 quits. The crashlog suggests that there's an
> Objective C problem (see the top of the log below), 
> which might indicate that this isn't a Max problem 
> at all [might not, of course].
>
>

I came across a similar bug and it happens to me when I try to change the LED, expansion or something else when the Wii Remote is not connected with the aka.wiiremote object.

It is an easy bug to fix I only had to add an if statement in those functions checking if the Wii Remote is connected or not.

This should do the trick, if you're not really into coding you can just send me a message I will send you my modified aka.wiiremote object.

Maybe i repeat myself, but OSCulator runs well here. Maybe try that instead, i am not sure, if it gives you all the features of aka.wiiremote though.

Maybe i repeat myself, but OSCulator runs well here. Maybe try that instead, i am not sure, if it gives you all the features of aka.wiiremote though.
But it is very stable.

aka.wiiremote and Max 5