max5: waveform~ = cpu hog? what happened to buftime message?

Apr 27, 2008 at 9:37am

max5: waveform~ = cpu hog? what happened to buftime message?

i haven’t done a lot of cpu util. comparison between 4 and 5 so far,
but this one really seems ridiculous.
while trying out an old max4 patch (that uses a bunch of waveform~
objects) in max5 i noticed that my computer started melting pretty
soon :(

running the attached test patch on my computer ( ppc pb g4, 1.5GHz,
os 10.4.11) i got the following results:
max4
cpu: 0%
processor load (activity monitor or top): 30 – 35%

max 5:
cpu: 2%
processor load: 75 – 85%, with occasional spikes to over 90%

while i know that waveform~ always seemed to draw a lot of power,
there was the (undocumented) buftime message, which made the decision
between update rate and cpu util. somewhat manageable.
unfortunately this message doesn’t work in max5 (max is not
complaining about unknown message, but doesn’t change the update rate
of waveform~ either).

any comments?

thanks,
volker.

#P window setfont “Sans Serif” 9.;
#P number 633 27 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
#P window linecount 1;
#P newex 633 71 30 196617 s wf;
#P toggle 706 304 30 0;
#P hidden newex 418 729 30 196617 r wf;
#P toggle 574 685 15 0;
#P newex 526 683 45 196617 rand~ 8;
#P message 540 713 56 196617 $1 , loop 1;
#P newex 526 733 54 196617 record~ g;
#P newex 402 707 73 196617 buffer~ g 500;
#P message 402 659 32 196617 set g;
#P user waveform~ 40 659 364 101 3 9;
#W mode select;
#W mouseoutput none;
#W clipdraw 1;
#W unit samples;
#W grid 22.675737;
#W ticks 0;
#W labels 1;
#W vlabels 0;
#W vticks 0;
#W bpm 120. 4.;
#W frgb 33 0 0;
#W brgb 60 178 173;
#W rgb2 0 95 255;
#W rgb3 0 0 0;
#W rgb4 0 0 0;
#W rgb5 146 179 217;
#W rgb6 100 100 100;
#W rgb7 100 100 100;
#P hidden newex 418 626 30 196617 r wf;
#P toggle 574 582 15 0;
#P newex 526 580 45 196617 rand~ 8;
#P message 540 610 56 196617 $1 , loop 1;
#P newex 526 630 53 196617 record~ f;
#P newex 402 604 72 196617 buffer~ f 500;
#P message 402 556 31 196617 set f;
#P user waveform~ 40 556 364 101 3 9;
#W mode select;
#W mouseoutput none;
#W clipdraw 1;
#W unit samples;
#W grid 22.675737;
#W ticks 0;
#W labels 1;
#W vlabels 0;
#W vticks 0;
#W bpm 120. 4.;
#W frgb 33 0 0;
#W brgb 60 178 173;
#W rgb2 0 95 255;
#W rgb3 0 0 0;
#W rgb4 0 0 0;
#W rgb5 146 179 217;
#W rgb6 100 100 100;
#W rgb7 100 100 100;
#P hidden newex 418 523 30 196617 r wf;
#P toggle 574 479 15 0;
#P newex 526 477 45 196617 rand~ 8;
#P message 540 507 56 196617 $1 , loop 1;
#P newex 526 527 54 196617 record~ e;
#P newex 402 501 73 196617 buffer~ e 500;
#P message 402 453 32 196617 set e;
#P user waveform~ 40 453 364 101 3 9;
#W mode select;
#W mouseoutput none;
#W clipdraw 1;
#W unit samples;
#W grid 22.675737;
#W ticks 0;
#W labels 1;
#W vlabels 0;
#W vticks 0;
#W bpm 120. 4.;
#W frgb 33 0 0;
#W brgb 60 178 173;
#W rgb2 0 95 255;
#W rgb3 0 0 0;
#W rgb4 0 0 0;
#W rgb5 146 179 217;
#W rgb6 100 100 100;
#W rgb7 100 100 100;
#P hidden newex 418 420 30 196617 r wf;
#P toggle 574 376 15 0;
#P newex 526 374 45 196617 rand~ 8;
#P message 540 404 56 196617 $1 , loop 1;
#P newex 526 424 54 196617 record~ d;
#P newex 402 398 73 196617 buffer~ d 500;
#P message 402 350 32 196617 set d;
#P user waveform~ 40 350 364 101 3 9;
#W mode select;
#W mouseoutput none;
#W clipdraw 1;
#W unit samples;
#W grid 22.675737;
#W ticks 0;
#W labels 1;
#W vlabels 0;
#W vticks 0;
#W bpm 120. 4.;
#W frgb 33 0 0;
#W brgb 60 178 173;
#W rgb2 0 95 255;
#W rgb3 0 0 0;
#W rgb4 0 0 0;
#W rgb5 146 179 217;
#W rgb6 100 100 100;
#W rgb7 100 100 100;
#P hidden newex 418 317 30 196617 r wf;
#P toggle 574 273 15 0;
#P newex 526 271 45 196617 rand~ 8;
#P message 540 301 56 196617 $1 , loop 1;
#P newex 526 321 54 196617 record~ c;
#P newex 402 295 73 196617 buffer~ c 500;
#P message 402 247 32 196617 set c;
#P user waveform~ 40 247 364 101 3 9;
#W mode select;
#W mouseoutput none;
#W clipdraw 1;
#W unit samples;
#W grid 22.675737;
#W ticks 0;
#W labels 1;
#W vlabels 0;
#W vticks 0;
#W bpm 120. 4.;
#W frgb 33 0 0;
#W brgb 60 178 173;
#W rgb2 0 95 255;
#W rgb3 0 0 0;
#W rgb4 0 0 0;
#W rgb5 146 179 217;
#W rgb6 100 100 100;
#W rgb7 100 100 100;
#P hidden newex 418 214 30 196617 r wf;
#P toggle 574 170 15 0;
#P newex 526 168 45 196617 rand~ 8;
#P message 540 198 56 196617 $1 , loop 1;
#P newex 526 218 54 196617 record~ b;
#P newex 402 192 73 196617 buffer~ b 500;
#P message 402 144 32 196617 set b;
#P user waveform~ 40 144 364 101 3 9;
#W mode select;
#W mouseoutput none;
#W clipdraw 1;
#W unit samples;
#W grid 22.675737;
#W ticks 0;
#W labels 1;
#W vlabels 0;
#W vticks 0;
#W bpm 120. 4.;
#W frgb 33 0 0;
#W brgb 60 178 173;
#W rgb2 0 95 255;
#W rgb3 0 0 0;
#W rgb4 0 0 0;
#W rgb5 146 179 217;
#W rgb6 100 100 100;
#W rgb7 100 100 100;
#P hidden newex 418 111 30 196617 r wf;
#P message 633 49 59 196617 buftime $1;
#P flonum 696 166 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
#P toggle 696 101 15 0;
#P newex 696 119 52 196617 metro 50;
#P newex 696 142 66 196617 adstatus cpu;
#P user ezdac~ 744 65 788 98 0;
#P toggle 574 67 15 0;
#P newex 526 65 45 196617 rand~ 8;
#P message 540 95 56 196617 $1 , loop 1;
#P newex 526 115 54 196617 record~ a;
#P hidden newex 464 37 48 196617 loadbang;
#P newex 402 89 73 196617 buffer~ a 500;
#P message 402 41 32 196617 set a;
#P user waveform~ 40 41 364 101 3 9;
#W mode select;
#W mouseoutput none;
#W clipdraw 1;
#W unit samples;
#W grid 22.675737;
#W ticks 0;
#W labels 1;
#W vlabels 0;
#W vticks 0;
#W bpm 120. 4.;
#W frgb 33 0 0;
#W brgb 60 178 173;
#W rgb2 0 95 255;
#W rgb3 0 0 0;
#W rgb4 0 0 0;
#W rgb5 146 179 217;
#W rgb6 100 100 100;
#W rgb7 100 100 100;
#P hidden connect 3 0 1 0;
#P hidden connect 3 0 16 0;
#P hidden connect 3 0 24 0;
#P hidden connect 3 0 32 0;
#P hidden connect 3 0 40 0;
#P hidden connect 3 0 48 0;
#P hidden connect 3 0 56 0;
#P hidden connect 3 0 11 0;
#P hidden connect 3 0 63 0;
#P connect 9 0 12 0;
#P connect 10 0 9 0;
#P connect 11 0 10 0;
#P connect 13 0 64 0;
#P connect 65 0 13 0;
#P connect 63 0 61 0;
#P connect 63 0 53 0;
#P connect 63 0 45 0;
#P connect 63 0 37 0;
#P connect 63 0 29 0;
#P connect 63 0 21 0;
#P connect 63 0 7 0;
#P connect 61 0 59 0;
#P connect 53 0 51 0;
#P connect 45 0 43 0;
#P connect 37 0 35 0;
#P connect 29 0 27 0;
#P connect 21 0 19 0;
#P connect 7 0 5 0;
#P connect 59 0 58 0;
#P connect 60 0 58 0;
#P connect 52 0 50 0;
#P connect 51 0 50 0;
#P connect 43 0 42 0;
#P connect 44 0 42 0;
#P connect 36 0 34 0;
#P connect 35 0 34 0;
#P connect 27 0 26 0;
#P connect 28 0 26 0;
#P connect 20 0 18 0;
#P connect 19 0 18 0;
#P connect 5 0 4 0;
#P connect 6 0 4 0;
#P hidden connect 62 0 55 0;
#P hidden connect 56 0 55 0;
#P hidden connect 48 0 47 0;
#P hidden connect 54 0 47 0;
#P hidden connect 46 0 39 0;
#P hidden connect 40 0 39 0;
#P hidden connect 32 0 31 0;
#P hidden connect 38 0 31 0;
#P hidden connect 30 0 23 0;
#P hidden connect 24 0 23 0;
#P hidden connect 16 0 15 0;
#P hidden connect 22 0 15 0;
#P hidden connect 14 0 0 0;
#P hidden connect 1 0 0 0;
#P window clipboard copycount 66;

#37290
Apr 27, 2008 at 2:47pm

#128788
Apr 28, 2008 at 9:08am

On 27 Apr 2008, at 16:47, Klaas-Jan Govaart wrote:
>>
>> running the attached test patch on my computer ( ppc pb g4, 1.5GHz,
>> os 10.4.11) i got the following results:
>> max4
>> cpu: 0%
>> processor load (activity monitor or top): 30 – 35%
>>
>> max 5:
>> cpu: 2%
>> processor load: 75 – 85%, with occasional spikes to over 90%
>>
>
> 10.4.11, mbp 2.16GHz:
>
> max 4 cpu 0%, activity monitor 19%
> max 5 cpu 1-2%, activity monitor 83-88%

thanks for testing, klaas.

any other takers?
is someone from cycling looking into it?

something definitely IS going wrong.

#128789

m
Apr 28, 2008 at 10:23am

#128790
Apr 28, 2008 at 10:56am

#128791
Apr 29, 2008 at 8:14am

#128792
Oct 15, 2008 at 1:33pm

Hello,

Any news on this front? Has waveform~’s cpu usage gone down after any of the updates? Or is it like the multislider cpu issue – Inherent to JUCE engine, and not improving anytime soon?

Any thoughts appreciated.
kjg

#128793
Oct 15, 2008 at 1:53pm

On 15 Oct 2008, at 15:33, Klaas-Jan Govaart wrote:
>
> Hello,
>
> Any news on this front? Has waveform~’s cpu usage gone down after
> any of the updates? Or is it like the multislider cpu issue –
> Inherent to JUCE engine, and not improving anytime soon?
>
> Any thoughts appreciated.
> kjg

the buftime message is back since 5.0.5 (maybe earlier), which makes
the update rate of [waveform~] manageable again.
i haven’t made any direct comparisons between 4.6 and 5.0.5, yet, but
the default setting of 500 ms seems to give reasonable cpu measures
on my system using max 5.
volker.

#128794
Oct 15, 2008 at 2:29pm

#128795

You must be logged in to reply to this topic.