-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Normalize (and Loudness Normalization) - OK & Preview buttons are grayed out (on invoking the effect) #2701
Comments
I'll note that the "(Maximum 0dB)" disappears when you check any button, and also that the unit text (dB / LUFS - see screenshot above) gets cut off before you resize the window. |
this has persisted across the recent UI change, see #3495 for screenshots |
Testing on W10 with latest 3.2.0 alpha - audacity-win-3.2.0-alpha-20220902+7c9c978-x64-msvc2022 Normalize and Loudness Normalization have the Apply button not-grayed-out and active - however they both still have the Preview button grayed out. This means that VI users cannot Tab to access the Preview button. |
Testing on W10 with latest 3.2.0 alpha - audacity-win-3.2.0-alpha-20220907+591f227-x64-msvc2022 @Paul-Licameli @LWinterberg @dozzzzer This now appears to be working correctly on Windows - in both effects the Preview and Apply buttons are no longer grayed-out and inaccessible when invoking the effect. |
The "Preview" button is still greyed out in Loudness Normalization. |
Tested and verified fixed in latest alpha branch. |
Describe the bug
When invoking the Normalize or the Loudness Normalization effects the OK button and the Preview button are both greyed out and the effect cannot be implemented on the selected audio.
This is a regression on 3.1.3 - and a regression on the previous alpha master that I have:
audacity-win-3.2.0-alpha-20220302+b7708d1-x64-msvc2022
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
Additional information (please complete the following information):
Additional context
Simple workaround - but does not look good to the user
See also:
Amplify fails to default offer amplification to 0db #2700
The text was updated successfully, but these errors were encountered: