> For the out of process comms OSC seems like a good candidate. Yeah, no need to reinvent OSC. In fact why not retain the OSC syntax for in-process GUIs too. Replace TCP with something more direct, like simple function calls into the host. That way both remote and local GUIs become essentially the same thing (with different 'transport' mechanisms). Running a GUI remotely then becomes a case of inserting a TCP wrapper between GUI and Host. The plugin dosn't need to know. OSC... "for example, a message's address pattern might be /voice/3/freq, its type string might indicate that there is a single floating-point argument, and the argument might be 261.62" Jeff ----- Original Message ----- From: "Steve Harris" <S.W.Harris@xxxxxxxxxxxxxxx> To: "GMPI list" <gmpi@xxxxxxxxxxxxx> Sent: Saturday, May 29, 2004 3:16 PM Subject: [gmpi] Re: 3.14 UIs > On Fri, May 28, 2004 at 01:05:50PM -0700, Tim Hockin wrote: > > It's time for topic #3.14 - User Interfaces. > > > > Have at it: > > http://www.gmpi-plugins.org/gmpi/requirements.php#sec_3.14 > > > > There is a lot of stuff there, it has lots of thoughts, but I don't think > > it accurately captures the REQUIREMENTS. > > For the out of process comms OSC seems like a good candidate. We've been > using it for a new linux focused stopgap softsynth api (DSSI), and it > seems to be working well, though its a bit early to tell really. There are > 4 or 5 synths that use it. > > The mechanism is that the UI is lanuched with the URL of hte hosts OSC > method root as an argument (eg. osc.udp://localhost:4444/foo/bar) and the > UI then reigsters with the host (to tell it where it is) and the host can > send messages to inform the UI of parameter changes + tell it to (un)hide > etc., the UI can send parameter change messages to the host. > > The exact mechanism is documented if anyone cares, but it probably doesnt > matter right now. > > - Steve > > ---------------------------------------------------------------------- > 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