I'm not sure why Classic Filters is "disabled" by default #6162
petersampsonaudacity
started this conversation in
Ideas & Feature Requests
Replies: 1 comment
-
BUMP @LWinterberg |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
@LWinterberg @Tantacrul
Of all the Native Audacity EGATs that we ship Classic Filters is the only one that is shipped as "disabled" in the Plugin Manager.
I find myself wondering why this remains the case. I seem to recall some ancient history where the author of this effect threw a wobbly and went off in a huff as it too too long (according to him) to get it included in an Audacity release.
I recall that the reason for the delay was that the effect's author failed to produce any documentation or even guidance to the manual team to help them document it to Audacity standard/quality. We subsequently just got on with it and did it ourseleves and eventually included Classic Filters as part of Audacity.
I can see no reason for it to continue to stick out like a sore thumb - and I recommend that we switch its default status to be "enabled",
Beta Was this translation helpful? Give feedback.
All reactions