[gmpi] Re: MIDI: Common event coding
- From: "Martijn Sipkema" <m.j.w.sipkema@xxxxxxxxxxxxxxxxxx>
- To: <gmpi@xxxxxxxxxxxxx>
- Date: Wed, 23 Jun 2004 18:12:09 +0100
> Having had the night to chew on this, I think that there may be a
> problem with attaching the raw MIDI bytes to the messages. Here is one
> use case:
>
> - Host records a series of MIDI controller messages while sending them
> to the plugin.
>
> - User then edits one of the recorded items and creates a value that is
> illegal to be coded as MIDI (controller value 64.01171875, or halfway
> between 2 14 bit numbers).
>
> - Host then plays the recorded data to the plugin. It has two choices:
> leave off the raw MIDI for this event, or quantize it to MIDI.
This problem wouldn't arise when MIDI was treated as MIDI.
Why can't a plugin just have one or more MIDI in/out ports just as
with audio and still have the MIDI inputs control the plugin? I see
only disadvatages to merging control into a single protocol and thus
no longer using standard MIDI.
--ms
----------------------------------------------------------------------
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:
