[gmpi] Re: 3.15 MIDI (What does it mean to be a plugin)
- From: Tim Hockin <thockin@xxxxxxxxxx>
- To: gmpi@xxxxxxxxxxxxx
- Date: Mon, 21 Jun 2004 20:58:48 -0700
On Tue, Jun 22, 2004 at 03:50:53PM +1200, Jeff McClintock wrote:
> > I'm willing to go one further and suggest that plugins might actually
> > generate MIDI output. Consider a sw proxy for a MIDI synth. The software
> > UI might look just like the synth. You can control the synth by
> > controlling the software. In this case it is a proxy plugin of sorts.
>
> Yes, the very interesting thing is, that MIDI need not travel through the
> GMPI graph (into other plugins).
>
> That's what I was getting at with my Firewire example. Imagine the same
> thing exactly, except the synth is connected to the PC via Firewire or USB.
> Again, not a problem to write a proxy.
>
> Yet there's no Firewire in the GMPI graph.
Yes. The slight difference that I see is that perhaps (!) MIDI output
should be part of the host API. MIDI being what it is, it seems
reasonably useful for the host to provide virtualized MIDI output ports to
which plugins could write.
----------------------------------------------------------------------
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:
