woodslanding

My cpu usage is 23% without any audio. I'm assuming I have something wildly inefficient in my patch (which IS huge, but has been fine until recently.) I'm not using any jitter objects, just regular max. And very little audio yet (and it's turned off anyway!) just a rather complex gui. When I'm patching, the UI freezes for 1-2 seconds every 5-10 seconds. Very frustrating!

Any clues on where to start tracking down CPU hogging? I'll read the chapter on debugging for starters ;)

Also, is there anyway to display NON-cpu usage in a max patch? I'm seeing a 0 from adstatus.....

My cpu usage is 23% without any audio.  I'm assuming I have something wildly inefficient in my patch (which IS huge, but has been fine until recently.)  I'm not using any jitter objects, just regular max.  And very little audio yet (and it's turned off anyway!) just a rather complex gui.  When I'm patching, the UI freezes for 1-2 seconds every 5-10 seconds.  Very frustrating!

Any clues on where to start tracking down CPU hogging?   I'll read the chapter on debugging for starters ;)

Also, is there anyway to display NON-cpu usage in a max patch?  I'm seeing a 0 from adstatus.....

max-ui-is-suddenly-overloaded

Okay, I unzipped my project backup from several days ago (when the UI was 98% as complicated as it is now) and CPU is running under 1%. So something is definitely wrong!

I read up on debugging, but in a project with 100 or so abstractions, it's difficult to know where to start putting watchpoints.

With Usine, I could get cpu numbers on each patch in a project. Is there some way to do this in Max?

BTW: I am running win 8.1 64 bit if it matters.

Okay, I unzipped my project backup from several days ago (when the UI was 98% as complicated as it is now) and CPU is running under 1%.  So something is definitely wrong!

With Usine, I could get cpu numbers on each patch in a project.  Is there some way to do this in Max?

BTW:  I am running win 8.1 64 bit if it matters.


Well, here's what I did, in hopes it helps somebody else in the same position. I unzipped both my old and new project trees, and moved files from the disfunctional tree to the older-but- functional one. Starting with the least likely candidates, I got 90% of my work back, and eventually narrowed it down to a single patch. I have no idea what made it go haywire, but I'll keep an eye on it as I work with it in future.

Well, here's what I did, in hopes it helps somebody else in the same position.  I unzipped both my old and new project trees, and moved files from the disfunctional tree to the older-but- functional one.  Starting with the least likely candidates, I got 90% of my work back, and eventually narrowed it down to a single patch.  I have no idea what made it go haywire, but I'll keep an eye on it as I work with it in future.

Max UI is suddenly overloaded