barry threw

I am developing a graphical Max object, and am having problems. The 

major issue is that my object crashes Max on instantiation. However, if 

there is already an instance of this object in a patch (i.e. you open a 

patch with the object in it), it loads correctly. You can make copies 

of the object in the normal option-drag manner, and they work correctly.

If anyone has had this kind of issue, and knows some troubleshooting 

steps to solve it, advice would be appriciated.

To debug said object automatically from XCode, I must use Max Runtime as 

my executable. Because my object only crashes Max on instantiation, not 

from an object already loaded in patcher, I suppose I must create a new 

instance of my object via Max Scripting. I can't seem to figure out how 

to make an instance of a user created external. I just have a 

[loadbang] -> [message] -> [thispatcher] with the following in the 

message box: script new user myobject 318 192 15 200 128 1 0 12...bunch 

of other crap; This doesn't seem to work, I get the message; "patcher: 

Help with this issue is also appreciated.

Today, Noise is triumphant and reigns sovereign over the sensibility of men.    

I am developing a graphical Max object, and am having problems.  The 
major issue is that my object crashes Max on instantiation.  However, if 
there is already an instance of this object in a patch (i.e. you open a 
patch with the object in it), it loads correctly.  You can make copies 
of the object in the normal option-drag manner, and they work correctly.

If anyone has had this kind of issue, and knows some troubleshooting 
steps to solve it, advice would be appriciated.

To debug said object automatically from XCode, I must use Max Runtime as 
my executable.  Because my object only crashes Max on instantiation, not 
from an object already loaded in patcher, I suppose I must create a new 
instance of my object via Max Scripting.  I can't seem to figure out how 
to make an instance of a user created external.  I just have a 
[loadbang] -> [message] -> [thispatcher] with the following in the 
message box: script new user myobject 318 192 15 200 128 1 0 12...bunch 
of other crap;  This doesn't seem to work, I get the message; "patcher: 
doesn't understand myobject".

-- 
barry threw
composition : sound : programming
http://www.barrythrew.com 
bthrew(at)gmail(dot)com
857-544-3967

Today, Noise is triumphant and reigns sovereign over the sensibility of men.	
- Luigi Russolo, The Art of Noises


debugging-loading-a-custom-max-object-via-scripting

You want "script new user myobject blah blah blah", i believe.

As for your development problem, I would look at the object's menu 

function or the way that you're processing args to the object, since 

it sounds like you may be passing bad/NULL/not enough/too much into 

Am 13.03.2007 um 04:38 schrieb Barry Threw:

> I am developing a graphical Max object, and am having problems. 

> The major issue is that my object crashes Max on instantiation. 

> However, if there is already an instance of this object in a patch 

> (i.e. you open a patch with the object in it), it loads correctly. 

> You can make copies of the object in the normal option-drag manner, 

> If anyone has had this kind of issue, and knows some 

> troubleshooting steps to solve it, advice would be appriciated.

> To debug said object automatically from XCode, I must use Max 

> Runtime as my executable. Because my object only crashes Max on 

> instantiation, not from an object already loaded in patcher, I 

> suppose I must create a new instance of my object via Max 

> Scripting. I can't seem to figure out how to make an instance of a 

> user created external. I just have a [loadbang] -> [message] ->

> [thispatcher] with the following in the message box: script new 

> user myobject 318 192 15 200 128 1 0 12...bunch of other crap; 

> This doesn't seem to work, I get the message; "patcher: doesn't 

> Help with this issue is also appreciated.

> Today, Noise is triumphant and reigns sovereign over the 

You want "script new  user myobject blah blah blah", i believe.

As for your development problem, I would look at the object's menu  
function or the way that you're processing args to the object, since  
it sounds like you may be passing bad/NULL/not enough/too much into  
the new method from the menu method.

> Oh Oracle!
>
> I am developing a graphical Max object, and am having problems.   
> The major issue is that my object crashes Max on instantiation.   
> However, if there is already an instance of this object in a patch  
> (i.e. you open a patch with the object in it), it loads correctly.   
> You can make copies of the object in the normal option-drag manner,  
> and they work correctly.
>
> If anyone has had this kind of issue, and knows some  
> troubleshooting steps to solve it, advice would be appriciated.
>
> Sub Issue:
>
> To debug said object automatically from XCode, I must use Max  
> Runtime as my executable.  Because my object only crashes Max on  
> instantiation, not from an object already loaded in patcher, I  
> suppose I must create a new instance of my object via Max  
> Scripting.  I can't seem to figure out how to make an instance of a  
> user created external.  I just have a [loadbang] -> [message] ->
> [thispatcher] with the following in the message box: script new  
> user myobject 318 192 15 200 128 1 0 12...bunch of other crap;   
> This doesn't seem to work, I get the message; "patcher: doesn't  
> understand myobject".
>
> Help with this issue is also appreciated.
>
> Thanks,
>
> barry
>
> -- 
> barry threw
> composition : sound : programming
> http://www.barrythrew.com bthrew(at)gmail(dot)com
> 857-544-3967
>
> Today, Noise is triumphant and reigns sovereign over the  
> sensibility of men.	
> - Luigi Russolo, The Art of Noises
>


Thanks, the scripting works. In fact, the object instantiates correctly 

