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
Crash editing Amplify (and some other effects) macro parameters #3769
Comments
The following EGATs also crash when trying to edit parameters in a Macro
And these Vamp plugins (other Vamp plugins appear unaffected):
I got the ET-phone-home-messages and pressed the Send button to send it on |
Another simpler workaround is to get this user to use the Normalize effect |
|
Suspect effects include those that override the So these should be checked: |
|
@Paul-Licameli @crsib @LWinterberg Testing with Paul's Branch build: audacity-win-3.2.2-alpha-20221006+73eb7de-x64 The following now do NOT crash Audacity at Step of of the STR:
BUT the following still cause a crash as step 5 UpdateI cannot test the Vamp plugins as these do not show up in the Analyze menu with Paul's branch build/ Nor do they show up in the Analyze menu with the latest 3,3,0 alpha either - I will log this as a separate issue |
Logged as: 3.3 alpha fails to load Vamp plugins #3795 |
|
I confirm the crashes in the three EQ effects from @petersampsonaudacity 's comment. The rest seem to not cause the crash. |
|
@Paul-Licameli @crsib @LWinterberg Testing with Paul's Branch build: Fix crash when editing macro parameters of Amplify and others... Build Audacity #2750 I confirm that the three effects that still previously crashed Audacity when trying to set parameters in a Macro di NOT do so now I also retested to confirm that the following still do NOT crash Audacity at Step of of the STR:
So all looks OK with this bug now in Paul's branch build. VampI still cannot test the Vamp plugins as these do not show up in the Analyze menu with Paul's branch build due to regression bug: |
|
BTW testing shows that this is a regression on 3.1.3 (introduced in 3.2.0) |
|
Verified. |
|
I confirm this remains un-fixed in latest 3.2.2 Beta: audacity-win-3.2.2-beta-20221017+31f4fee-x64-msvc2022 and in 3.3 alpha: audacity-win-3.3.0-alpha-20221011+69764a4-x64-msvc2022 |
|
@petersampsonaudacity it's not yet merged into the release branch |
|
@dozzzzer I figured that... so this was really a "nudge" to see if this could get merged, particularly since it's a P1 regression bug - and one that real-life users are falling foul of (as reported on the Forum) |
|
Testing on W10 with latest 3.2.2 Beta: audacity-win-3.2.2-beta-20221018+1196ca9-x64-msvc2022 I confirm that the three effects that still previously crashed Audacity when trying to set parameters in a Macro do NOT do so now in this Beta I also retested to confirm that the following still do NOT crash Audacity at Step of of the STR:
So all looks OK with this bug now in the latest 3.2.2 Beta |
Paul-Licameli commentedOct 6, 2022
•
edited by petersampsonaudacity
Bug description
Reported to me by Larry Hudson who has for years taught classes in the use of Audacity for voiceover.
Steps to reproduce
Crash!
But a known workaround:
Thereafter, editing the macro parameter is possible, so long as you do not close the Audacity project window in which you opened Amplify
Expected behavior
No crash
Actual behavior
a) No response in some cases
b) in other cases one gets the ET-phone-home dialog
Audacity Version
current master / alpha / nightly build
3.2.1
Operating system
Windows, macOS, Linux
Additional context
This bisects to 35581fa and does not affect all effects.
I don't know yet the complete list of effects that suffer. Specific Amplify code wasn't changed. It was instead things in the framework. But Nyquist effects (example, Low-pass filter) do not have the problem.
Another rescue for this user could be to write a simple Nyquist effect to substitute for amplify and share it.
The text was updated successfully, but these errors were encountered: