-
Notifications
You must be signed in to change notification settings - Fork 404
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
Clicks n Pops Master Issue #699
Comments
OK so my first thought on clicks-n-pops is that something must be uninitialized, reads random memory, and then outputs garbage to the sound channel. So I bit the bullet and set up surge so I could actually play notes on an on screen keyboard while it was running in valgrind. For other intrepid folks, here's how
once surge has started jack keyboard should have a 'connected to' option for surge in. Pick it and press a note and surge will play. Useful. When you do that, on linux you see lots and lots of jmps on uninitialized reads, some in the filters. |
Oh and that's just from playing a single note in the init patch. I'm sure other reports in the clicks n pop family have similar problems in other spots. |
Linking #710 here also |
In two places, filters were using uninitialized memory at creation. In some cases, for some values, in some instances, this would create a large "pop" as the filter went unstable with crazy coefficients or history values. In my headless simulator, without these initialization changes we get a click and pop within the first 100 instances. With them there is no unstable run within 20,000 instances. In theory this Closes surge-synthesizer#790 Closes surge-synthesizer#753 Closes surge-synthesizer#699 Closes surge-synthesizer#698 Closes surge-synthesizer#662 Closes surge-synthesizer#660
In two places, filters were using uninitialized memory at creation. In some cases, for some values, in some instances, this would create a large "pop" as the filter went unstable with crazy coefficients or history values. In my headless simulator, without these initialization changes we get a click and pop within the first 100 instances. With them there is no unstable run within 20,000 instances. In theory this Closes surge-synthesizer#790 Closes surge-synthesizer#753 Closes surge-synthesizer#699 Closes surge-synthesizer#698 Closes surge-synthesizer#662 Closes surge-synthesizer#660 Former-commit-id: 8e8307f5065169c6651215a1832bdd3cd315b403 [formerly 506ec57] Former-commit-id: f6fd0b5ce82ee51975a9e12079ff44d6d788405f Former-commit-id: 025d2371d9ed79ddc4da4540211633bbc416ccbd
Just having a master issue for all the clicks n pops reporting we have. I have an update in a second on some thoughts.
The text was updated successfully, but these errors were encountered: