Re: Filing of User Presets - files vs. builtin
Re: Filing of User Presets - files vs. builtin
- Subject: Re: Filing of User Presets - files vs. builtin
- From: Bill Stewart <email@hidden>
- Date: Thu, 24 Oct 2002 11:15:00 -0700
I would completely support this point of view...
I've just take a pass with of doing this with our DLS unit and the only
additional information that we have to save (initially at least) is the name
of the bank that the unit is using.
The bank itself contains all of the information it needs and of course the
synth itself can't work without the correct bank...
(And yes, I'm sure that some synths will have a vast range of parameters -
but if the data is declared static const in your code it isn't a big deal
and is loaded in a separate manner (ie read only data) than executable code)
Factory preset values should be contained within the unit (whether that's a
synth or an effect)... You can store this either as static data in your
component, or as resource files (you can put any file you want in the
resource directory of your component folder), and I don't see a problem with
either approach.
However, what I do see a problem with is additional files floating around a
users system that are factory presets... (More to come on this later...)
I'm still digesting the rest of the comments and trying to understand if
there has been any consensus reached on this matter - if anyone feels like
writing a summary of the ideas presented that would help an overworked
designer here understand:)
Bill
on 24/10/02 5:33 AM, Marc Poirier wrote:
>
Pardon me, Marc is on a roll this morning... ;)
>
>
Okay, I have heard a few of you drop mention of how synth plugins would
>
have SOOO MANY preset files. I just wanna get something straight... Are
>
you folks talking about those shipped with the plugins, or user-made
>
presets? If you're talking about the prior (shipped), then I wouldlike to
>
say that I would hope that plugin-makers would consider using the "factory
>
preset" facilities of AU rather than distributing tons of file-age. For
>
one thing, this means that you won't have to *hope* that hosts find your
>
presets (this hopefully won't be an issue with a standard location) and
>
construct a menu from them. Instead, all of the prests will be nicely
>
built-in to the effect. It's very easy to implement this. I've done it
>
in my AUs in minutes, no problem, and way nicer than making the user
>
manually load preset files (yuck, I always hate that). And the nice thing
>
with AU vs. VST is that presets really are presets, i.e. unchangeable (in
>
VST world, the idea of a "preset" and the user state is all mixed up).
>
>
Marc
>
_______________________________________________
>
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.