• 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: Presets etc.
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Presets etc.


  • Subject: Re: Presets etc.
  • From: "Michael Kleps [reFX]" <email@hidden>
  • Date: Thu, 29 Apr 2004 17:07:11 +0200

Marc,

But your proposed "general" solutions are not general, they are
VST-specific, and that's the problem. There are some places where VST and
AU simply do not operate the same, and special attention to each is
needed. I really don't know what the hell you keep referring to about me
saying "you have to do my way, I don't care what you want." I'm trying to
suggest a solution to make your users happy, but yes, I'm not suggesting
anything to make you happy.

My problem with you is that you decide what is best, not the user. If you don't need the (optional) functionality I request, why don't you stop moaning? Why do you care? I am not rallying for support here, I just wanted to make it clear to Apple and involved parties that there are developers out there who think it might be a good idea to make available what people are used to for several years now.

Stop your "everybody who thinks different than me is an idiot" crusade and allow people to "think different" ;^)

I don't want to take anything away from you, I just would like the functionality people are used to for years added into the API. You must admit that the preset management in VST is pretty simple, for the host AND the plugin. In the minimum case you need four functions. Two of them are already in AU (get/setParameter), two new ones would need to be added (get/setProgram). The SaveState and RestoreState just would need an additional parameter (bool isBank).

That is a no-brainer to implement for the host and plugin side. It could be optional. It's *added* value. Nothing gets lost. The host can still provide a list of files on the HD and overwrite the edit buffer (like it does now). Just think about giving people a choice.

Hope you can be more constructive in the future instead of flaming me for wrong assumptions I made because of the poor docs and me beeing so stupid to assume that such a simple and established concept like "banks" exists in AU world.

-Mike
_______________________________________________
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: Presets etc. (From: Marc Poirier <email@hidden>)

  • Prev by Date: Re: Presets etc.
  • Next by Date: Re: Presets etc.
  • Previous by thread: Re: Presets etc.
  • Next by thread: CoreAudio swiki
  • Index(es):
    • Date
    • Thread