benniy

i have a question: i'm doing quite a few heavy calculations on the "ticks"-output of a [plugsync~] object.

have been thinking that [round] and [change] could reduce the cpu load (as the amount of messages would be restricted – anyhow i'm not even sure if this is the case.

has anybody got a tip for me? and possibly also another way to monitor the cpu load besides "view -> show cpu usage"?

hello folks,
i have a question: i'm doing quite a few heavy calculations on the "ticks"-output of a [plugsync~] object.
have been thinking that [round] and [change] could reduce the cpu load (as the amount of messages would be restricted – anyhow i'm not even sure if this is the case.

plugsync-cpu-load-reduction

I've noticed that plugsync~ delivers "ticks"-output at intervals of 64 samples (= vector size) which corresponds to 64/44.1, ie. about 1.5ms. Obviuosly, the amount of messages can be reduced with [round] and [change], at the cost of accuracy. But if that doesn't make a notable difference in performance I would think that your "heavy calculations" are not problematic. Keep in mind that math operations are typically executed in microseconds.

glad to hear that the round/change route makes a difference, at least theoretically :)

maybe you know where i can find the problem:

i have the feeling, that lots of UI-aspects in my patch (also simple ones such as hide and show commands for bpatchers)

are occasionally massively delayed (deferred?). i'm not using any MSP (if this is also correct for the plugsync object) –

mainly midi and clocking stuff (as mentioned – calculating, zmapping and routing clocks from [plugsync~] to run sequencer)

have you got a clue what the problem could be or how i could at least monitor it?

as always – thank you, broc!
glad to hear that the round/change route makes a difference, at least theoretically :)

maybe you know where i can find the problem:
i have the feeling, that lots of UI-aspects in my patch (also simple ones such as hide and show commands for bpatchers)
are occasionally massively delayed (deferred?). i'm not using any MSP (if this is also correct for the plugsync object) –
mainly midi and clocking stuff (as mentioned – calculating, zmapping and routing clocks from [plugsync~] to run sequencer)

have you got a clue what the problem could be or how i could at least monitor it?


plugsync~ cpu load reduction