Re: auval doesn't detect third party AudioUnits when launched via SSH on Mojave
Re: auval doesn't detect third party AudioUnits when launched via SSH on Mojave
- Subject: Re: auval doesn't detect third party AudioUnits when launched via SSH on Mojave
- From: Brian Willoughby <email@hidden>
- Date: Wed, 06 Mar 2019 22:42:29 -0800
There are a few possible explanations.
First, check the path. You’re probably running a different version of auval via
ssh versus direct. Use `which auval` in each situation to see. You can also run
`auval` without any options to confirm the Version.
Second, I assume that you’re running a different version of Xcode on the new
computer, and it’s very likely that you’re not building your plugins correctly.
I have never had auval fail to recognize a properly-built AudioUnit. As a test,
try installing your AudioUnits as built on another computer, to remove your new
build environment as a variable.
Third, there are both 32-bit and 64-bit plugins, and auval can only scan one
kind at a time. You can pass a command-line parameter to auval that will select
between 32- and 64-bit plugins. Not sure why the path or version would affect
this, but it’s worth confirming.
Brian Willoughby
On Mar 6, 2019, at 9:05 AM, Corentin Comte <email@hidden> wrote:
> I've just replaced my old mac Mini (which was running on El Capitan) by a
> brand new one, running on Mojave. I use this computer to build and validate
> AudioUnit plugins, thanks to a bunch of scripts executed through SSH.
>
>
> The problem is that, since I updated to Mojave, when I launch auval to test
> my plugins, I get this message:
>
> --------------------------------------------------
> VALIDATING AUDIO UNIT: '...' - '...' - '...'
> --------------------------------------------------
> ERROR: Cannot get Component's Name strings
> ERROR: Error from retrieving Component Version: -50
>
> * * FAIL
> --------------------------------------------------
> TESTING OPEN TIMES:
> FATAL ERROR: didn't find the component
>
> What intrigues me is that I only get this message when launching auval via an
> SSH connection to the computer. If I run auval directly on the computer, I
> don't have any issue. If I run 'auval -a' via SSH, none of my AudioUnits
> would appear in the list, only those from Apple ; but when I run the same
> command directly on the computer, my AudioUnits are actually displayed in the
> list.
>
> I have the feeling that there is something in Mojave's security settings that
> forbid auval to properly run via SSH, does someone have any clue or the
> same problem ?
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden