What happened to max 9 ??

ward de jager's icon

I am just playing with demo of max 9 and what happened ?

It's has become a real cpu hog ( shown in win dows taskmamanger ) , constantly in the red
Here' I am doing a very basic phase distortion patch , using function /shape~ and some lists for sequencing .
Scheduler to overdrive , it has a constant cpu of 40%

Recreated the patch in Pure data (plug data ) 100 % , barely hits the 2% cpu mark .




Joshua Kit Clayton's icon

There are a few things that might be hidden for taking up CPU.

First is that there is a new preference in Max 9, default on, "Prioritize Scheduler Accuracy over CPU usage" which will use some extra cycles to more accurately run the high priority scheduler when in overdrive (but not scheduler in audio interrupt). Try turning this off to see if it is the culprit for you.

Second, if you've enabled Debug -> Event Probe, then extra allocations for every message sent through every patchcord will take place. Depending on the patch this could be measurable or negligible. If Event Prove is enabled, try turning it off.

Otherwise, if you share a patch and your support info dict, we can offer more insight, than just from the screenshots.

ward de jager's icon

Debug was off and prioritize scheduler is on because I need it to be as accurate as possible .

Can't share patches because I'm running the demo