RE: Sharing data between UI and AU
RE: Sharing data between UI and AU
- Subject: RE: Sharing data between UI and AU
- From: Muon Software Ltd - Dave <email@hidden>
- Date: Wed, 23 Feb 2011 22:29:20 +0000
- Acceptlanguage: en-US, en-GB
- Thread-topic: Sharing data between UI and AU
> Because you have no guarantee that the AU and the host will continue
> to be the same process.
Actually I think it's a pretty good bet for now and quite some time to come.
If any host developer decided arbitrarily to do this, they'd break a vast number of "legacy" plugins that assume their DSP and GUI will run in the same process. With the majority of "legacy" plugins not supporting such a feature, the only way a host could do it would be if they detected and whitelisted plugins that supported full DSP/GUI seperation, and blacklisted the rest. I'd be willing to bet that such a feature wouldn't take off until plugin developers are thoroughly weaned off VST2.4 and have expunged all traces of it from their code bases, and to be quite frank there is very little commercial pressure to abandon it for VST3 (which supports full DSP/GUI seperation) just yet.
> Besides the initial setup, the shared memory area incurs no additional overhead, even within the same process. You just have two sets of virtual pages that map to
> the same physical pages.
The additional overhead is that incurred by developers in the time it would take to change all their existing shared code bases and wrappers to support this feature.
I've heard the argument that says we shouldn't use common code, shared code bases or wrappers to target all the available platforms because each platform has unique features and the result is a lowest-common-denominator experience. However I think that few developers have the luxury of writing plugins that take advantage of all the disparate features of all the platforms out there, so the lowest-common-denominator-experience dominates now and for quite some time to come.
Kind regards
Dave
_______________________________________________
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