< Back to IRCAM Forum

MuBu and M4L cpu load

MuBu
#1

Hi all,

I recently created a device in M4L using a patch that I had previously used with success in max 6.0.8 (It uses several externals: imubu, mubu, mubu.knn, mubu.track, mubu.process and pipo modules …).

But I have noticed that during use the CPU load often jumps abruptly to very high values (40% - 70%), obviously causing clicks and not allowing the application to work well.

As mentioned previously I had no particular problem using the same patch in max 6.0.8, so I do not know if it is a known bug of MuBu externals or is it a problem due to my system configuration (OSX 10.8.2 / Max 6.0 .8 - MuBu 1.6.4 / Live 8.4).

Anyway I hope that for the next release also this “problem” is taken into account …

As always, thanks for your work.

greetings

pjeve

#2

Hi,

Can you tell us a little bit more about the patch?

N.

P.S.: A wild guess of what may happen here would be that the computation peaks are due to the synthesis of long grains with mubu.granular~ or mubu.concat~. Note that these externals synthesize a grain or segment entirely right when it is triggered. Long grains may cause CPU usage peaks depending on Max’ i/o buffer. The percentage of CPU load is calculated as the time spent calculating within a given period. If this period (corresponding to the i/o buffer) is shorter, punctual calculations may appear heavier. The only remedy here would be to shorten your grains/segments.