Friday, October 06, 2006

crash and burn

i've created a monster. there is some error in a patch i've spent hours on and now there is an error message everytime as soon as i open the patch. then max crashes. the error message says "stack overload select resume from the edit menu to the scheduler". it seems like the same problem happens if you (for example) try to use a patch with a int object's left outlet linked to an int left inlet then that left outlet linked into the first one's left inlet.
so i get that you can't do that, but now it seems like there is one locked in my patch and i think it may be triggered with a loadbang. so as soon as i open it: error message then max crashes.
is there anyway i can change my patch outside of max or can i disable a loadbang without opening the patch. i am pretty sure the answer is no and i just wasted a fw hours, but any insight would be helpful.


Blogger J Bunch said...

try pressing shift+command as the patch is loading. that is supposed to prevent loadmess from sending its info. I am not sure if it works with loadbang, but it's one thing you could try.

3:30 AM, October 06, 2006  
Blogger Steve Taylor said...

Try opening your patch as a text file, with the "Open as text..." command under the file menu. Then, look for the offending loadbang message (there will be a ton of short text lines). Try deleting the loadbang line, and then opening the patch again in the regular way.

If you're having trouble opening it the regular way after you look at its text, then select all the text, copy it (command-C) and select "New from clipboard" from the File menu. Hope this helps...

7:42 AM, October 06, 2006  
Blogger vincent murphy said...

thanks guys,
unfortunately, that did not solve my problem. so maybe it's not the loadbang. i assume the next step is to either analyze the patch as text to find the problem (or give up) right?

10:45 AM, October 06, 2006  
Blogger Steve Taylor said...

It's pretty tough to analyze Max patches even when they're not textfiles! What I usually do is Save As when I'm about to make a change that might wreck the patch, and give it a new name.

It sounds like you've made a kind of recursive, infinite loop. In one of the pdf documentation files (I think it's Tutorials and Topics) there's a chapter on debugging, which everyone should read. There are some tracing tools etc. in Max; if you turn those on before opening your monster, it might make your patch go slowly enough that it doesn't get caught in the loop (or whatever it is) right when it opens. Good luck...

10:52 AM, October 06, 2006  

Post a Comment

Links to this post:

Create a Link

<< Home