[gmpi] Re: Use case scenario for Control Parameters vs MIDI in GMPI

  • From: Sebastien Metrot <meeloo@xxxxxxxxxx>
  • To: gmpi@xxxxxxxxxxxxx
  • Date: Wed, 16 Jun 2004 17:19:39 +0200

The host can do many things but it doesn't know about a particular UI and so can't decide when to start or not to start this particular event capture unless the plugin code explicitely asks for it. Steve's proposal suits my need and I think that provision should explicitely be made in the specs for this use case. Then the "only GMPI events" solution suits me as long as smart params value are used (floating points midi note numbers in order to have a fast mapping...).

Thanks, going back to lurk mode :).

Sebastien


Vincent Burel wrote:


----- Original Message ----- From: "Steve Harris" <S.W.Harris@xxxxxxxxxxxxxxx>
To: <gmpi@xxxxxxxxxxxxx>
Sent: Wednesday, June 16, 2004 4:57 PM
Subject: [gmpi] Re: Use case scenario for Control Parameters vs MIDI in GMPI





On Wed, Jun 16, 2004 at 04:52:02 +0200, Sebastien Metrot wrote:


Hi all,

I've been following the MIDI vs No Midi argument (should I say flame


war?).


I understand the points that have been made so far and I would
personally think the "Control Parameters defined as a superset of MIDI"
would be the best solution.
However I need a clarification from the brains on this list about the
way one the the very basic features of most morden plugins can work:
Our users want to be able to easily link their control surface elements
to our plugins parameters. What most plugins out there do is let the
user select the corresponding knob (right click + menu, or double click
like reason, whatever...) and link the NEXT incomming midi message as
the source of events for this params. I feel this kind of flexibility is


This is exactly the kind of thing its designed to support. The difference
is that the host would do the MIDI->GMPI mapping, not the plugin.



it's also already done in Cubae for exemple, when the host can map a MIDI controler (or whatever) to a parameters of the even VST 1.0 plug-in format. In a similar way, this can be also done in the GMPI architecture, by presenting a Parameters Port. with a public protocole that the host can understand, interpret and use. But this does not forbid to the plug-in to present a MIDI port if wanted... That's why i don't understand the actual battle around MIDI or NOT MIDI.

VB




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