Re: Transport start/stop for Effect Units needed
Re: Transport start/stop for Effect Units needed
- Subject: Re: Transport start/stop for Effect Units needed
- From: Urs Heckmann <email@hidden>
- Date: Fri, 16 May 2003 09:52:42 +0200
Am Mittwoch, 14.05.03, um 20:24 Uhr (Europe/Berlin) schrieb Howard Moon:
Unfortunately, that does not work when using the FXpansion AU wrapper,
because the transport state is not known. I would think that the
transport state ought to be available, but the doc's say it's only for
an Output unit, which we don't get with the wrapper product.
Please don't get me wrong, I don't wanna rant here, but I have to
release some air, and your post offers the occasion. (I do not mean to
be pointing at you, I mean this in general)
I think it wouldn't be appropriate to change the APIs to get a
workaround running for those who do not want to use the APIs.
I like Angus' wrapper very much. But I see now that some companies are
going to license his technology to get rid of the need to convert their
stuff from VST to AU. If you follow user postings on sites like
osxaudio.com, you'll see that a lot of musicians will consider that as
an imposture. Any company that ships "AudioUnits" which in fact are
VSTs sent through the wrapper will gather annoying feedback. Let it be
legitimate or not.
I don't see much of a difference between "wrapped VST" and "true
AudioUnit". - Except for, like consensus of buggyness in VST world,
every other plugin that's coded strictly for Cubase SX will cause some
sort of problems with the wrapper and possibly bring another
modification request for AU on the table.
Howard, in your case it's a bug in Cubase SX that AU should take care
of? - I'd say, it's the wrong address here. - As Bill spoke word in the
beginning, don't do workarounds for buggy hosts. Keep the standard
clean. - Don't repeat the mistakes experienced elsewhere!
Well, may it be that the "transport info" would be a useful thing.
Could be. But the base of arguments should be something different from
workaroundings.
However, any additional effort made to support this "subversion" of
AudioUnits standard wouldn't make the situation better (I mean lack of
AUs). - It's not hard to write AUs, and the day VSTGUI goes open source
(under BSD license, I've heard), any techy problems will be gone,
especially those with Emagic's porting stuff (well, if they manage to
improve that a bit as well).
Sorry I had to say this (after long telephone calls with another guy
who just prove me right last weekend).
Cheers,
;) Urs
_______________________________________________
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.