benniy

i'm currently working on a rather big patch (

https://www.youtube.com/watch?v=xTgSgTGoBLc)

and i'm suspecting quite some cpu load. i'm no whizz when it comes to processes "inside" of

a computer, but anyhow i can't really explain because my patch is not using any DSP.

> visual elements such as bpatchers (i use for submenus) stop reacting to hide/show effects

> little knobs (handles) from my patchchords occasionally disappear / are not selectable

i am using plugsync~ to calculate different clocks for my sequencer (link above).

i don't know if this is the most elegant route to go or if it may be part of the problem,

is there any rule of thumb; a list of objects that are very cpu intense or ways to check

for them? any other tips as for cpu-load reduction?

edit: i should say that ableton live only shows ~5% of cpu usage when the device is active. can therefore even less explain all the flaws and lacks i get.

i'm currently working on a rather big patch (https://www.youtube.com/watch?v=xTgSgTGoBLc)
and i'm suspecting quite some cpu load. i'm no whizz when it comes to processes "inside" of
a computer, but anyhow i can't really explain because my patch is not using any DSP.

some symptoms:
> visual elements such as bpatchers (i use for submenus) stop reacting to hide/show effects
> max + live lock up
> little knobs (handles) from my patchchords occasionally disappear / are not selectable
> print-objects don't output anymore
... i could go on

as a quick side-info:
i am using plugsync~ to calculate different clocks for my sequencer (link above).
i don't know if this is the most elegant route to go or if it may be part of the problem,
although i can't really imagine.

is there any rule of thumb; a list of objects that are very cpu intense or ways to check
for them? any other tips as for cpu-load reduction? 

edit: i should say that ableton live only shows ~5% of cpu usage when the device is active. can therefore even less explain all the flaws and lacks i get.


max / m4l cpu problems