RE: Communication across AUs
RE: Communication across AUs
- Subject: RE: Communication across AUs
- From: "Timo K" <email@hidden>
- Date: Fri, 2 Jul 2010 19:44:52 +0200
> -----Original Message-----
> From: coreaudio-api-bounces+tk.coreaudio=access-
> email@hidden [mailto:coreaudio-api-
> bounces+tk.coreaudio=email@hidden] On Behalf Of Alex
> Weiss
> Sent: Thursday, July 01, 2010 3:21 PM
> To: tahome izwah
> Cc: coreaudio-api
> Subject: Re: Communication across AUs
>
> Using a distributed notification center was my first thought as well,
> but I'm a little concerned about performance. For now, I'm using a
> regular notification center, although that assumes that both plug-ins
> have the same address space. I'll also look into shared memory or some
> other IPC procedures. I think what it boils down to is that at some
> point I'll have to implement all three options and test them in terms
> of their robustness and performance.
You will have no fun at all:
- you cannot determine the execution order of the plugin instances
- you cannot determine if the host decides not to render an instance
- buffer sizes of instances in different tracks will vary
- song position in different instances will differ (in the same 'moment',
depending on track delay, other plugins in the track forcing delay
compensation, threading)
- communication via IPC is useless (no performance)
- In-Process-communication is not that easy since you need to keep it lock
free
there is even more to that issue...
best
-timo
_______________________________________________
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