Tested at 1.5 RC5
Check interval appears to be ignored for |Delta|>X
Create a LS as follows:
Function |Delta|>X
Source Pot1
Value 10%
Check Interval 500ms
Min duration 0.1s (just for visibility)
My understanding (?) is that this triggers if pot1 has changed in either direction by more than 10% within 0.5s
If you now rotate pot1 very slowly I'd assume this should not trigger at all as it is changing by perhaps 3% in 0.5s. However this seems to trigger when pot1 gets to each 10% increment, i.e. starting from -100% triggering at -90%, -80% -70% etc, regardless of how slowly you rotate the pot or indeed even if you stop rotating. This suggests that the check interval is being ignored.
This can nicely be demonstrated by configuring a couple of screen widgets to display Pot1 and the LS next to each other.
I don't believe this is related to RC5 changes as I've seen this before, indeed I thought I'd raised an issue for it before but I can't see it (unless I started raising it but didn't actually submit - apologies if this is a dup).
I don't regard this as a critical problem, but feel it could be addressed perhaps with 1.5.1?
Jedsters
commented
4 months ago
Tested at 1.5 RC5 Check interval appears to be ignored for |Delta|>X
Create a LS as follows: Function |Delta|>X Source Pot1 Value 10% Check Interval 500ms Min duration 0.1s (just for visibility)
My understanding (?) is that this triggers if pot1 has changed in either direction by more than 10% within 0.5s
If you now rotate pot1 very slowly I'd assume this should not trigger at all as it is changing by perhaps 3% in 0.5s. However this seems to trigger when pot1 gets to each 10% increment, i.e. starting from -100% triggering at -90%, -80% -70% etc, regardless of how slowly you rotate the pot or indeed even if you stop rotating. This suggests that the check interval is being ignored.
This can nicely be demonstrated by configuring a couple of screen widgets to display Pot1 and the LS next to each other.
I don't believe this is related to RC5 changes as I've seen this before, indeed I thought I'd raised an issue for it before but I can't see it (unless I started raising it but didn't actually submit - apologies if this is a dup).
I don't regard this as a critical problem, but feel it could be addressed perhaps with 1.5.1?
Thanks