[gmpi] Re: closing reqs 3.8
- From: Chris Grigg <gmpi-public@xxxxxxxxxxxxxx>
- To: gmpi@xxxxxxxxxxxxx
- Date: Thu, 29 Jan 2004 18:08:28 -0800
Fine, but I didn't write that. Tim put it in the draft requirements
document and I was responding to him, particularly his comment that
Req 22 is ok, in light of the recent curtailed MIDI thread.
-- Chris G.
Hi Chris,
the notion that a plug-in parameter requires a fixed MIDI Controller number
is obsolete.
Too early to decide that. Some here will agree, some won't. We havn't
discussed MIDI yet.
Best Regards,
Jeff
----- Original Message -----
From: "Chris Grigg" <gmpi-public@xxxxxxxxxxxxxx>
To: <gmpi@xxxxxxxxxxxxx>
Sent: Friday, January 30, 2004 1:31 PM
Subject: [gmpi] Re: closing reqs 3.8
At 4.23...
"If GMPI is to succeed at all, it must be interoperable with the
enormous installed base of MIDI applications, plugins, and devices.
Pure MIDI, however, is too limited for GMPI's use. GMPI plugins and
hosts need more flexibility than simple MIDI can provide. The notion
that a parameter requires a fixed MIDI CC number is obsolete. In the
software world of control signals, any CC should be able to go to any
parameter."
...we should probably define 'pure MIDI' and 'simple MIDI' so people
know which of MIDI's many, many aspects you have in mind there. For
example, the MIDI event message transport layer per se doesn't force
any particular interpretation on any controller number; really its
flexibility can't be beat. Perhaps you're confusing MIDI per se with
unfortunate limitations in the ways MIDI has been implemented in
previous OS and plug-in APIs?
Can I suggest replacing the above with the following?:
"If GMPI is to succeed at all, it must be interoperable with the
enormous installed base of MIDI applications, plug-ins, and devices.
However GMPI's handling of MIDI must take care to preserve the
inherent flexibility of the MMA MIDI specifications, and avoid the
numerous harmful assumptions and other limitations on MIDI message
contents and semantics from which some previous OS and plug-in APIs
have suffered. In particular, the notion that a plug-in parameter
requires a fixed MIDI Controller number is obsolete; in the software
world of routable control signals, any MIDI controller message source
should be able to drive any GMPI plug-in control (parameter)."
> -- Chris G.
----------------------------------------------------------------------
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
- Follow-Ups:
- [gmpi] Re: closing reqs 3.8
- From: Jeff McClintock
- [gmpi] Re: closing reqs 3.8
- From: Tim Hockin
- References:
- [gmpi] Re: Reqs 3.8 Events - ramped events
- From: Tim Hockin
- [gmpi] Re: Reqs 3.8 Events - ramped events
- From: Steve Harris
- [gmpi] Re: Reqs 3.8 Events - ramped events
- From: David Olofson
- [gmpi] Re: Reqs 3.8 Events - ramped events
- From: Steve Harris
- [gmpi] Re: Reqs 3.8 Events - ramped events
- From: Tim Hockin
- [gmpi] Re: closing reqs 3.8
- From: Tim Hockin
- [gmpi] Re: closing reqs 3.8
- From: Chris Grigg
- [gmpi] Re: closing reqs 3.8
- From: Jeff McClintock
Other related posts:
- » [gmpi] Re: closing reqs 3.8
- » [gmpi] Re: closing reqs 3.8
- » [gmpi] Re: closing reqs 3.8
- » [gmpi] Re: closing reqs 3.8
- » [gmpi] Re: closing reqs 3.8
- » [gmpi] Re: closing reqs 3.8
- » [gmpi] Re: closing reqs 3.8
- » [gmpi] Re: closing reqs 3.8
- » [gmpi] Re: closing reqs 3.8
- » [gmpi] Re: closing reqs 3.8
- » [gmpi] Re: closing reqs 3.8
- » [gmpi] Re: closing reqs 3.8
- » [gmpi] Re: closing reqs 3.8
the notion that a plug-in parameter requires a fixed MIDI Controller numberis obsolete.
Too early to decide that. Some here will agree, some won't. We havn't discussed MIDI yet.
Best Regards, Jeff
----- Original Message ----- From: "Chris Grigg" <gmpi-public@xxxxxxxxxxxxxx> To: <gmpi@xxxxxxxxxxxxx> Sent: Friday, January 30, 2004 1:31 PM Subject: [gmpi] Re: closing reqs 3.8
At 4.23...> -- Chris G.
"If GMPI is to succeed at all, it must be interoperable with the enormous installed base of MIDI applications, plugins, and devices. Pure MIDI, however, is too limited for GMPI's use. GMPI plugins and hosts need more flexibility than simple MIDI can provide. The notion that a parameter requires a fixed MIDI CC number is obsolete. In the software world of control signals, any CC should be able to go to any parameter."
...we should probably define 'pure MIDI' and 'simple MIDI' so people know which of MIDI's many, many aspects you have in mind there. For example, the MIDI event message transport layer per se doesn't force any particular interpretation on any controller number; really its flexibility can't be beat. Perhaps you're confusing MIDI per se with unfortunate limitations in the ways MIDI has been implemented in previous OS and plug-in APIs?
Can I suggest replacing the above with the following?:
"If GMPI is to succeed at all, it must be interoperable with the enormous installed base of MIDI applications, plug-ins, and devices. However GMPI's handling of MIDI must take care to preserve the inherent flexibility of the MMA MIDI specifications, and avoid the numerous harmful assumptions and other limitations on MIDI message contents and semantics from which some previous OS and plug-in APIs have suffered. In particular, the notion that a plug-in parameter requires a fixed MIDI Controller number is obsolete; in the software world of routable control signals, any MIDI controller message source should be able to drive any GMPI plug-in control (parameter)."
---------------------------------------------------------------------- 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.
- [gmpi] Re: closing reqs 3.8
- From: Jeff McClintock
- [gmpi] Re: closing reqs 3.8
- From: Tim Hockin
- [gmpi] Re: Reqs 3.8 Events - ramped events
- From: Tim Hockin
- [gmpi] Re: Reqs 3.8 Events - ramped events
- From: Steve Harris
- [gmpi] Re: Reqs 3.8 Events - ramped events
- From: David Olofson
- [gmpi] Re: Reqs 3.8 Events - ramped events
- From: Steve Harris
- [gmpi] Re: Reqs 3.8 Events - ramped events
- From: Tim Hockin
- [gmpi] Re: closing reqs 3.8
- From: Tim Hockin
- [gmpi] Re: closing reqs 3.8
- From: Chris Grigg
- [gmpi] Re: closing reqs 3.8
- From: Jeff McClintock