Re: auval only showing apple audiounits
Re: auval only showing apple audiounits
- Subject: Re: auval only showing apple audiounits
- From: "James A. Baxter via Coreaudio-api" <email@hidden>
- Date: Tue, 16 Jul 2019 19:00:53 -0400
I think I've tracked down this issue to a specific new function in iTerm v3.2.8
(we're at 3.2.9 now). It turns out Apple Terminal does not have this issue.
As well as "auval" not working, my test scripts using the three techniques
below don't work in iTerm v3.2.8+:
* AVAudioUnitManager.shared.manager().components(matching:
componentDescription)
* AVAudioUnitManager.shared.manager().components(passingTest: { comp, stop in
* AudioComponentFindNext(comp, &componentDescription)
I posted on the iTerm gitlab issue board, but thought someone here might know
what's up.
The new function is "MoveOutOfAquaSession()". Simply commenting out the call
to this function fixes the issue.
void MoveOutOfAquaSession() { // FIX for issue 4147
// This function must be called just before fork();
//
// This funcion move the process from the Aqua 'per-sesion' namespace to the
// same user 'per-user' namespace. This method is the standard method used
// by Apple for doing this kind of move. It is exactly the same move method
// used by Launchd.
mach_port_t parent = MACH_PORT_NULL;
kern_return_t kr;
kr = bootstrap_parent(bootstrap_port, &parent);
if (kr == KERN_SUCCESS) {
// Detach server daemon process from the user's Aqua 'per-session'
namespace,
// and move it to the same UID 'per-user' namespace (just one level up).
mach_port_mod_refs(mach_task_self(), bootstrap_port,
MACH_PORT_RIGHT_SEND, -1);
task_set_special_port(mach_task_self(), TASK_BOOTSTRAP_PORT, parent);
return; /* All Done! now return, as we are ready to begin forking! */
}
// Never reach. Unless if we had failed to get the parent bootstrap port,
which according
// to Apple's documentation never happens. But I already saw rare weird
system situations
// where it may happen.
// Almost impossible, but if it happens, for sure is a BUG. So log it just
in case.
FDLog(LOG_ERR, "BUG: Error getting parent BS port! Please report this msg
and code: '%x'", kr);
}
More detail, including the file containing this function and the function that
calls it, as well as a huge comment explaining it:
https://gitlab.com/gnachman/iterm2/issues/7946
> On Apr 17, 2019, at 3:00 PM, email@hidden wrote:
>
> Send Coreaudio-api mailing list submissions to
> email@hidden
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.apple.com/mailman/listinfo/coreaudio-api
> or, via email, send a message with subject or body 'help' to
> email@hidden
>
> You can reach the person managing the list at
> email@hidden
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Coreaudio-api digest..."
>
>
> Today's Topics:
>
> 1. Re: auval only showing apple audiounits (James Baxter)
> 2. Re: auval only showing apple audiounits (Bernie Maier)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 16 Apr 2019 15:02:35 -0400
> From: James Baxter <email@hidden>
> To: email@hidden
> Subject: Re: auval only showing apple audiounits
> Message-ID: <email@hidden>
> Content-Type: text/plain; CHARSET=US-ASCII
>
> I only tried "auval -a" for the first time recently and had the same issue.
> Also High Sierra 10.13.6.
>
> I just tried "auval -32 -a" even though I thought everything was 64-bit
> (e.g., I don't use the 32-bit bridge in Logic Pro X), and sure enough that
> shows at least most of the ones that were missing.
>
> Maybe I'm confused about the meaning of 32-bit in this context?
>
> FWIW, this is what a failure to find a specific plugin looks like:
>
> auval -v aufx Td10 Tdrl
>
> AU Validation Tool
> Version: 1.6.1a1
> Copyright 2003-2013, Apple Inc. All Rights Reserved.
> Specify -h (-help) for command options
>
> --------------------------------------------------
> VALIDATING AUDIO UNIT: 'aufx' - 'Td10' - 'Tdrl'
> --------------------------------------------------
> 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
>
>
>> On Apr 12, 2019, at 3:00 PM, email@hidden wrote:
>>
>> Send Coreaudio-api mailing list submissions to
>> email@hidden
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>> https://lists.apple.com/mailman/listinfo/coreaudio-api
>> or, via email, send a message with subject or body 'help' to
>> email@hidden
>>
>> You can reach the person managing the list at
>> email@hidden
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of Coreaudio-api digest..."
>>
>>
>> Today's Topics:
>>
>> 1. auval only showing apple audiounits (Oliver Larkin)
>>
>>
>> ----------------------------------------------------------------------
>>
>> Message: 1
>> Date: Fri, 12 Apr 2019 11:11:23 +0100
>> From: Oliver Larkin <email@hidden>
>> To: email@hidden
>> Subject: auval only showing apple audiounits
>> Message-ID: <email@hidden>
>> Content-Type: text/plain; CHARSET=US-ASCII
>>
>> Since a few weeks ago when I type auval -a on the command line I only see
>> Apple AUs.
>>
>> Logic X however, when it runs auval can find the 3rd party AUs.
>>
>> Anyone know how to fix that? This is on 10.13
>>
>> Thanks,
>>
>> Oli
>>
>>
>> ------------------------------
>>
>> Subject: Digest Footer
>>
>> _______________________________________________
>> Coreaudio-api mailing list
>> email@hidden
>> https://lists.apple.com/mailman/listinfo/coreaudio-api
>>
>>
>> ------------------------------
>>
>> End of Coreaudio-api Digest, Vol 16, Issue 29
>> *********************************************
>
>
>
> ------------------------------
>
> Message: 2
> Date: Wed, 17 Apr 2019 07:21:05 -0400
> From: Bernie Maier <email@hidden>
> To: email@hidden
> Subject: Re: auval only showing apple audiounits
> Message-ID: <email@hidden>
> Content-Type: text/plain
>
> On Wed, 17 Apr 2019, at 5:03 AM, James Baxter wrote:
>
>> ERROR: Cannot get Component's Name strings
>> ERROR: Error from retrieving Component Version: -50
>
> Just a shot in the dark here, but those specific messages make me wonder if
> you are still using the old Component Manager to identify your Audio Unit and
> whether that long-deprecated Component Manager has finally been killed off
> for the 64-bit world.
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> Coreaudio-api mailing list
> email@hidden
> https://lists.apple.com/mailman/listinfo/coreaudio-api
>
>
> ------------------------------
>
> End of Coreaudio-api Digest, Vol 16, Issue 32
> *********************************************
_______________________________________________
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