[gmpi] Re: Reqs draft
- From: "Angus F. Hewlett" <amulet@xxxxxxxxxxxxx>
- To: gmpi@xxxxxxxxxxxxx
- Date: Wed, 12 Nov 2003 05:47:39 -0500 (EST)
On Tue, 11 Nov 2003, Tim Hockin wrote:
> On Tue, Nov 11, 2003 at 09:50:35AM -0500, Angus F. Hewlett wrote:
> > > I think the concern is for dynamic metadata, as exposed by wrapper
> > > plugins.
> >
> > Agreed, but does this really need to be runtime-dynamic or is a
> > seperate wrapper-config app sufficient? As someone that's been working
> > with this stuff for quite a while, I'm inclined to think that
> > runtime-dynamic wrapping, whilst nice in theory, is a PITA in practise and
> > a breeding ground for instability.
>
> Forcing me to go outside my app is a step in the wrong direction, I think.
Yes, but we're talking about plugins that exist outside of GMPI.
Think about it this way:- if your wrapper configures itself on the fly at
GMPI enumeration time, we suddenly bring ALL the enumeration problems that
FormatX has right in to GMPI-space. I find that unacceptable.
> We're all very quick to fix bugs that we think might occur. I think this
> need to stop :)
I've worked with DX and VST enough to know that these are not bugs that
might occur, but bugs that WILL occur unless we take action to insulate
GMPI from the problems that other platforms suffer from. The problem would
appear to be of a different magnitude on those platforms compared to say
LADSPA.
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:
