[gmpi] Re: MIDI: Common event coding
- From: Steve Harris <S.W.Harris@xxxxxxxxxxxxxxx>
- To: gmpi@xxxxxxxxxxxxx
- Date: Wed, 23 Jun 2004 22:29:34 +0100
On Wed, Jun 23, 2004 at 11:05:59 -0700, Chris Grigg wrote:
> Off hand I can't think of any obvious reason why this couldn't be
> done, if there's enough support. Though maybe I take that back,
> since OSC messages are totally open-ended -- any string could be a
> new message so you can't pre-determine a cross-coding -- as opposed
> to MIDI, where the message code set is fixed and known. See, for
> Mike the important thing is that the expanded message and the stapled
> MIDI are in sync, have the same info, which I .think. is what I
> showed, I hope, whereas it could be hard to make that promise with a
> free-form message code set -- not just OSC, but any protocol with
> that characteristic.
Right, but theres no natural mapping for the universe of OSC messages into
GMPI, so its going to be some kind of relevant subset that can be mapped,
and hence could be stapled. It doesnt seem any more useful than stapled
MIDI though ;)
- Steve
----------------------------------------------------------------------
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:
