in x64 on decay output = input within the same frame
in x86 it takes one frame. within that one it’s nearly there. ~3.5e-017 is not much, but enough to mess up the logic, when you don’t expect it switching architecture
@h99 nope, not related. this case is always evaluating. my guess is a precision issue btw x86 and x64. and or the question how the calculation is implemented that a filtertime of 0 can lead to an interpolation between former value and current input
