[gmpi] Re: 3.12 wrap-up
- From: "Koen Tanghe" <koen@xxxxxxxxxxxxxxxxxxx>
- To: <gmpi@xxxxxxxxxxxxx>
- Date: Thu, 20 May 2004 02:24:38 +0200
On Thursday, May 20, 2004 12:23 AM [GMT+1=CET],
Jeff McClintock <xxxjeffmcc@xxxxxxxxxxxxx> wrote:
>> Something that does matter (I think), is that it says that the host is
>> responsible for doing the mapping. I'm just wondering: won't there be
>> cases where it would make more sense for the receiving plugin to do
>> decide on the mapping depending on what it is receiving from?
>
> Hi Koen,
> My preference is no. If my plugin has a parameter that ranges from (for
> example) 0 to 10, then that's what i want to receive.
Preferably, yes.
> I don't want to recieve different range and have to map it myself. I
> don't want to have to write a bunch of if-else statements to handle
> conversions from any arbitary type either.
In most cases, you wouldn't need to, of course.
> I would prefer the conversion to be external. SynthEdit handles this type
> of thing via seperate plugins. i.e. there is a "Float to Bool" plugin,
> and a "Float to Text" plugin, which has options like "Number of Decimal
> Places".
Ah, OK. That seems to be what was called the "remapper" plugin in one of my
previous mails.
> The fact is, conversions are rare, and when you do need to convert, it's
> nice to have a pre-written object with plenty of options.
Oh yes, I agree that lots of standard pre-written conversions should be
available. I was just trying to think of cases where that wouldn't be good
enough and avoid that a plugin developer just can't do anything about that.
But I still haven't thought of any real cases, so I guess it may just be
some "worst case/what if" thinking ;-)
> My feeling is that the need to convert parameter types is more relevant in
> modular hosts anyhow, and not really a concern for the mainstream.
Yeah, you're probably right.
Koen
PS
Does anyone happen to know more about the AU mappings?
----------------------------------------------------------------------
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: http://www.freelists.org/archives/gmpi
Email gmpi-request@xxxxxxxxxxxxx w/ subject "unsubscribe" to unsubscribe
- References:
- [gmpi] Re: 3.12 Control I/O
- From: Chris Grigg
- [gmpi] Re: 3.12 Control I/O
- From: Tim Hockin
- [gmpi] Re: 3.12 Control I/O
- From: Chris Grigg
- [gmpi] Re: 3.12 Control I/O
- From: Tim Hockin
- [gmpi] Re: 3.12 Control I/O
- From: Jeff McClintock
- [gmpi] Re: 3.12 Control I/O
- From: Tim Hockin
- [gmpi] Re: 3.12 Control I/O
- From: Chris Grigg
- [gmpi] Re: 3.12 Control I/O
- From: Tim Hockin
- [gmpi] Re: 3.12 wrap-up
- From: Tim Hockin
- [gmpi] Re: 3.12 wrap-up
- From: Chris Grigg
- [gmpi] Re: 3.12 wrap-up
- From: Tim Hockin
- [gmpi] Re: 3.12 wrap-up
- From: Koen Tanghe
- [gmpi] Re: 3.12 wrap-up
- From: Jeff McClintock
Other related posts:
- » [gmpi] Re: 3.12 wrap-up
- » [gmpi] Re: 3.12 wrap-up
- » [gmpi] Re: 3.12 wrap-up
- » [gmpi] Re: 3.12 wrap-up
- » [gmpi] Re: 3.12 wrap-up
- » [gmpi] Re: 3.12 wrap-up
- » [gmpi] Re: 3.12 wrap-up
- [gmpi] Re: 3.12 Control I/O
- From: Chris Grigg
- [gmpi] Re: 3.12 Control I/O
- From: Tim Hockin
- [gmpi] Re: 3.12 Control I/O
- From: Chris Grigg
- [gmpi] Re: 3.12 Control I/O
- From: Tim Hockin
- [gmpi] Re: 3.12 Control I/O
- From: Jeff McClintock
- [gmpi] Re: 3.12 Control I/O
- From: Tim Hockin
- [gmpi] Re: 3.12 Control I/O
- From: Chris Grigg
- [gmpi] Re: 3.12 Control I/O
- From: Tim Hockin
- [gmpi] Re: 3.12 wrap-up
- From: Tim Hockin
- [gmpi] Re: 3.12 wrap-up
- From: Chris Grigg
- [gmpi] Re: 3.12 wrap-up
- From: Tim Hockin
- [gmpi] Re: 3.12 wrap-up
- From: Koen Tanghe
- [gmpi] Re: 3.12 wrap-up
- From: Jeff McClintock