• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Known issues with VST-AU based AudioUnits
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Known issues with VST-AU based AudioUnits


  • Subject: Re: Known issues with VST-AU based AudioUnits
  • From: Glenn Olander <email@hidden>
  • Date: Sat, 21 Jun 2003 14:57:19 -0700

Ok, you had your little joke. Surely that's not the SDK you were
referring to when you said:

There are a number of audio units that are exhibiting some bad behaviours that are based on this SDK... If this is something you have used to port a VST plugin to an AU we would like these issues to be fixed by those audio units.

But, this is exactly my point. Apple and Emagic seem to not
be taking responsibility for the VST-AU SDK? If you (Apple
and Emagic) are no longer supporting it, then please come and
say so. The only thing worse than not supporting it is to
feign support for it.

Glenn



Bill Stewart wrote:
Well... We have an SDK and we do maintain it, diligently I would hope... Its called the CoreAudio SDK and it is available for download by any registered Apple Developer at:

http://developer.apple.com/audio

Bill

On Saturday, June 21, 2003, at 10:15 AM, Glenn Olander wrote:

And, indeed I'm grateful for the heads up.
But if Apple is aware of shortcomings in (their) SDK,
why not fix it?

I get the feeling EMagic and Apple are reluctant to
support the SDK. I think the result has been we've all
been patching it ourselves to fix various problems.
The result is the very inconsistency that Bill is
reporting.

If Apple is concerned about problems in AU's due
to shortcomings in the SDK, I would humbly suggest the
best way to remedy that problem is to fix the SDK, instead
of relying on each developer to devise a fix and apply it.

Glenn


Jeremey Sagan wrote:

These look like problems which could be fixed in the SDK?
If that is true...then why are you telling us this? Why
not just fix the SDK? It is written by a company you now
own :-).
Glenn
If I wrote an AU plug-in that used this SDK, I would be want to know of problems found within it regardless of whether the SDK was fixed or not.

_______________________________________________
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.


-- mailto:email@hidden
tel: +1 408 974 4056

________________________________________________________________________ __
"Much human ingenuity has gone into finding the ultimate Before.
The current state of knowledge can be summarized thus:
In the beginning, there was nothing, which exploded" - Terry Pratchett
________________________________________________________________________ __
_______________________________________________
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.

References: 
 >Re: Known issues with VST-AU based AudioUnits (From: Bill Stewart <email@hidden>)

  • Prev by Date: Re: more AU info and plugins (should be "I need to share data")
  • Next by Date: Re: more AU info and plugins (should be "I need to share data")
  • Previous by thread: Re: Known issues with VST-AU based AudioUnits
  • Next by thread: Re: Known issues with VST-AU based AudioUnits
  • Index(es):
    • Date
    • Thread