[gmpi] MIDI: Proposed Requirements (wrap up try #1)
- From: Tim Hockin <thockin@xxxxxxxxxx>
- To: gmpi@xxxxxxxxxxxxx
- Date: Wed, 23 Jun 2004 22:57:25 -0700
Woops, I meant to change the subject...
On Wed, Jun 23, 2004 at 02:26:25PM -0700, Tim Hockin wrote:
> So how can we encapsulate what we've been discussing into requirements?
> Obviously, Chris' proposal (with updates as discussed since then, right
> Chris :) will be included or linked to in the More Info section.
Proposed reqs for Section 3.15 "MIDI". I am sure there are more that are
needed, and some rewording. Suggestions?
* GMPI must provide complete interoperability with MIDI controllers. It
must be possible to control plugins within a GMPI graph with MIDI input.
MIDI input must be sent through the host like all GMPI events.
MORE: For every MIDI message, there must be a corresponing parallel in
GMPI. It must be possible to losslessy transcode a MIDI event into a
GMPI event and back. A basic proposal covering the details of this
transcoding has been developed. <link>
* Plugins must be able to expose a preferred MIDI map, which allows the
host to configure some automatic MIDI control of the plugin.
MORE: It's probably OK to limit this MIDI map functionality to the
following MIDI messages: 7-bit CC, 14-bit CC, RPN, NRPN, note-on,
note-off, pitchbend, channel aftertouch, and poly aftertouch.
* Plugins must be controllable through host-based MIDI-learn. This allows
the host to map any incoming MIDI controller to any parameter.
MORE: This is "click and wiggle" functionality. The user selects a
parameter, then sends a MIDI controller message. That MIDI control is
bound to the specified parameter. It's probably OK to limit this
functionality to the following MIDI messages: 7-bit CC, 14-bit CC, RPN,
NRPN, note-on, note-off, pitchbend, channel aftertouch, and poly
aftertouch.
* It must be possible for GMPI plugins to receive MIDI SysEx messages.
GMPI hosts must not modify SysEx messages in any way.
* It must be possible for plugins to send MIDI.
MORE: One possible mechanism for plugins to send MIDI is for hosts to
provide a GMPI->MIDI output plugin. Another possible option is for GMPI
to define a host-based API for accessing virtualized MIDI outputs.
----------------------------------------------------------------------
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: MIDI: Proposed Requirements (wrap up try #1)
- From: Koen Tanghe
- [gmpi] Re: MIDI: Proposed Requirements (wrap up try #1)
- From: Jeff McClintock
- References:
- [gmpi] MIDI: Common event coding
- From: Chris Grigg
- [gmpi] Re: MIDI: Common event coding
- From: Paul Davis
- [gmpi] Re: MIDI: Common event coding
- From: Tim Hockin
- [gmpi] Re: MIDI: Common event coding
- From: Jeff McClintock
- [gmpi] Re: MIDI: Common event coding
- From: Tim Hockin
- [gmpi] Re: MIDI: Common event coding
- From: Tim Hockin
Other related posts:
- » [gmpi] MIDI: Proposed Requirements (wrap up try #1)
- » [gmpi] Re: MIDI: Proposed Requirements (wrap up try #1)
- » [gmpi] Re: MIDI: Proposed Requirements (wrap up try #1)
- » [gmpi] Re: MIDI: Proposed Requirements (wrap up try #1)
- » [gmpi] Re: MIDI: Proposed Requirements (wrap up try #1)
- » [gmpi] Re: MIDI: Proposed Requirements (wrap up try #1)
- » [gmpi] Re: MIDI: Proposed Requirements (wrap up try #1)
- » [gmpi] Re: MIDI: Proposed Requirements (wrap up try #1)
- » [gmpi] Re: MIDI: Proposed Requirements (wrap up try #1)
- » [gmpi] Re: MIDI: Proposed Requirements (wrap up try #1)
- » [gmpi] Re: MIDI: Proposed Requirements (wrap up try #1)
- » [gmpi] Re: MIDI: Proposed Requirements (wrap up try #1)
- » [gmpi] Re: MIDI: Proposed Requirements (wrap up try #1)
- » [gmpi] Re: MIDI: Proposed Requirements (wrap up try #1)
- » [gmpi] Re: MIDI: Proposed Requirements (wrap up try #1)
- » [gmpi] Re: MIDI: Proposed Requirements (wrap up try #1)
- » [gmpi] Re: MIDI: Proposed Requirements (wrap up try #1)
- » [gmpi] Re: MIDI: Proposed Requirements (wrap up try #1)
- » [gmpi] Re: MIDI: Proposed Requirements (wrap up try #1)
- » [gmpi] Re: MIDI: Proposed Requirements (wrap up try #1)
- » [gmpi] Re: MIDI: Proposed Requirements (wrap up try #1)
- » [gmpi] Re: MIDI: Proposed Requirements (wrap up try #1)
- » [gmpi] Re: MIDI: Proposed Requirements (wrap up try #1)
- » [gmpi] Re: MIDI: Proposed Requirements (wrap up try #1)
- » [gmpi] Re: MIDI: Proposed Requirements (wrap up try #1)
- » [gmpi] Re: MIDI: Proposed Requirements (wrap up try #1)
- » [gmpi] Re: MIDI: Proposed Requirements (wrap up try #1)
- » [gmpi] Re: MIDI: Proposed Requirements (wrap up try #1)
- » [gmpi] Re: MIDI: Proposed Requirements (wrap up try #1)
- » [gmpi] Re: MIDI: Proposed Requirements (wrap up try #1)
- [gmpi] Re: MIDI: Proposed Requirements (wrap up try #1)
- From: Koen Tanghe
- [gmpi] Re: MIDI: Proposed Requirements (wrap up try #1)
- From: Jeff McClintock
- [gmpi] MIDI: Common event coding
- From: Chris Grigg
- [gmpi] Re: MIDI: Common event coding
- From: Paul Davis
- [gmpi] Re: MIDI: Common event coding
- From: Tim Hockin
- [gmpi] Re: MIDI: Common event coding
- From: Jeff McClintock
- [gmpi] Re: MIDI: Common event coding
- From: Tim Hockin
- [gmpi] Re: MIDI: Common event coding
- From: Tim Hockin