darkflow

I try to avoid asking for help, instead trying to figure stuff out for myself (which is why this is my first post on this website and I've been using max since September) but it has become increasingly annoying that Max keeps crashing more frequently. Now it has got to the point that when I work on my current patch (which is essentially the main portion of my uni degree) it will crash after placing 4 or 5 object boxes down, or opening or closing a few windows. So I'm saving every 20 seconds. It simply unexpectedly quits.

I'm running Max/MSP 4.6.3 (which to the best of my knowledge is the latest) on:

I am also using the Make Controller and one hi object to a very small extent at slow poll/data speeds in my patch.

My patch is 1000% debugged (I have been working on it for months!). There is nothing in my patch that would cause problems and I've gone over it many times.

The patch uses around 65% CPU and less than 200MB of memory. If I copy the Max code to the clipboard it is 2634 lines long. Is this abnormally large? I'm under the impression it's nothing ridiculous.

1. Isn't Max meant to be rock solid - eg could it actually be my patch? Although I would bet my telecaster it's not.

2. Is max 5 (which I think I'm getting a free upgrade to) going to be more stable if 4 isn't that stable?

3. Should I consider fundamentally changing a 2634 object worth patch to try and stop max crashing 1 week before I am exhibiting it?

I suppose it's a more of "what would someone else do in my shoes" post.

Thank you for your time everybody who reads this,

Hi all,
I try to avoid asking for help, instead trying to figure stuff out for myself (which is why this is my first post on this website and I've been using max since September) but it has become increasingly annoying that Max keeps crashing more frequently. Now it has got to the point that when I work on my current patch (which is essentially the main portion of my uni degree) it will crash after placing 4 or 5 object boxes down, or opening or closing a few windows. So I'm saving every 20 seconds. It simply unexpectedly quits.

Intel 2GHz x2 (Quadcore)
667MHz 2GB RAM
1330MHz FSB etc

So what I am asking really is,
1. Isn't Max meant to be rock solid - eg could it actually be my patch? Although I would bet my telecaster it's not.
2. Is max 5 (which I think I'm getting a free upgrade to) going to be more stable if 4 isn't that stable?
3. Should I consider fundamentally changing a 2634 object worth patch to try and stop max crashing 1 week before I am exhibiting it?

Thank you for your time everybody who reads this,
D


persistent-instability-in-latest-public

Ok, 65% CPU wtf I thought that was a bit high, so i started ripping chunks of patch out.... Then I narrowed it down and deleted the one single mc.usb object that is in the entire thing and my cpu dropped to 8%!! Really sorry guys, I think that was the problem, I'm going to do some further testing now - just thought i'd reply asap so nobody writes back for no reason...

sorry again, but it looks like I may need help with the make controller if this is the right place if i cant get it working other ways, ill try osc etc.

I do apologize for being so hasty posting this topic without checking out what I only just found out - I think writing something on a forum just clarifies your situation somewhat so it was probably necessary anyway for me, but for those who have bothered to read this topic now and for everyone out there with a Make Controller kit please listen to my newly discovered primary rule of Max/Make land:

"IF YOU SEND DATA TO MC.USB OBJECT WITHOUT THE ACTUALLY MC PLUGGED IN YOUR WORLD WILL TURN TO SHIT"

or alternatively put, the mc.usb external will turn your shiny new mac into a mung bean if the controller isn't plugged in.

or put another way, why did I pay so much for a piece of shit with such a poorly written external.

Anyway, to bed i go now,
Sorry for posting crap,
D


That's good to know about cpu usage when not plugged in. I have a make controller too, but lately find myself futzing around with the arduino (it was only $25 vs. $149, but haven't made it talk to Max yet.

How are you using the make controller with max? I'm building a modular synth (paia9700s) that I can hopefully control with Max through control voltages through an i/o board (not midi). Thus, my small collection of controller boards.

I've been roughly successful getting theremin CV/gate data into a make board and into Max, much more work to go on that project.

If you don't mind coding, you might want to take a look at the arduino too. It's cheap and may do what you need.

That's good to know about cpu usage when not plugged in.  I have a make controller too, but lately find myself futzing around with the arduino (it was only $25 vs. $149, but haven't made it talk to Max yet.

How are you using the make controller with max?  I'm building a modular synth (paia9700s) that I can hopefully control with Max through control voltages through an i/o board (not midi).  Thus, my small collection of controller boards.

If you don't mind coding, you might want to take a look at the arduino too. It's cheap and may do what you need.


WELL, you made me laugh! :) good to know!

On Jan 2, 2008, at 10:49 PM, darkflow wrote:

> "IF YOU SEND DATA TO MC.USB OBJECT WITHOUT THE ACTUALLY MC PLUGGED 

>
> "IF YOU SEND DATA TO MC.USB OBJECT WITHOUT THE ACTUALLY MC PLUGGED  
> IN YOUR WORLD WILL TURN TO SHIT"
>


I'll have to check that cheaper one out... unfortunately my programming skills are rubbish - I'm only good at VB, very basic C++ and your standard web stuff meaning that my last attempt at writing an external ended in me wanting to leave england and become a Tibetan Yak farmer instead.

As for my project and the make controller, its a bit lame at the minute, I've just got it controlling some LEDs. But when I said about it not being plugged in, I've looked and it doesn't just use a lot more CPU (65%... 3D rendering uses less on my machine) it also accumulates memory usage, like all the commands are being placed in one ridiculously humongous queue (I mean it got to like 2 gig in 20 mins!) and that is completely responsible for all the crashes I've been having. I've been using max again now for about an hour without that one mc.usb in my patch and it hasn't crashed once!

The whole CV -> computer concept with the make controller is actually a really cool one, especially because I have an analogue systems synth sitting next to me, it would be very cool to extend it digitally but using the analogue OSCs etc - I've just been so immersed in this project, my only perceived possible function of the make controller so far has been for the project.

If I don't get a good mark I'm going to be horribly disappointed.

But anyway dude I wish you well with your CV/synth patch.

Now I'm actually going to go bed before I wake up in the dark again (which I find totally rubbish).

> That's good to know about cpu usage when not plugged in. I have a make controller too, but lately find myself futzing around with the arduino (it was only $25 vs. $149, but haven't made it talk to Max yet.

http://www.maxobjects.com/?request=arduino

> That's good to know about cpu usage when not plugged in.  I have a make controller too, but lately find myself futzing around with the arduino (it was only $25 vs. $149, but haven't made it talk to Max yet.

Persistent instability in latest public