Re: Change of factory presets in AU initiated by plugin
Re: Change of factory presets in AU initiated by plugin
- Subject: Re: Change of factory presets in AU initiated by plugin
- From: Stefan Gretscher <email@hidden>
- Date: Wed, 11 Dec 2013 02:00:17 +0100
Issuing a propertyChanged(kAudioUnitProperty_PresentPreset, kAudioUnitScope_Global, 0) should do the trick in any up-to-date host.
However, some older host may only recognize the older kAudioUnitProperty_CurrentPreset.
Should a host fail with both, you may be able to work around with kAudioUnitProperty_ClassInfo, but keep in mind that this is actually intended for a different use case.
Best,
Stefan
Am 05.12.2013 um 13:24 schrieb Rolf Wöhrmann <email@hidden>:
> Hi
>
> many plugins have in addition to the host's factory preset selectors also own ones in their UI. If the plugin is performing such a change initiated from its own UI, I'm looking for a way to tell the host (Logic X for ex.) to update its display to the new selected factory patch.
>
> Any clue?
>
> Best
> Rolf
>
> ======
>
> Rolf Wöhrmann
>
> email: email@hidden
> phone: +49 151 23010709
> Twitter: nlogmusic
> web:
> http://www.temporubato.com
> http://www.brokensilicon.com
>
>
>
> _______________________________________________
> 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