Re: The Plugin Settings Approach.
Re: The Plugin Settings Approach.
- Subject: Re: The Plugin Settings Approach.
- From: Jay Vaughan <email@hidden>
- Date: Wed, 12 Feb 2003 16:37:10 +0100
Well, as the muso part of me speaking, I find this solution a little bit
like using a blowtorch to light a candle. In my songs, I use tons of
plugins, and I would say that probably less than 1% of the settings that I
come up are useful in any other context than the specific track of that
specific song. What I would be left with, using your approach, it a
folder full of thousands of settings with filenames using some obtuse hash
naming system and I would never be able to find the 0.6% of useful presets
in that overflowing folder!
Well, I don't see it that way I guess, so this is a stylistic
conflict of ideas, more than anything.
I've been in plenty of studio environments where they *want* to use
the same Reverb settings, or compression, for different projects.
If I come up with some setting while working
on a song that I think is really generally useful, then I export a preset.
Ah, gotcha.
Please don't be offended by my disagreement, I respect your ideas and
definitely do recognize the problems that you're trying to address and
that they are real, but I think that your proposed solution would create
new problems that are worse than the ones that are being solved.
The feeling is mutual. I mean no offense, I'm just proferring a
different view on this Plugin scenario. However, I see the wisdom of
bundling plugin settings with project files, too ...
On this basis, lets just drop it then.
--
j.
Jay Vaughan email@hidden
>>music:technology:synthesizers - www.access-music.de/
_______________________________________________
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.