F2 bug - not recognizing sample rate change

[DaveBenham]

Once all the parameters have been set, the cutoff frequency becomes incorrect if the VCV sample rate changes. For example, doubling the sample rate doubles the effective cutoff frequency. The problem is fixed if the frequency cutoff is modified and then reset.

F2 just needs to add sample rate change as one of the checks to determine if (something - I don't know the code) needs to be recalculated

[kockie69]

Ok, looks like an easy fix. I will have a look. I was about to release a new version but will try to get this one added.

[kockie69]

Sorry, I think it is more difficult, I was too optimistic.
At the moment the code is capturing the sample rate change but there is no code implemented to really handle it. I will not implement it in the new 1.2.5 release, hopefully in 1.2.6.