No disrespect either, but I actually read more than you were thinking of, given that I included the 2nd way (the "value increase" priority) in the code as well, anticipating your response (despite you assuring me that you wanted the "time expiration" priority twice). It's just that you didn't understand the implications properly.Don't take this the wrong way, I don't mean any disrespect, but maybe you didn't read this properly?![]()
Let me explain it better, for the last time: you either stay on that initial greater position for the whole second regardless of the increasing in volume potentially happening during that second OR you react straight away when increasing in volume regardless of whether that might happen during the second you want to stay in that initial greater position. It's either one or the other, there's no middle way, it's like saying you want to both drive your car for one whole hour and immediately get out whenever your speed increases.
No, it does not, because it's not logically possible, see the real life example above. It has nothing to do with Rainmeter. Whatever you think you saw in those VU meters is mostly likely skipping some values or something. But if you want, feel free to provide such an example, with the entire data for examination, and if you're right I'll admit without any issues.Every VU meter with Peak does exactly what I'm asking.
For the earlier example with each of these volumes at 200 ms each, during a whole second:
1) 0.7
2) 0.5
3) 0.3
4) 0.4
5) 0.2
The process first chooses to display 0.7 when reaching 0.5, because you want to stay on the greater volume for that second and the volume dropped. Then, it still chooses 0.7 when reaching 0.3, for the same reasons. But, when reaching 0.4, what do you do choose: 0.7 to stay on it for a whole second, or 0.4 because the volume increased from the previous 0.3? Can you do both at the same time without one of them being canceled by the other? Show me the VU meter - or any other tool or human - that can do the latter, and I'll eat my hat (or hood, lol). Do you understand now?

Statistics: Posted by Yincognito — Yesterday, 9:37 pm