Bugzilla – Bug 1722
Equalization effect: possible crash when using Manage > User Presets
Last modified: 2019-08-22 05:29:45 UTC
Is it possible to grey out "Manage > Save Preset" in the EQ effect? We already say in the manual that the presets feature is not working. Greying out "Save Preset" would prevent bad things from happening.
(In reply to Bill Wharrie from comment #1) I fully support this (and more ...). Apart from the potential crash situation it seemms nonsensical to have the two formas of curve management in EQ a) EQ's own Save/Manage Curves b) the Manage button Note that: a) is where the preset=curves are stored an managed from (i.e. the pukka way for EQ) is via this mech. b) with this the Manage>Factory Presets soes not work b1) it does not restore the default flat curve b2) if you use it in Graphic mode it switches you into Draw mode - it should not So maybe we should be: 1) graying out all the "Manage> *** Preset(s)" commands, or 2) graying out the Manage button in EQ 3) removing the Manage button in EQ Or more radically 5) retain the "Manage> *** Preset(s)" commands - but make thes go to the Save/Manage curves dialog.
Testing on W10 with RC001 for 2.3.2 I cannot reproduce this A) indeed at Step 10 my new names curve has disappeared B) but at Step 11 "User Presets" is grayed out and no crash can occur or occurs or if I already have a user preset then it is not grayed out bit the preset I "saved" at step 9 is not shown in the available user presets list - so once again no crash. But I think this bug stays open pending the planned separation of EQ into two separate effects for the two modes - and the simplification, unification and standardization of managing presets. So this remains thereby a target bug for fixing in 2.3.3
See also bug 2112.
Elevating to P2 to raise focus-level for the EQ split & maintenance planned for 2.3.3 - and P2 because of crash
Testing on W10 with audacity-2.3.3-alpha-326-c9fbd283b7bfc8702caf86a4672cba7ff6260b7d This now works with the user preset not being lost (same occurs independently in the two new split EQ effects. This loks to be fixed as a side effect of fixing Bug #2031