[gmpi] Re: MIDI: Proposed Reqs (try #3)
- From: Chris Grigg <gmpi-public@xxxxxxxxxxxxxx>
- To: gmpi@xxxxxxxxxxxxx
- Date: Wed, 14 Jul 2004 11:41:19 -0700
Looks great.
//FIXME: need clarity!
Req. 72: HW/SW STUDIO ROUTING/MANAGEMENT - It must be possible to
effectively route MIDI 1.0 connections (though the in-graph data
need not necessarily be in pure MIDI 1.0 format) between proxied MIDI
HW devices and/or other GMPI plugins in the same GMPI graph, using
only
the GMPI API.
//FIXME: need clarity!
<<<
I think what this is saying is, if you have "pure" GMPI plugins in a
graph being fed by a MIDI host, then the pure plugins need to never
cause MIDI data loss. Chris?
More like: It is a valid application of GMPI to have a graph that
does nothing but enables MIDI connections between units (any
combination of SW and proxied HW), and when used that way, GMPI must
provide performance indistinguishable from MIDI over DIN (except for
the message time quantization/reordering artifacts caused by
repacketizing the MIDI stream).
-- 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
- References:
- [gmpi] Re: MIDI: Proposed Reqs (try #3)
- From: Ron Kuper
Other related posts:
- » [gmpi] MIDI: Proposed Reqs (try #3)
- » [gmpi] Re: MIDI: Proposed Reqs (try #3)
- » [gmpi] Re: MIDI: Proposed Reqs (try #3)
- » [gmpi] Re: MIDI: Proposed Reqs (try #3)
- » [gmpi] Re: MIDI: Proposed Reqs (try #3)
- » [gmpi] Re: MIDI: Proposed Reqs (try #3)
- » [gmpi] Re: MIDI: Proposed Reqs (try #3)
- » [gmpi] Re: MIDI: Proposed Reqs (try #3)
- » [gmpi] Re: MIDI: Proposed Reqs (try #3)
- » [gmpi] Re: MIDI: Proposed Reqs (try #3)
- » [gmpi] Re: MIDI: Proposed Reqs (try #3)
- » [gmpi] Re: MIDI: Proposed Reqs (try #3)
- » [gmpi] Re: MIDI: Proposed Reqs (try #3)
- » [gmpi] Re: MIDI: Proposed Reqs (try #3)
- » [gmpi] Re: MIDI: Proposed Reqs (try #3)
- » [gmpi] Re: MIDI: Proposed Reqs (try #3)
- » [gmpi] Re: MIDI: Proposed Reqs (try #3)
Looks great.
//FIXME: need clarity!
onlyReq. 72: HW/SW STUDIO ROUTING/MANAGEMENT - It must be possible to effectively route MIDI 1.0 connections (though the in-graph data need not necessarily be in pure MIDI 1.0 format) between proxied MIDI HW devices and/or other GMPI plugins in the same GMPI graph, using
the GMPI API.
//FIXME: need clarity! <<<
I think what this is saying is, if you have "pure" GMPI plugins in a graph being fed by a MIDI host, then the pure plugins need to never cause MIDI data loss. Chris?
- [gmpi] Re: MIDI: Proposed Reqs (try #3)
- From: Ron Kuper