I am looking at resetting the mTime* measures, but how is that achieved? How to you reset a measure that is ticking up? It resets every time it is at '2', but once the Peak maxes out it seems to go over 2 and then can't reset itself.
I am looking at resetting the mTime* measures, but how is that achieved? How to you reset a measure that is ticking up? It resets every time it is at '2', but once the Peak maxes out it seems to go over 2 and then can't reset itself.
If you want to reset it to its initial value of 1 (as per its Formula option), disable the measure, update it, enable it again and update it again. If you want to reset it to 0, skip updating it again in the last step. Obviously, if needed, you can delay enabling it again and any potential update again as desired via !Delay.
This doesn't quite work, but do you see what I'm trying to do with it? On sensing a drop in volume, which can be made more or less sensitive by adding/removing zeros after the decimal, it will pause the meter to allow it to stay when dropped, but react straight away when increased in volume. See IfCondition2:
Thing is, the #CURRENTSECTION# is never going to equal (#CURRENTSECTION# - 0.1). So how do I write a formula that can measure a decrease in peak volume? Then it can pause, delay, unpause on a decrease in volume and ignore on increase.
The only way I can think of is getting the value from the previous skin update. But I don't even know if that can be done, let alone how to do it!
sl23 wrote: ↑July 1st, 2024, 1:54 pmThing is, the #CURRENTSECTION# is never going to equal (#CURRENTSECTION# - 0.1).
Obviously.
sl23 wrote: ↑July 1st, 2024, 1:54 pmThe only way I can think of is getting the value from the previous skin update. But I don't even know if that can be done, let alone how to do it!
There you go, yes. Of course you know how to do it and that it can be done, just save (!SetVariable) that previous value to a variable, and compare it with the current measure value. Naturally, for this to work, the comparison must be done before the current measure value is saved as the previous value variable.
I know I have to figure out where the [!SetVariable Peak "[mPeakLeft]"] needs to go and how to set a delay when updating that. Where it is now isn't updating the Variable for some reason.
Only issue with this, is that it's rather jittery in function. Increases in Peak are meant to be, but you don't get the nice smooth decrease as it would during normal functioning.
And also, refreshing the skin causes the Peak meters 'X' position to zero out instead of stay where they are.
sl23 wrote: ↑July 1st, 2024, 3:58 pm
I feel like I'm just making a mess of this!
This has fixed an issue with the Peak meters constantly zeroing out for an update every 2 seconds, but I'm lost trying to achieve my goal!
sl23 wrote: ↑July 1st, 2024, 4:01 pm
Only issue with this, is that it's rather jittery in function. Increases in Peak are meant to be, but you don't get the nice smooth decrease as it would during normal functioning.
And also, refreshing the skin causes the Peak meters 'X' position to zero out instead of stay where they are.
I don't even remember what was your goal right now, lol - so many different questions at each step for things you should have known already, I'm lost in that spider net. Don't know how your skin should be written or why things zero out or not, it's your skin. So, do you still need that previous value vs current value thingy or not?