[gmpi] Re: MIDI: Proposed Reqs (try #2)
- From: Mike Berry <mberry@xxxxxxxxx>
- To: gmpi@xxxxxxxxxxxxx
- Date: Wed, 07 Jul 2004 11:04:35 -0600
Chris Grigg wrote:
3.15. MIDI
Req. 68: NO DRAG ON PURE GMPI - In general, none of the following MIDI
requirements should be met by handicapping the abstract design of other,
non-MIDI-related, 'pure GMPI' requirement areas; in particular, MIDI's
well-known limitations in terms of integer field sizes, message model,
etc. should not be taken as bounds on GMPI per se.
Req. 69: EXTERNAL MIDI IN & OUT - It must be possible for hosts to
control plugs from arbitrary MIDI 1.0 HW instrument controllers, HW
control surfaces, and SW outside the GMPI graph (though the in-graph
data need not necessarily be in pure MIDI 1.0 format).
This req, though I understand it, is a bit convoluted. Can I suggest:
Req. 69: EXTERNAL MIDI IN & OUT - Hosts are not required to support any
external control protocol, including MIDI. However, it must be possible
to write a host in which users can control plugs from arbitrary MIDI 1.0
HW instrument controllers, HW control surfaces, and SW outside the GMPI
graph (though the in-graph data need not necessarily be in pure MIDI 1.0
format). This includes but is not limited to playing notes, adjusting
parameters, host-side ad hoc 'click-and-wiggle' controller mappings, and
System Exclusive communication. It must also be possible for plugs to
communicate to arbitrary external MIDI devices (including other SW
outside the GMPI graph) by effectively emitting MIDI 1.0 for the host to
route to destinations outside the GMPI graph (though the in-graph data
need not necessarily be in pure MIDI 1.0 format). Plugs must not need to
use platform native MIDI I/O APIs to achieve this, it must be possible
using only the GMPI API.
Req. 77: MIDI-PARAMETER MAPPING - Plugs with MIDI-driven parameters (in
the sense of section 3.11 Parameters) must be able to expose to the host
an arbitrary MIDI-messages-to-parameters map. The map must be
changeable at runtime, for example when the parameter set changes.
Why is this req necessary? Can't the plugin do it itself using an
actor? The host uses its own remapping, but since the MIDI is stapled to
the event, the plugin preprocessor can remap at will, without having to
add a new API element to publish parameter maps.
--
Mike Berry
Adobe Systems
----------------------------------------------------------------------
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:
