RE: Cubase SX != AU
RE: Cubase SX != AU
- Subject: RE: Cubase SX != AU
- From: "Mikael Hillborg" <email@hidden>
- Date: Mon, 20 Oct 2003 09:34:44 +0200
Urs Heckmann wrote:
>
>
If VST3 gets anywhere close to what was said there, AU support would be
>
a no-brainer to add to that engine (or write a wrapper, which would
>
basically be an Opcode-converter, so my impression). Well, that was
>
back in May or so and not official, so I can't say for sure.
Perhaps, yes, but I assume it might take some time before the VST3 spec
if finalized. And then it'll take some time after that to provide the AU
support on top of that. So to me it sounds like it'll take some time and
that the exclusion of AU even in SX 2.0 is a kind of strategy.
A plugin-type war going on...? On the other hand, AU is for Mac OS X as
what DirectX/DirectSound is for Windows so I don't see any particular
reason to exclude AU support. It certainly won't hurt the strength and
position of the VST framework. People won't use AU plugins only, just
because they're on Mac.
>
I think it would make a difference if users claimed demand.
>
Unfortunately, I don't think users have strong reasons to do so.
Well, I'd like to compare with some Windows hosts, which support both
DirectX plugins and VST plugins. So why not...
Mikael
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.