when called via Max scripting. The crash only occurs when the object is 

I'll look into the null argument possibility. It sounds very promising. 

I'm not so good at this graphical Max object thing yet....

> You want "script new user myobject blah blah blah", i believe.

> As for your development problem, I would look at the object's menu 

> function or the way that you're processing args to the object, since it 

> sounds like you may be passing bad/NULL/not enough/too much into the new 

> Am 13.03.2007 um 04:38 schrieb Barry Threw:

>> I am developing a graphical Max object, and am having problems. The 

>> major issue is that my object crashes Max on instantiation. However, 

>> if there is already an instance of this object in a patch (i.e. you 

>> open a patch with the object in it), it loads correctly. You can make 

>> copies of the object in the normal option-drag manner, and they work 

>> If anyone has had this kind of issue, and knows some troubleshooting 

>> steps to solve it, advice would be appriciated.

>> To debug said object automatically from XCode, I must use Max Runtime 

>> as my executable. Because my object only crashes Max on 

>> instantiation, not from an object already loaded in patcher, I suppose 

>> I must create a new instance of my object via Max Scripting. I can't 

>> seem to figure out how to make an instance of a user created 

>> external. I just have a [loadbang] -> [message] -> [thispatcher] with 

>> the following in the message box: script new user myobject 318 192 15 

>> 200 128 1 0 12...bunch of other crap; This doesn't seem to work, I 

>> get the message; "patcher: doesn't understand myobject".

>> Help with this issue is also appreciated.

>> Today, Noise is triumphant and reigns sovereign over the sensibility 

Today, Noise is triumphant and reigns sovereign over the sensibility of men.

Thanks, the scripting works.  In fact, the object instantiates correctly 
when called via Max scripting.  The crash only occurs when the object is 
instantiated from a object box.

I'll look into the null argument possibility.  It sounds very promising. 
   I'm not so good at this graphical Max object thing yet....

Jeremy Bernstein wrote:
> You want "script new  user myobject blah blah blah", i believe.
>
> As for your development problem, I would look at the object's menu 
> function or the way that you're processing args to the object, since it 
> sounds like you may be passing bad/NULL/not enough/too much into the new 
> method from the menu method.
>
> jb
>
> Am 13.03.2007 um 04:38 schrieb Barry Threw:
>
>> Oh Oracle!
>>
>> I am developing a graphical Max object, and am having problems.  The 
>> major issue is that my object crashes Max on instantiation.  However, 
>> if there is already an instance of this object in a patch (i.e. you 
>> open a patch with the object in it), it loads correctly.  You can make 
>> copies of the object in the normal option-drag manner, and they work 
>> correctly.
>>
>> If anyone has had this kind of issue, and knows some troubleshooting 
>> steps to solve it, advice would be appriciated.
>>
>> Sub Issue:
>>
>> To debug said object automatically from XCode, I must use Max Runtime 
>> as my executable.  Because my object only crashes Max on 
>> instantiation, not from an object already loaded in patcher, I suppose 
>> I must create a new instance of my object via Max Scripting.  I can't 
>> seem to figure out how to make an instance of a user created 
>> external.  I just have a [loadbang] -> [message] -> [thispatcher] with 
>> the following in the message box: script new user myobject 318 192 15 
>> 200 128 1 0 12...bunch of other crap;  This doesn't seem to work, I 
>> get the message; "patcher: doesn't understand myobject".
>>
>> Help with this issue is also appreciated.
>>
>> Thanks,
>>
>> barry
>>
>> --barry threw
>> composition : sound : programming
>> http://www.barrythrew.com bthrew(at)gmail(dot)com
>> 857-544-3967
>>
>> Today, Noise is triumphant and reigns sovereign over the sensibility 
>> of men.   
>> - Luigi Russolo, The Art of Noises
>>
>
>

-- 
barry threw
composition : sound : programming
http://www.barrythrew.com
bthrew(at)gmail(dot)com
857-544-3967

Today, Noise is triumphant and reigns sovereign over the sensibility of men.
- Luigi Russolo, The Art of Noises


it's very simple. you have to have *ALL* non JS graphical objects in the Cycling '74/Max-Startup folder. It must reside in the max bar or it'll cause an error when you type the name in.

Try moving toggle.mxe to the externals folder, starting max and typing toggle into an object box, you'll get the same error.

it's very simple. you have to have *ALL* non JS graphical objects in the Cycling '74/Max-Startup folder.  It must reside in the max bar or it'll cause an error when you type the name in.  

Try moving toggle.mxe to the externals folder, starting max and typing toggle into an object box, you'll get the same error.


Hate to break it to you, but my object is in the max-startup folder.

> it's very simple. you have to have *ALL* non JS graphical objects in the Cycling '74/Max-Startup folder. It must reside in the max bar or it'll cause an error when you type the name in. 

> Try moving toggle.mxe to the externals folder, starting max and typing toggle into an object box, you'll get the same error.

jamez wrote:
> *ANSWER*
>
> it's very simple. you have to have *ALL* non JS graphical objects in the Cycling '74/Max-Startup folder.  It must reside in the max bar or it'll cause an error when you type the name in.  
>
> Try moving toggle.mxe to the externals folder, starting max and typing toggle into an object box, you'll get the same error.
>

debugging / loading a custom max object via scripting