if 0.7, 0.5, 0.3, 0.4, 0.2 happen one after the other during that one second while it should stay in position at 0.7if 0.7, 0.5, 0.3, 0.4, 0.2 happen one after the other during that one second while it should stay in position at 0.7 (because 0.5 was less than the previous 0.7 value), it should however use 0.4 when this occurs (because it is greater than the previous 0.3 value), right? In other words, an increase in the value has priority over the potential stay in position that might be happening at the same time? Yes or no.
This was correct, what I asked for and what you achieved. Perfect, except I hadn't foreseen the downside of it. If you change it to this
if 0.7, 0.5, 0.3, 0.9, 0.2 Then the priority is given to the increase if it all happens as before within that second. Your code doesn't do that as it just continues regardless of the increase.
Only if during that second there is an increase in volume from the 0.7 does it override the delay. Perhaps, I assumed you know more about how Peak meters worked? You are a magician with code but if you aren't aware of how they work, then you can't make the code do what you want. Have you ever seen Peak meters in action?
I'm not saying you aren't right, I'm just guessing at how it appears to work from a non-programmer pov.
I'll try make a quick video with foobar...
Statistics: Posted by sl23 — Yesterday, 10:05 pm