bkshepard

Is there a way to launch Max/MSP with the scheduler turned off or in some kind of "safe" mode. I've got a patcher that has a recursive connection that causes a stack overflow as soon as I try to open the file. I know exactly where the connection is, but I can't get the file to open. As soon as I attempt to launch the file, I get the Stack Overflow message with the instructions to resume the scheduler under the edit menu. The warning message has an okay box that as soon as I click causes Max/MSP to crash.

I've tried opening the patcher in text mode which I can do. I can find the object that has the "illegal" patch cord, but I'm not sure how to find the actual patch cord. If I delete the object, the patcher will then open, but it all the other patch cords in the patcher are wrong.

Is there a way to launch Max/MSP with the scheduler turned off or in some kind of "safe" mode.  I've got a patcher that has a recursive connection that causes a stack overflow as soon as I try to open the file.  I know exactly where the connection is, but I can't get the file to open.  As soon as I attempt to launch the file, I get the Stack Overflow message with the instructions to resume the scheduler under the edit menu.  The warning message has an okay box that as soon as I click causes Max/MSP to crash.

I've tried opening the patcher in text mode which I can do.  I can find the object that has the "illegal" patch cord, but I'm not sure how to find the actual patch cord.  If I delete the object, the patcher will then open, but it all the other patch cords in the patcher are wrong.

launch-maxmsp-in-safe-mode

On 24 avr. 07, at 18:31, Brian Shepard wrote:

> Is there a way to launch Max/MSP with the scheduler turned off or 

> in some kind of "safe" mode. I've got a patcher that has a 

> recursive connection that causes a stack overflow as soon as I try 

> to open the file. I know exactly where the connection is, but I 

> can't get the file to open. As soon as I attempt to launch the 

> file, I get the Stack Overflow message with the instructions to 

> resume the scheduler under the edit menu. The warning message has 

> an okay box that as soon as I click causes Max/MSP to crash.

> I've tried opening the patcher in text mode which I can do. I can 

> find the object that has the "illegal" patch cord, but I'm not sure 

> how to find the actual patch cord. If I delete the object, the 

> patcher will then open, but it all the other patch cords in the 

You can disable the loadbang by pressing command+shift while opening 

> Is there a way to launch Max/MSP with the scheduler turned off or  
> in some kind of "safe" mode.  I've got a patcher that has a  
> recursive connection that causes a stack overflow as soon as I try  
> to open the file.  I know exactly where the connection is, but I  
> can't get the file to open.  As soon as I attempt to launch the  
> file, I get the Stack Overflow message with the instructions to  
> resume the scheduler under the edit menu.  The warning message has  
> an okay box that as soon as I click causes Max/MSP to crash.
>
> I've tried opening the patcher in text mode which I can do.  I can  
> find the object that has the "illegal" patch cord, but I'm not sure  
> how to find the actual patch cord.  If I delete the object, the  
> patcher will then open, but it all the other patch cords in the  
> patcher are wrong.
>
> Any hints?  Thanks.

You can disable the loadbang by pressing command+shift while opening  
the patch.

Quote: Emmanuel Jourdan wrote on Tue, 24 April 2007 10:21

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

> You can disable the loadbang by pressing command+shift while opening 

That's great to know, thanks. Actually, I realized that if I first opened Max/MSP and enabled Trace mode it allowed me to open the patcher, delete the offending patch cable and the resave the patcher. It all works fine now. I learned two really helpful tips today! (well, three if you count the fact that I was reminded about recursive connections!)

Quote: Emmanuel Jourdan wrote on Tue, 24 April 2007 10:21
----------------------------------------------------
>
> You can disable the loadbang by pressing command+shift while opening  
> the patch.
>
> ej
>
----------------------------------------------------

That's great to know, thanks.  Actually, I realized that if I first opened Max/MSP and enabled Trace mode it allowed me to open the patcher, delete the offending patch cable and the resave the patcher.  It all works fine now.  I learned two really helpful tips today! (well, three if you count the fact that I was reminded about recursive connections!)


> I can find the object that has the "illegal" patch cord, but I'm not

> sure how to find the actual patch cord. If I delete the object, the 

you can rename the object to something non existent. For example if its 

a metro object rename it to metrop. This will then not be found and a 

bogus object with all the connection is in place. Change the 

connections, rename the object back to its original and you're done...

