[gmpi] Re: Nothing since June?
- From: Jeff McClintock <jeffmcc@xxxxxxxxxx>
- To: gmpi@xxxxxxxxxxxxx
- Date: Fri, 18 Nov 2005 14:32:24 +1300
> so how should the GUI be handled
> for easiest conversion later? I haven't seen *anything* on GMPI
The draft GMPI spec is offline at present unfortunately.
The general gist is, in order to record automation on any control
movements, the host mediates between the GUI and the DSP.
[GUI]<-->[Host]-->[DSP]
This contrasts with VST where DSP and GUI are more tightly coupled.
In order to accommodate different windowing systems and toolkits,
GMPI does not specify how you draw the GUI. I guess you'll be provided
only a window handle (HWND) and an Interface to the host...
IGmpiHost->SetParameter(..) // pseudo code
..in turn your GUI exposes it's own interface to the host, this provides
for host-automation of the gui parameters...
IGmpiGui->OnParameterUpdate(...)
With VST plugins, VSTGUI is a separate SDK to ease GUI construction.
I'm not familiar with VSTGUI but I imagine we can connect VSTGUI to GMPI
somehow, perhaps via an adapter.
So you could either write a GUI-less plugin, or use VSTGUI if that suits.
I'm attempting to write my own Host<-->GUI interface at present. The
current design supports:
-Getting and Setting: float, int, bool, raw-binary, and string parameters.
-Displaying a pop-up menu above a control on behalf of the host
"MIDI-Learn|MIDI Un-Learn|etc".
Anyhow that's my take on the GMPI GUI so far, hope I'm not out-of-line.
Best Regards,
Jeff
BobF wrote:
-----Original Message-----
From: gmpi-bounce@xxxxxxxxxxxxx
[mailto:gmpi-bounce@xxxxxxxxxxxxx] On Behalf Of Jeff McClintock
Sent: Thursday, November 17, 2005 1:55 PM
To: gmpi@xxxxxxxxxxxxx
Subject: [gmpi] Re: Nothing since June?
> Anything you could use a hand with?
Hi Bob,
I guess if you or others here have experience writting
plugins, we need
a simple synth and effect that can be distributed with the SDK.
The pupose being to illustrate how to write a GMPI plugin. The code
should be open source, the DSP techniques should be kept
simple so as to
be easy for newbies to understand.
The initial plugin can be written using an existing standard
(VST, AU,
DSSI), we'll convert it to GMPI as the spec solidifies.
What does you think?
I've got a few tutorial-type ideas. I'll work this around and see what I
can come with.
Anything I do will be with VST on Windows, so how should the GUI be handled
for easiest conversion later? I haven't seen *anything* on GMPI, so I'm not
sure what you guys came up with for GUI support.
Bob
----------------------------------------------------------------------
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
----------------------------------------------------------------------
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:
