balala wrote: ↑May 21st, 2020, 6:28 pmI think this is a normal thing, for the same reason why, as you probably know, all "visualizer" skins increase the CPU usage, due to the required low Update.
Not so much due to the low Update, but due to more than one skin having low Update, and also due to the high CPU usage of AudioLevel measures (as they perform FFT, Hann functions, RMS, etc) in conjuction with other factors that increase CPU usage "externally" of Rainmeter. Incidentally, I've spent the last days testing this extensively, since I just added an audio skin / visualiser to my suite.
balala wrote: ↑May 21st, 2020, 6:28 pmWhen using the ActionTimer plugin, although the Update of the whole skin is in most cases "normal", but at least while running, the ActionTimer plugin measure is updated frequently. And in many cases along with it, a few other measures, as well as a few meters are also updated same frequently. This can led to a CPU usage increase. I think this is normal and how much it goes on, depends on the code of the skin itself.
It's only the update of the AT plugin measure, as the rest of the code is intentionally identical for both methods (AT and no AT), actually. Even the YT video used in testing is identical, for perfectly accurate test results.
balala wrote: ↑May 21st, 2020, 6:28 pm[!MoveMeter...] and
[!UpdateMeter...][!Redraw] do different things, you can't compare them.
They don't do much different things when used in the same context (i.e. when moving a meter) ... or at least that's not the intent of the skin developer when using them. For example, assuming SomeMeter has its
Y=0, these two things below do the same thing, but the 2nd choice is faster:
Code: Select all
[!SetOption SomeMeter X 30][!UpdateMeter SomeMeter][!Redraw]