Re: preventing an Audio Unit from crashing its host
Re: preventing an Audio Unit from crashing its host
- Subject: Re: preventing an Audio Unit from crashing its host
- From: Taylor Holliday <email@hidden>
- Date: Mon, 23 Jul 2012 20:11:13 -0700
Thought I'd revisit this. Does anyone know of a way to have the plugin
GUIs appear as if they're running within my host app, when in fact the
entire plugin is in a separate process?
On Wed, Jul 4, 2012 at 8:13 AM, Paul Davis <email@hidden> wrote:
>
>
> On Tue, Jul 3, 2012 at 8:22 PM, Taylor Holliday <email@hidden>
> wrote:
>>
>> What's the best way to prevent an Audio Unit from crashing the app that's
>> hosting it?
>
>
> there is no best way - there's only one way, which you've already
> identified.
>
> even if you catch all possible signals that would arise from a crash in the
> plugin and then just keep going, you have no idea how safe it is to do so -
> the plugin may have invalidated critical data belonging to host memory.
>
>>
>> If I run the Audio Units in a separate process, then their GUIs would also
>> be in that process, which isn't great.
>
>
> in theory, the AudioUnit spec allows for the GUI to be run in a separate
> process or even on a separate machine. in practice ... not so much. and
> you're right that its not great.
>
_______________________________________________
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