-
Notifications
You must be signed in to change notification settings - Fork 17.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix Static Notches #28034
Fix Static Notches #28034
Conversation
I think we should still remove the check here:
It will allow runtime param changes to take affect for static notch as they do for the others. |
This was/is covered by the init() above. The reason not to do it here is the cost of updating the static notch all the time when it doesn't need it. |
The init allows runtime change in frequency/bandwidth/attenuation but not runtime change in harmonics or double/triple notch.
I guess I don't really understand why we carefully check if we should re-init due to param change. It seems to be the update is the costly one we just do that all the time (except static). Why don't we check for a change in options or harmonic too and then call init and update at once? |
I mean this is true, but I don't think what you are suggesting fixes this does it? I agree that allowing runtime changes to these properties would be convenient.
Really just copying the pattern that was there for the LPF. It is true that calculating A&Q is expensive, so avoiding doing that all the time makes sense. However, we have made a lot of effort into making update cheap, so it may be that simply removing the check is not such a big deal anymore. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
good find, thanks!
Thanks @tridge I've pulled in the change |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is correct.
Bug introduced in #25442
I will note in passing that my review indicated this shouldn't be removed.
I have added a test to make sure this can't regress