Re: Logic does not recognise AU plugins until OSX restart.
Re: Logic does not recognise AU plugins until OSX restart.
- Subject: Re: Logic does not recognise AU plugins until OSX restart.
- From: Bram Bos via Coreaudio-api <email@hidden>
- Date: Mon, 26 Oct 2020 16:44:06 +0000
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=none; dmarc=none; dkim=none; arc=none
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Q1i8dktiVz6g/RsBR1W2MEeJeZPXste3hLM5KNP+290=; b=UumBMZx+eMihnWOJGW8I8vu92FrrIY4cv3jtm9CKYwyLtzSdhChDS3jgmvze84B+2NaRvuSEK82VSyigHSNZ5fSQgxWJa3UgeuddE+Znctnv/hpHsiF/k1GC8Vv2WSBfTDT7YJ9Wsfo77xTaq53nXRsx9cc8QgjW3ksjSHpwJvoHmdW2WIrsxmiHY/JlwUuzmZyLUbvQVInYXErlRhzDZuFOMXX7bNdfQrU3cWNuisEcTyGQwCbfsHO/P3UkYkFAkchtEOPOIzVAiDEnwseHvK5yneCWUUrvtxtCXIm29QquVXHlaNxbW7WJ5xiGDo7xER9FyQf/n96vuKF/PyF7jg==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=BKxywOABEyF2ARVRQPo9F0ZgIk2etWD/H+ZJhdpdWq4yIi6M3Y8bMFnXw4T/Y513M4pxdsdDLCb7Qv+67tUnVk8hWKHZI2IXbSHlqxF5rE04BqSsOcrFu61nkOJEcc8PaLSR3wKKA537se5B8UQSWMb9JBpiWPE4jbzzNKVCpzgTomRVLhF1zAsIQIrt3y0OwsypoXZ55aLPUj5nt424QOrPlUoPmiseMybCA/q2Hp1wwexdVwFEaQZEzXbfrvsLL00xPh0s758iiHhnLttmEGvX2wuWbqtB8HhP2vs+TVSuSOocPOyAFFmTGBKHliBD4NIEfFtAYwmbW+y8aTCQTQ==
- Thread-topic: Logic does not recognise AU plugins until OSX restart.
I'd be very interested in knowing the solution to this issue.
It happens in iOS as well: new customers contacting me that the newly installed
AUv3 doesn't show up in any host. In 99% of the cases a restart solves it, but
by then some will already have left a 1-star review with a message that the app
doesn't work 😕
________________________________
From: audio boy via Coreaudio-api <email@hidden>
Sent: Monday, October 26, 2020 3:15 AM
To: coreaudio-api <email@hidden>
Subject: Logic does not recognise AU plugins until OSX restart.
Having googled, this does seem to be a long standing problem and we
are not the only vendor to be affected by this. However it's clear
from user reports that many AUs are not affected by this and show up
correctly after install. So I would really like to figure out finally
exactly why this happens.
Does anyone know what the official mechanism is? There doesnt seem to
be anything on it in the apple docs.
What might be relevant is that we dont put our AU properties (type,
subtype) etc in the plist, only the .R file, as a result, we are using
the older entry point mechanism. But several major vendors, such as
U-HE are also doing the same, having checked, and these plugins show
up fine after install, at least on my test machine.
Also as you may have seen in my other recent post, we have set an
invalid SubType code (a number instead of a valid FourCC). Could this
be a reason? (But we are unable to change this as doing so makes our
plugins apparently disappear from Logic).
Would really really like to finally solve this problem....
Thanks
_______________________________________________
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
_______________________________________________
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