[gmpi] Re: 3.15 MIDI

  • From: Chris Grigg <gmpi-public@xxxxxxxxxxxxxx>
  • To: gmpi@xxxxxxxxxxxxx
  • Date: Tue, 15 Jun 2004 16:18:07 -0700

On Tue, Jun 15, 2004 at 04:00:25PM -0400, Paul Davis wrote:
>What else are the REQUIREMENTs?

  * it must be possible for GMPI plugins to deliver MIDI (or other
    unspecified streams of byte-level data) to particular
    destinations.

 without this, its not possible write things that control external MIDI
 h/w, integrate into GMPI, but want tight control over the MIDI data
 delivered to the outside world.


Hrrm, is this really what we want?  Are plugins going to be controlling
external MIDI?  Wouldn't the plugin then be a driver plugin of sorts, with
the actual MIDI driver open (or a host-centric MIDI pseudo driver) ?

Tim

A plug-in is just another functional entity in the studio, like a physical MIDI instrument or an effects box. The host is where it lives, but it should be able to interoperate with all other functional entities in the studio, HW & SW. Limitations on its connectivity options should not be accepted without good reason.

Also, there are plenty of good ordinary regular use cases for a plug processing purely internal MIDI, not just external. For example, host MIDI track --> MIDI strummer plug in --> SW MIDI instrument plug in. Or host MIDI track --> MIDI note number splitter --> two SW MIDI instrument plug ins.

-- 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: //www.freelists.org/archives/gmpi
Email gmpi-request@xxxxxxxxxxxxx w/ subject "unsubscribe" to unsubscribe

Other related posts:

  1. Home
  2. gmpi
  3. Archive
  4. 06-2004