Re: Presets etc.
Re: Presets etc.
- Subject: Re: Presets etc.
- From: Marc Poirier <email@hidden>
- Date: Thu, 29 Apr 2004 11:14:23 -0400 (EDT)
Yes yes, I agree with all that Angus says, and he says it better than I
can sometimes manage... :)
Marc
On Thu, 29 Apr 2004, Angus F. Hewlett wrote:
>
At 12:10 29/04/2004 +0200, Michael Kleps [reFX] wrote:
>
>
>There are several ways
>
>to do things and I prefer to have alternatives that do not limit me or
>
>my users. Concerning presets VST can actually do exactly the same and
>
>more than AU and I think having additional, usefull functionality is a
>
>good thing.
>
>
It's NOT a good thing if it:-
>
>
* Complicates and confuses the plugin<->host interface unnecessarily
>
(elegant simplicity is the key there)
>
>
* Removes the onus from the host (where it should be, in this case) to
>
implement this functionality in a way that, if implemented, would benefit
>
ALL plug-ins not just those that happen to have implemented it themselves.
>
>
>Since FXP/FXB file-format is well documented, even a C/C++ beginner can
>
>read/write them and since the chunk format is arbitary you can store
>
>ANY data you want, so there is no good reason NOT to use it, since on
>
>windows so many hosts support it and I don't think it's a good idea to
>
>have 200 different preset formats if the first one was good enough.
>
>
FXP/FXB is hardly an ideal format, but in any case:- for a given plug-in,
>
provided you know the format for both your VST and your AU, an FXP/FXB -->
>
.aupreset batch converter is also something that a C/C++ beginner can manage.
>
>
>I posted my comments to make it known to Apple and involved parties
>
>that banks and writeable presets might be a good idea for future
>
>updates. Saying "I don't need this" doesn't help anybody and doesn't
>
>stop other developers from needing it.
>
>
No, that's true... but at the end of the day, it's not about what the
>
developer needs, but what the user needs (in this case, the ability to
>
change and manage patches in an efficient, fast way). IMHO, it would be a
>
better solution to say "no AU plug-in should have patch management, so, AU
>
host vendors, you'd better get off your backsides and implement decent
>
patch managers in your hosts", rather than adding the extra complexity to
>
the plugin<->host interface that having a "presets-and-banks" architecture
>
built in to the API implies.
>
>
>
Regards,
>
Angus.
>
=======================================================
>
Angus F. Hewlett, Technical Director
>
FXpansion Audio UK Ltd - http://www.fxpansion.com
>
=======================================================
_______________________________________________
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.