[gmpi] Re: 3.14 UIs
- From: "Jeff McClintock" <jeffmcc@xxxxxxxxxx>
- To: <gmpi@xxxxxxxxxxxxx>
- Date: Fri, 4 Jun 2004 14:48:18 +1200
> Only thing I'm left wondering is, did we
> decide the DSP fork does vs. doesn't need to be able to push stuff to
> the GUI fork?
I'm hoping Yes, DSP can generate data destined for GUI.
> Or is the param-change notification requirement meant to
> address that?
There's two cases:
1) Host changes parameter due to automation. Both GUI and DSP are
'receivers'
[Host] --> [GUI]
[Host]-->[DSP]
2) DSP needs to send info to the GUI, like audio VU level, or as in the
Scope example, a captured section of audio to display.
[DSP]->[Host]->[GUI]
Note, this requires a distinction between events sent to the DSP vs events
generated by the DSP.
I call the two directions "input parameters" and "output parameters"
...but I think the term "output parameter" is a bit confusing. Tim called
them "control outputs", that might be a better term.
Jeff
----- Original Message -----
From: "Chris Grigg" <gmpi-public@xxxxxxxxxxxxxx>
To: <gmpi@xxxxxxxxxxxxx>
Sent: Friday, June 04, 2004 1:57 PM
Subject: [gmpi] Re: 3.14 UIs
> This is IMHO a really great description, Jeff. Thanks. To me, it
> feels very close to done. Only thing I'm left wondering is, did we
> decide the DSP fork does vs. doesn't need to be able to push stuff to
> the GUI fork? This makes all GUI-related operations driven by the
> GUI fork. Or is the param-change notification requirement meant to
> address that?
>
> -- Chris G.
>
> > > Well standardising an IPC mechanism which out of process UIs can use
to
> >> talk to the host is much simpler.
> >
> >Agree, Hopefully GMPI can provide the 'plumbing', so that writting an
> >out-of-process plugin is just as easy as an in-process one. The plugin
> >binary should not need networking code.
> >
> >The GUI should be able to:
> >- set any parameter
> >- read any parameter (value & metadata)
> >- It should be notified whenever a parameter changes value and screen
needs
> >updating.
> >- Recall a program.
> >- Store a program
> >- Tell the Host to load or save a bank/program to standard bank file
format.
> >- Tell the host to apply "MIDI learn" to a parameter.
> >
> >All communication is via the host, to allow undo/redo and automation to
work
> >solidly. Parameters may be designated private, to allow data transfer to
> >GUI (waveform displays etc) without exposing that parameter to the user.
> >
> >hope that's reasonable.
> >
> >Best Regards,
> >Jeff
>
> ----------------------------------------------------------------------
> 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:
