have a look at the [dsp] object/abstraction. it uses [cputime]. you
should be able to feed this directly back to your patch.
for example, if dsp reaches a certain percentage, then turn off some
subpatches or reduce the refresh rate of your vu meters...
marius.
matteo sisti sette wrote:
Hi,
Hi,
I wish I could estimate cpu usage (in terms I will define later)
from within the patch, in order to have some part of the patch adapt
to it and work with higher resolution when more free cpu power is
available, and less when the cpu load is higher. For instance, I would
like to have some
Now I noticed this weird thing:
Compare this:
[bang~]
|
[t b b]
| |
[timer]
|
(number)
to this:
[bang~]
|
[t b b]
| |
[realtime]
|
(number)
With [timer] I get 1.45125, which is 64/44100*1000 as expected. With
[realtime], I would expect a slightly varying value around 1.45125
With [timer] I get 1.45125, which is 64/44100*1000 as expected. With
[realtime], I would expect a slightly varying value around 1.45125
approximately, but I get values below 0.1!!
Whooops! :$:$:$:$:$:$
That's not true!!
With realtime I get a lot of small values around 0.1 and then,
