[gmpi] Re: preset setting Requirements
- From: "Angus F. Hewlett" <amulet@xxxxxxxxxxxxx>
- To: gmpi@xxxxxxxxxxxxx
- Date: Mon, 17 Nov 2003 14:27:17 -0500 (EST)
On Tue, 18 Nov 2003, Jeff McClintock wrote:
> > > Ahh. Do we need a requirement for this? What is the requirement?
>
> The current state of affairs is:
> - A plugin has several patches/presets (all stored internally), and the host
> can switch between thoses patches (just like a hardware device).
Yes, in VST it's like that... this is an absolute pain in the ass for all
concerned, and one of the WORST design flaws in VST. Other APIs do not
take this approach.
> The host stores banks and patches. The host provides "Save Bank to disk"
> etc.
> The user still sees your plugin has 127 patches. Except you didn't have
> to write the code.
> All that code is written once, bug-free, in the host.
>
> Quite a radical idea. But quite sensible. After all, every plugin has
> patch-management code. Putting that code in the host is a smart idea, your
> plugin is just as good, but you write less code. a win-win situation?
Absolutely... and (imho) not that radical at all.
Regards,
Angus.
----------------------------------------------------------------------
Generalized Music Plugin Interface (GMPI) public discussion list
Participation in this list is contingent upon your abiding by the
following rules: Please stay on topic. You are responsible for your own
words. Please respect your fellow subscribers. Please do not
redistribute anyone else's words without their permission.
Archive: //www.freelists.org/archives/gmpi
Email gmpi-request@xxxxxxxxxxxxx w/ subject "unsubscribe" to unsubscribe
Other related posts:
