[gmpi] Re: Time Summary (was *Ping*)

  • From: "Angus F. Hewlett" <amulet@xxxxxxxxxxxxx>
  • To: gmpi@xxxxxxxxxxxxx
  • Date: Tue, 20 May 2003 15:37:38 -0400 (EDT)

On Tue, 20 May 2003 RonKuper@xxxxxxxxxxxx wrote:

> >>>
> I've come to the conclusion that implementing a pure music event plug is
> not the highest priority of folks on the list.
> <<<

> I disagree.  I would think the MMA member companies would be interested a
> pure music event plugin.  Existing APIs such as MFX and OPT ought to be GMPI
> compatible, and these APIs are MIDI only.

The ultimate question is really, how much does GMPI care about interfacing
with devices outside of the GMPI universe? It's really not too painful to
implement arpeggiators and suchlike in the "events treated the same as
audio blocks, no future knowledge"... a small efficiency hit, that's all.

IMHO, if there is ANY audio rendering going on, this "everything treated
like audio" model is absolutely fine. However, in a MIDI-only graph
situation, you end up with a scenario where, for low latency, the system
must constantly, in effect, poll the graph for data by pumping
process-requests through it. I personally don't have a problem with that -
a MIDI-only graph is going to be so lightweight on CPU anyway, that
polling it every 3-5ms is not a big deal. It is kinda ugly though.

Overall, this really doesn't affect MIDI plug-in implementation at all -
a baseclass can hide it anyways very easily, no problem there. What it
DOES affect more is a MIDI-only host/graph implementation.

Regards,
        Angus.


----------------------------------------------------------------------
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: