Audacity Bug Summary
••• Introduction •••
••• Keywords •••
    Audacity 3.0.3 development began 19th April 2021

Audacity Bugzilla



Bug 2036 - Mac: Some AU plug-in effects can be enabled but fail to register
Mac: Some AU plug-in effects can be enabled but fail to register
Status: RESOLVED FIXED
Product: Audacity
Classification: Unclassified
Component: Audio Units
2.3.0
Mac macOS
: P3 Repeatable
Assigned To: Default Assignee for New Bugs
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2018-11-26 07:44 UTC by Peter Sampson
Modified: 2020-04-13 06:20 UTC (History)
7 users (show)

See Also:
Steps To Reproduce:
1) purge the audacity settings folder to emulate factory settings 2) Manage Plug-ins 3) Mark all shown AU effects as enabled 4) Click OK 5) observe through a series of dialogs the the following AU effects fail to register AUMixer AUMatrixMixer AUMultiChannelMixer AUMixer3D AUMultiSplitter AUShceduledSoundPlayer AUAudioFilePlayer AUSpeechSynthesis 6)observe from the Effects menu that these AU effects are not available
Release Note:
Group: AU effects The following AU effects can be marked "enabled" in the Manage Plug-ins dialog but they fail to register and are not available for use AUMixer AUMatrixMixer AUMultiChannelMixer AUMixer3D AUMultiSplitter AUShceduledSoundPlayer AUAudioFilePlayer AUSpeechSynthesis
First Git SHA:
Group: ---
Workaround:
Closed: 2020-04-13 00:00:00


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Sampson 2018-11-26 07:44:38 UTC
The following AU effects can be sen in the "New" list in the Manage Plug-ins dialog:

AUMixer
AUMatrixMixer
AUMultiChannelMixer
AUMixer3D
AUMultiSplitter
AUShceduledSoundPlayer
AUAudioFilePlayer
AUSpeechSynthesis

But they fail to register through a series of dialogs - each one of which the user must acknowledge.

Occurs on 2.3.0 and the 64-bit 2.3.1 alpha (I have not tested earlier versions)
Comment 1 Peter Sampson 2018-11-26 08:04:20 UTC
Further testing shows that this first occurred in 2.2.2

But it looks like for 2.2.1 and earlier these particular AU effects were not shipped with Audacity
Comment 2 Steve Daulton 2018-11-26 09:08:35 UTC
(In reply to Peter Sampson from comment #1)
"We" don't ship AU effects. Some are shipped with macOS. Others are shipped with other Mac software, and some are available as third party downloads.

Some AU effects could require features in the host application that Audacity does not support (as is the case with some VST effects).

We should probably note in the manual which "standard" AU plug-ins (ones that are shipped with the operating system) are not supported by Audacity.
Comment 3 Peter Sampson 2018-11-26 09:26:27 UTC
(In reply to Steve Daulton from comment #2)
>We should probably note in the manual which "standard" AU plug-ins 
>(ones that are shipped with the operating system) are not supported 
>by Audacity.

But before I do that I would like to know if the set I list is Mojave specific or is the same in earlier macOS versions

-------------------------------------------------

>"We" don't ship AU effects. Some are shipped with macOS. 
>Others are shipped with other Mac software, and some are 
>available as third party downloads.

So why do I see a different (smaller) set available in 2.2.1 and earlier when running on the same Mojave Mac ?   :-//
Comment 4 Cliff Scott 2018-11-26 10:22:24 UTC
I asked Gale about these plugins quite a while back and he assured me that those 8 not enabling is normal.

I don't know why you have a shorter list, but going back to 2.1.2 I still show those 8 that will not enable.
Comment 5 Leland Lucius 2020-03-07 02:50:40 UTC
Fixed in:

https://github.com/audacity/audacity/commit/35fa6cf

None of these plug-ins expose parameters and this wasn't handled properly.

BUT...

Since they are handled correctly now, they appear in the menu if you enable them.  But, Audacity isn't prepared to handle the functions they perform.  In theory, the AUAudioPlayer and AUNetReceive could be made to work, but I'm not sure the effort is worth it.

Should we just add them to a "blacklist" so they are bypassed in the scan altogether?
Comment 6 Peter Sampson 2020-03-08 07:55:28 UTC
(In reply to Leland Lucius from comment #5)
Testing on macOS 10.15.3 with Audacity 2.4.0 5900c52

I get no complaint dialogs at step 5 and all available AU effects appear top register and can be properly enabled in the Plug-in Manager.   But some in the list in the Steps to reproduce do not work and others are missing (presumably no longer distributed with macOS 10.15.3)

1) These ones register and can be enabled.  They appear in the Effect menu, but when you select them nothing happens (other AU effects do work).
AUMixer
AUMatrixMixer
AUMultiChannelMixer
AUMixer3D
AUMultiSplitter


2) These AU effects are no longer listed as available in the "New" list in Plug-in Manager
AUShceduledSoundPlayer
AUAudioFilePlayer
AUSpeechSynthesis


3) In Comment #4 Leland talks about "AUAudioPlayer and AUNetReceive" - these too appear to be no longer available on 10.15.3 (I can supply a screenshot with my list of AU effects if that helps at all - please advise)


So technically this bug as written is fixed as the AU effect can all be registered and enabled - BUT because they don't work I shall REOPEN this for the residual (unless we want that as a new bug?).
Comment 7 Leland Lucius 2020-04-12 15:07:27 UTC
Blacklist added for these effects since Audacity doesn't support them:

appl/augn/afpl/Apple: AUAudioFilePlayer
appl/augn/nrcv/Apple: AUNetReceive
appl/augn/sspl/Apple: AUScheduledSoundPlayer
appl/augn/ttsp/Apple: AUSpeechSynthesis
appl/aumx/3dmx/Apple: AUMixer3D
appl/aumx/mspl/Apple: AUMultiSplitter
appl/aumx/mxmx/Apple: AUMatrixMixer
appl/aumx/smxr/Apple: AUMixer

If additional "problematic" effects are found in the future, it's easy to blacklist them. (Though an external "blacklist.txt" file would be even better.)
Comment 8 Peter Sampson 2020-04-13 06:20:52 UTC
(In reply to Leland Lucius from comment #7)
Testing on macOS 10.15.4 with Audacity 2.4.0 2e5fc67

These problematic effects are no longer shown available on the "New" section of the Plug-in Manager.

The blacklist looks to be working properly