-
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
Allow users to specify (multiple) locations in Preferences during Plugin/Effects scan #6156
Comments
@vsverchinsky . There's a problem with the tab order. If the "add new location" for the VST plugins is the focus, then if a user presses Tab, then the "add new location" button for the VST3 plugins becomes the focus, rather than the text box. This is a confusing reading order for users of screen readers - and it looks pretty odd as well. |
When submitting the new plugin locations, then removing one of them and clicking OK button, Audacity crashes:2024-04-23_19-04-00.mp4After adding a plugin location for LADSPA, then for LV2 and then clicking the Remove button for LV2, the previously added LADSPA location is deleted instead:2024-04-23_18-55-10.mp4When adding new plugin locations, the bottom of the screen gets squashed:2024-04-23_18-58-27.mp4 |
@vsverchinsky If more than one directory is added for the same plugin family, the new text boxes are put on top of the rest, taking away all available space with each newly added line: |
Windows:
2024-05-17_17-16-53.mp4macOS:
|
@vsverchinsky one of the previously reported issues remains unfixed: on macOS, a custom VST path is still being ignored and the plugins in it aren't found. |
Tested. All previously reported problems have been fixed. |
Your idea
Add a new option in Effects preferences to specify custom plugin search path
Problem to be solved
At the moment, Audacity just reads from one location, which can be very problematic for those who like to keep effects on different drives, or when apps install effects in non-standard places
Prior art
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: