Masa

Somehow my Max patch's CPU usage is 260.6% just with a qmetro running.

Could anyone kindly take a look at the patch to see possible problems?

Somehow my Max patch's CPU usage is 260.6% just with a qmetro running.
Could anyone kindly take a look at the patch to see possible problems?

my-max-patch-is-extremely-slow

Don't know, I don't know what it is supposed to do but anyway it takes only 0.9% for my computer... have you checked the CPU limit of your Audio Settings?

I have to apologise the messiness of the patch to ask for help (I am patching in a hurry to make it for tomorrow's performance...).

So far I had to size down the matrices from 1920 x 1080 to 720 x 480, and slowe down the qmetro from 10 to 40 too. It's better, but still over 100%.

I have to apologise the messiness of the patch to ask for help (I am patching in a hurry to make it for tomorrow's performance...).
The CPU limit is set to '0'.
So far I had to size down the matrices from 1920 x 1080 to 720 x 480, and slowe down the qmetro from 10 to 40 too. It's better, but still over 100%.

I do not really understand what the patch is supposed to do, nor am I familiar with your patching strategies, so only some general comments, that should help with speeding things up.

By the way: running your patch takes only 1% on my cpu, what may be because the graphic file is not loaded and therefore not beeing processed ...

- Avoid animated GUI elements, they take processing power to be drawn in the interface. If you need the information to be shown for work but not in the performance you can put them into BPatchers and show/hide them like this

The BPatchers' name in the message box has to correspondent with the name of the BPatcher // okay, this is totally cirular, but you know what I mean ...

There are people saying that these are also calculated when hidden but for me this tactic speeds my patch (that is mostly opengl video & audio) up 3 times ...

- Further on you can change the [jitter] methods to [jit.gl] pipelines that allocates the sound to the cpu and the graphics to the gpu, I don't know for graphics, but for video it helps a lot.

Here is an example that Vade shared a while ago_

All of this not really helpful, as it doesn't deal with your posted patch, but as nobody else answered, I'd thought to say at least something ...

I do not really understand what the patch is supposed to do, nor am I familiar with your patching strategies, so only some general comments, that should help with speeding things up. 

By  the way: running your patch takes only 1% on my cpu, what may be because the graphic file is not loaded and therefore not beeing processed ...

The BPatchers' name in the message box has to correspondent with the name of the BPatcher // okay, this is totally cirular, but you know what I mean ...
There are people saying that these are also calculated when hidden but for me this tactic speeds my patch (that is mostly opengl video & audio) up 3 times ...

My Max patch is extremely slow