Re: Filing of User Presets
Re: Filing of User Presets
- Subject: Re: Filing of User Presets
- From: Robert Grant <email@hidden>
- Date: Thu, 24 Oct 2002 09:21:04 -0400
On Thursday, October 24, 2002, at 08:26 AM, Marc Poirier wrote:
I am somewhat concerned about the need to support this but it seems
limited to synth AUs rather than effects.
What makes you say that?
Well my (admittedly limited) experience tells me that number of synth
presets seem
to be about an order of magnitude larger than effect presets. As an
example I find
that working with the list of presets in a Soundfont quite unpleasant
as they're all
presented in a long list. It would be much nicer if they were grouped
in categories
like Bass or Pad etc.
People have been suggesting this sort of thing, and while it has some
seemingly nice advantages, I don't think it's a good idea to make a
single
file of presets, or at least not to make it the only way. This is
simply
not how musicians use preset files. Look around the internet and you
will
find tons of web page hubs for plugin preset sharing, and that sort of
thing is much easier to do with individual files for each preset rather
than bunched files. For one thing, if the only way was to have a
bunched
file, then when you downloaded one person's preset file for X plugin,
you'd have to trash yours (because you could only use one file). For
another thing, then Jenny Musician, whenever she has a new preset to
share for X plugin, has to delete her single file from the collection
and
then reupload. Perhaps there could be the option for collection files,
but single files need to be possible, too.
I don't think it needs to be has difficult as it sounds in your
example. Apps
would have to support an Import/Export capability for presets but this
is nothing
more than loading or dumping a plist, about 10 lines of code. And if we
have a
standard then I can easily see a framework being provided that
facilitates the
whole thing.
In the UI I think it could work in a host very much like IEs favorites.
You could have a
button on an AU that meant "Add to presets" and it would snapshot the
class info,
provide a dialog/sheet for naming the preset (and perhaps add it to a
preset
group). A "Preset" menu could then list all the presets (with submenus
for groups)
and provide import/export capabilities for the presets (single or
multiple).
I'm going to explore this in my Rax app.
Thanks,
Robert.
_______________________________________________
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.