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: Robert Grant <email@hidden>
- Date: Fri, 25 Oct 2002 12:05:26 -0400
Hi Art,
The only thing that's stopping me from agreeing with you is that there's
no way to differentiate the .plist files for an AU without looking
inside
one. What you're suggesting implies that there will not be a
corresponding
quick selection list for user presets akin to picking the factory
presets.
If everyone is happy with making the user pull up a file selection box
every time
they want to choose a user preset and potentially telling them that
they're trying to
load an incompatible preset (because we won't know until we look
inside) then I
guess the argument is moot.
To me, though, it sounds a bit un-Mac like.
Robert.
On Friday, October 25, 2002, at 10:09 AM, Art Gillespie wrote:
Oh man, I completely missed this thread. And I've got an alternative
option: None.
I think someone's got their head around this the wrong way. Presets
are user documents, period. These options of 'where to store them'
indicate that they're being thought of as components, which they most
certainly are NOT. I don't want Project Builder saving my source files
in my preferences directory (or even making decisions about the layout
of my source tree) and I don't want Word bundling all my .doc's in a
single file in my Preferences directory.
If a user wants to be able to share his presets among his apps (or his
colleagues), it's not too much to ask him to manage them himself (e.g.
setting up his own presets folder with subfolders for apps). Also, the
notion of a global list of available presets for a given plug-in is
absolutely absurd. I've got nearly 300 (hard-earned) presets for
Waves' Ren Reverb... and there's no expletive way I want to see them
all in a drop-down list at once. I'd rather load a bank from a
directory location that I set.
So what's the big deal with this? Why try to enforce preset management
schemes on the user (and complicate a standard?). Hosts should simply
give users the option to load/save presets/banks in the location of
their choice... IMNSHO the only thing that's necessary is
standardization of bank/preset file format.
Best,
Art
0xBA
On Thursday, October 24, 2002, at 09:50 PM, Robert Grant wrote:
Option 3. Save the preset in a preferences dictionary in
Library/Preferences, using the
bundle id as the filename. Presets for an individual AU would all be
stored in the
same preferences file.
_______________________________________________
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.
_______________________________________________
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.