modulators, global & macro

[Christoph Hart]

@ulrik hmm, both use about 3% on my MacBook Air M1.

[A Former User]

@ulrik On my MacPro the synth timer example hovers around 1% and the macro example around 2%! Great stuff. I used timers in my instrument as well to make any parameter modulate, but the macros are are great too for that maybe...

[ulrik]

@christoph-hart hmm, ok there were not much difference in those examples.
Now I have two examples again, and this is heavy operations going on.

Both examples execute exactly the same tasks.

• example 1 (4 modulators in 4 SimpleGains, level read in synth.timer)

• example 2 (4 Macro modulators, 4 cb controlling the same parameters as above)

!

Watch the cpu

[ulrik]

@christoph-hart you use M1, I use Intel, is that the problem you think?

[ulrik]

@christoph-hart I guess I'm doing something stupid in the Macro version 🤪

I can send you the macro version if you want to see it?

[Christoph Hart]

@ulrik You are running the timers in the deferred callback, so it's no wonder why they don't appear in the CPU meter (this is just measuring the audio callback).

The macros will always run in the audio thread (which is what you want, otherwise your modulation system will not work if there is no interface present.

[ulrik]

@christoph-hart Haha...how the heck could you see that??
You're right, I forgot I had defer true in the timer cb, sorry

Well I took it away and now it's running defer = false, in the audio thread right?

The cpu increased a lot I can tell, it's almost as the macro but not really, the macro version is pending between 20-40? and the other version between 15-25 ?
On the other hand it stopped with "Execution timed-out" in the timer cb

[ulrik]

@christoph-hart thank you, I will stick to the Macro system now :)