I’m having the following problems with AU on the DTK (hence Big Sur and Apple Silicon).
I’ve tested with a default plug-in project, newly generated with Projucer, and it exhibits the same issues, which may or may not be correlated.
Problem number 1:
EDIT: auval -comp
seems to fail also for plug-ins that load perfectly well in Logic on ARM64, therefore it’s not related to the problem #2 described below. It might even be that validating with the -comp
switch is not supported on ARM64 (yet)
EDIT2: the Apple webisite confirms that the Component Manager API, the one that’s tested with -comp
, is no longer supported on ARM64. See my post below.
The command
auval -comp -v Plug Ids Here
fails with this output:
AU Validation Tool
Version: 1.7.0
Copyright 2003-2019, Apple Inc. All Rights Reserved.
Specify -h (-help) for command options
--------------------------------------------------
VALIDATING AUDIO UNIT: 'aufx' - 'Lpqp' - 'Manu'
** As Component **
--------------------------------------------------
Manufacturer String: yourcompany
AudioUnit Name: NewProject
Component Version: 1.0.0 (0x10000)
* * PASS
--------------------------------------------------
TESTING OPEN TIMES:
FATAL ERROR: didn't find the component
I have attempted:
- deleting the build folder
- changing the version number of the plug-in before rebuilding
- restarted the computer and killed AudioComponentRegistrar before attempting rescan
But none of the above worked.
Problem number 2:
When launching Logic Pro 10.6, a window appears saying that there are invalid plug-ins and prompts to open the Plug-in Manager. There the plug-in is listed with a “crashed validation” message.
Selecting it and clicking “Reset & Re-scan selection” opens a window that reports the following error:
validating Audio Unit NewProject by yourcompany:
arch: Unknown architecture: arm64e
validation result: crashed validation
What is working:
Please note that the problematic auval command has the -comp
switch to test the AU as Component.
The “default” scan of auval -v Plug Ids Here
completes successfully, but that’s not what I’m after.
The original project was passing both types of validation on Intel Catalina and I suspect that, if it passes auval -comp on Big Sur Arm64, that could also solve problem #2 with Logic. EDIT: thanks to the responses below, it appears this has nothing to do with the ability of the plug-in to satisfy Logic validation criteria
Also about Logic, in the Plug-in Manager I checked the box in the “Use” column to use the plug-in anyway and (after restarting Logic, otherwise it doesn’t pick it up), the plug-in appears in the Audio-Unit menu (under a sub-menu named [Incompatible]
) and it works flawlessly when instantiated.
So both above problems seem to be specifically related to auval rather than Logic.
Details:
I’m on the current JUCE develop (several commits after 6.0.4)
This is a DTK still with its original Big Sur 11.0 beta version (20A5299w). I’m afraid to update it because I’ve heard horrific stories about bricked devices.
All projects have been built on the DTK, for arm64 architecture only (i.e. Rosetta has not a role in all of the above), using the Xcode beta that came with it: Version 12.0 beta (12A8158a)
I have been unable to run on it a more recent version of Xcode (e.g. 12.2): it bounces a few times in the dock then crashes. But that’s a different issue, possibly due to the fact that the OS is not up to date with the latest beta.
Questions:
I’m aware that similar issues have been reported in the main topic JUCE and macOS 11 / ARM by @zabukowski, but in contrast with his experience, a default generated project from Projucer doesn’t pass auval in my case.
Perhaps his attempts at executing auval from the command line didn’t include the -comp
switch?
But even in that case, the issue #2 with Logic remains in my case, where in his it looks it was being correctly recognized and that error window regarding arm64e stopped appearing.
Neither my original project nor the default one have QTKit or OpenGL frameworks.
Has anyone had similar problems?