Re: Presets etc.
Re: Presets etc.
- Subject: Re: Presets etc.
- From: "Michael Kleps [reFX]" <email@hidden>
- Date: Wed, 28 Apr 2004 14:59:41 +0200
thanks for clarifiying this. Unfortunatly I have to support VST and AU
and for simplicity I don't want to do any major changes to either
implementation. In fact, I have not modified a single line of code in
the VST version to make the AU version work. I will hence lie to the
host and tell him that I have no factory presets at all. Then the user
is forced to use my internal preset-management that is a LOT more
flexible (IMHO) then the AU one (presets can be changed and organized
in banks). VST handles presets like a RAM bank, so the user, not the
host, can decide what to do with it.
???
Most users who I have dealt with prefer the AU approach to presets and
find the VST "programs" concept to be confusing and lead to undesired
behavior. But I really don't see how one case the user decides what
happens and the other the host decides, that's a weird take on it...
Then you have different customers, but this could be from the different
platforms we work for. Most of my customers are PC users which use VST
and thus they are used to the VST behaviour. I find the AU behaviour
very confusing and limiting. I have several AU beta-testers that
complained that their preset is always overwriting the first factory
preset and that when the load another soundbank (through the supplied
internal load functions) that the preset list in logic is not updated
to reflect this. Seems that even my Mac AU customers are used to the
VST behaviour. Even hardware synthesizers have a RAM bank and not just
one slot. And when you do sysex dumps you always have the choice to
dump only the current preset or the entire bank.
Anyway, I was lacking this information and was thus making false
assumptions. I will now lie to the host, provide my own load/save
functions (for presets AND banks, all in good old compatible FXP/FXB
format) and treat a "state" as a complete bank, so the user can use
program-changes to switch between several of HIS presets within one
bank. This is called "total recall" (saving *everything* related to the
plugin in the song) and this total recall functionality is NOT included
in AUl.
I don't think leaving very usefull functionality out of AU was a good
idea and I would love to see this included. How about a new property?
"Presets are writable" and "Can save banks"? There is nothing to loose.
Cheers,
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.