(Just in case disabling the loadbangs didn't work)

Brian Shepard schrieb:
> I can find the object that has the "illegal" patch cord, but I'm not
> sure how to find the actual patch cord.  If I delete the object, the 
> patcher will then open, but it all the other patch cords in the 
> patcher are wrong.

you can rename the object to something non existent. For example if its 
a metro object rename it to metrop. This will then not be found and a 
bogus object with all the connection is in place. Change the 
connections, rename the object back to its original and you're done...

-- 
Stefan Tiedje------------x-------
--_____-----------|--------------
--(_|_ ----|-----|-----()-------
-- _|_)----|-----()--------------
----------()--------www.ccmix.com


Quote: Stefan Tiedje wrote on Wed, 25 April 2007 03:41

> you can rename the object to something non existent. For example if its 

> a metro object rename it to metrop. This will then not be found and a 

> bogus object with all the connection is in place. Change the 

> connections, rename the object back to its original and you're done...

If I rename an object with a bogus name, wouldn't that delete all the inlets and outlets on the object, and thus, the patch connections?

Quote: Stefan Tiedje wrote on Wed, 25 April 2007 03:41
----------------------------------------------------

> you can rename the object to something non existent. For example if its 
> a metro object rename it to metrop. This will then not be found and a 
> bogus object with all the connection is in place. Change the 
> connections, rename the object back to its original and you're done...

If I rename an object with a bogus name, wouldn't that delete all the inlets and outlets on the object, and thus, the patch connections?


you can create your object (myobject) with x inputs and x outputs, soon rename the controversial object with this new object (myobject)

> > you can rename the object to something non existent. For example if its 

> > a metro object rename it to metrop. This will then not be found and a 

> > bogus object with all the connection is in place. Change the 

> > connections, rename the object back to its original and you're done...

> If I rename an object with a bogus name, wouldn't that delete all the inlets and outlets on the object, and thus, the patch connections?

>
> > you can rename the object to something non existent. For example if its 
> > a metro object rename it to metrop. This will then not be found and a 
> > bogus object with all the connection is in place. Change the 
> > connections, rename the object back to its original and you're done...
>
> If I rename an object with a bogus name, wouldn't that delete all the inlets and outlets on the object, and thus, the patch connections?
>
>
----------------------------------------------------


not if you change it's name in text source:

On Apr 25, 2007, at 9:19 PM, Brian Shepard wrote:

> If I rename an object with a bogus name, wouldn't that delete all 

> the inlets and outlets on the object, and thus, the patch connections?

> If I rename an object with a bogus name, wouldn't that delete all  
> the inlets and outlets on the object, and thus, the patch connections?


> If I rename an object with a bogus name, wouldn't that delete all the 

inlets and outlets on the object, and thus, the patch connections?

It's nice to have an abstraction with just a load of inlets and outlets 

Brian Shepard wrote:
 > If I rename an object with a bogus name, wouldn't that delete all the 
inlets and outlets on the object, and thus, the patch connections?

It's nice to have an abstraction with just a load of inlets and outlets 
for this purpose.

That's pretty cool. I had just assumed (yeah, I know what they say) that creating a bogus object in text mode would do the same thing as in binary mode. Thanks for the tips everyone.

I will also say, though, that enabling Trace before opening the patch worked fabulously for my aforementioned problem since the offending patch cord was way down in the process. It kept the scheduler on the first task, allowing me to delete the cord and save and reopen the patcher without having to even go into text mode.

That's pretty cool.  I had just assumed (yeah, I know what they say) that creating a bogus object in text mode would do the same thing as in binary mode.  Thanks for the tips everyone.

I will also say, though, that enabling Trace before opening the patch worked fabulously for my aforementioned problem since the offending patch cord was way down in the process.  It kept the scheduler on the first task, allowing me to delete the cord and save and reopen the patcher without having to even go into text mode.

> If I rename an object with a bogus name, wouldn't that delete all the

> inlets and outlets on the object, and thus, the patch connections?

The bogus object wouldn't make sense if it had no ins and outs. Try it 

I've done it a million times, it works....

Brian Shepard schrieb:
> If I rename an object with a bogus name, wouldn't that delete all the
> inlets and outlets on the object, and thus, the patch connections?

The bogus object wouldn't make sense if it had no ins and outs. Try it 
I've done it a million times, it works....

Quote: Stefan Tiedje wrote on Wed, 25 April 2007 15:39

> I've done it a million times, it works....

Quote: Stefan Tiedje wrote on Wed, 25 April 2007 15:39
----------------------------------------------------
> Try it 
> I've done it a million times, it works....
>
> Stefan
>

Launch Max/MSP in "Safe" mode