tlm
January 19, 2022, 10:27am
1
I just upgraded to Audacity 3.1.3 and found that I could not make a keyboard shortcut for the “Label Sounds” plugin unless I deleted a duplicate version of it from the /Users/[name]/Library/Application\ Support/audacity/Plug-Ins folder. That is, once I deleted/disabled the version in that folder (but still had the version within the Applications folder) I was able to make a shortcut for it in the Preferences.
Maybe this is intended behavior, I don’t know. For me it was very confusing. As I tried to get previous plug-ins working I noticed that some appeared in the Tools > Add/Remove Plug-ins … dialog which were not actually present in the Plug-ins folder of the Audacity App “Package” folder. I always closed and reopened Audacity between making changes to the Plug-ins folders, but I didn’t reboot – so maybe that’s why. If I understand correctly, any plugins which I add should go into the /Users/[user]/Library/Application\ Support/audacity/Plug-Ins folder, but I because of my confusion I also started tinkering with the Audacity App “Package” folder. I’m probably doing something wrong in managing these plug-ins, but I just thought I’d mention it.
steve
January 19, 2022, 10:39am
2
Not exactly as intended. There are several issues logged for attention regarding effect management, including:
opened 12:15PM - 02 Sep 21 UTC
bug
P3
macros / scripting
plugins
**Describe the bug**
Identically-named effects cannot be differentiated in the … Select Command dialog in Macro editing
Originally logged on Bugzilla as P3 1709
https://bugzilla.audacityteam.org/show_bug.cgi?id=1709
**To Reproduce**
Steps to reproduce the behavior:
1. Install any two identically-named effects of different type (e.g. "Limiter" in nyquist and LV2)
2. Manage Macros
3. Add a new Macro or select an existing Macro
4. Click Insert - in the Select Command dialog there will be two entries with the same name (e.g. "Limiter")
5. Click either entry and then click "Edit Parameters"
6. Observe: Regardless of which entry you click, the same dialog is shown
**Expected behavior**
Similarly named effects should be differeentiated
**Screenshots**
None
**Additional information (please complete the following information):**
- OS: all OS
- Version: Reported on 2.2.0 - but still extant with 3.0.4 / a;pha 3.1.0
**Additional context**
**Bill wrote on the Bugzilla thread:**
On Mac:
1) download the free mda VST pack http://mda.smartelectronix.com/effects.htm
2) install "mda Limiter.vst" in ~/Library/Audio/Plug-ins/VST
3) start Audacity
4) in Effects Preferences, choose Group by Type, then OK
5) in the Plug-ins Manager, enable the mda Limiter effect
6) import or create some audio and select it
7) Effect > VST > Limiter: you get the nyquist Limiter effect
If you don't do step 4, then you get a cascading menu at Effect > Limiter where you can choose one or the other by full path.
This is similar to choosing an effect in Chains where it is done by name rather than by full path.
BTW, on my Mac (10.11.4) all the mda VST effects crash Audacity. Just a heads-up in case you were thinking of actually using the mda Limiter.
**and later he wrote:**
On Mac:
1) download the free mda VST pack http://mda.smartelectronix.com/effects.htm
2) install "mda Limiter.vst" in ~/Library/Audio/Plug-ins/VST
3) start Audacity
4) in the Plug-ins Manager, enable the mda Limiter effect
5) File > Chains > Edit Chains, Add a new chain and click Insert
Note that in the "Select Command" dialog there are two entries for "Limiter"
6) Select the first "Limiter" in the list and Edit Parameters
- you get the Nyquist Limiter
7) Select the second "Limiter" in the list and Edit Parameters
- you get the Nyquist Limiter
I don't think this is a matter of "LV2 effects are hidden by like-named LADSPA effects in Chain editing" as the title currently says, since it happens with identically-named effects of any stripe.
Changing the bug title to:
Identically-named effects cannot be differentiated in the Select Command dialog in chain editing
Although, as shown in comment 2, there is also a problem with identically-named effect in the Effect menu.
Also changing Component from "LV2" to "User Interface" since this seems to be an issue of choosing effects by name rather than an issue with any particular effect type.
opened 03:18PM - 01 Sep 21 UTC
bug
P5
Effects (EGATs)
**Describe the bug**
If the "type" of a plug-in that has already been registere… d is changed, the plug-in does not move to the correct menu for the new type.
The problem appears to be that the menus are populated from the pluginregistry.cfg file, which does not get updated when plug-ins change.
Originally logged on Bugzilla as P3 1942
**To Reproduce**
Steps to reproduce the behavior:
1) Open an installed plug-in in a plain text editor,
2) Find the line near the top that starts with:
$type
The type will be one of:
process
analyze
generate
tool
tool .... (one of the first three types).
3) Change the type to one that belongs in a different menu. For example if it is a "process" (Effect menu) type, change it to a "generate" type.
eg. from:
$type process
to:
$type generate
4. Observe: the plug-in does not move to the new menu.
**Expected behavior**
A clear and concise description of what you expected to happen.
**Screenshots**
If applicable, add screenshots to help explain your problem.
**Additional information (please complete the following information):**
- OS: [e.g. Mac High Sierra, Ubuntu 18.04, Windows 10]
- Version [e.g. Audacity 2.5.1]
- (if relevant) Sound Device [e.g. Windows WASAPI, USB Sound card]
**Additional context**
To get the plug-in to appear in the new menu after the type has been changed, it is necessary to:
1) Close Audacity
2) Delete pluginregistry.cfg
3) Restart Audacity.
We have had reports from very confused users about "Sample Data Export" being in the wrong menu (which I believe is due to this bug).
opened 08:21AM - 29 Jul 21 UTC
closed 11:36AM - 01 May 22 UTC
Scheduled for replacement
**Describe the bug**
On Windows, if a 64bit version of 3.0.3 is installed witho… ut first uninstalling any existing 32bit versions then:
1. On the effects menu, there are duplicates for the nyquist effects which are shipped with Audacity: for each a effect there's sub menu with two items.
2. If you uninstall the 32 bit version after installing the 64 bit version, there are no entries for Audacity in the start menu.
On Windows , users should be recommended to uninstall any 32 bit versions before installing a 64bit version.
**To Reproduce**
Steps to reproduce the behavior:
1. Open effects menu.
2. There are sub menus for the nyquist effects shipped with Audacity
**Expected behavior**
On the effects menu, there should be items for nyquist effects, not sub menus.
**Additional information (please complete the following information):**
Windows 10
Audacity 3.0.3 64bit
opened 11:28AM - 17 Jun 21 UTC
closed 08:22AM - 10 Aug 22 UTC
Design / UX
Task
plugins
PluginManager
Design in Figma
Automatically detecting new installed VST/AU plugins, scann… ing them at startup, and clean up of the current plugin manager
Related to: #992
- [x] Automatic scan, test and enabling of plugins
- [ ] New UI
- [ ] Manually adding search paths
tlm
January 19, 2022, 10:52am
3
Thanks for the quick response. Obviously, you folks are on it.