[MOD] Moving on with Control Chain
Harry van Haaren
harryhaaren at gmail.com
Tue Nov 11 19:52:40 BRST 2014
On Tue, Nov 11, 2014 at 7:42 PM, Gianfranco Ceccolini <
franconassis at gmail.com> wrote:
> And both Hanspeter as Harry mentioned the use of LV2:Atom but I don't
> think we got the grip here of it yet. Is it possible to exemplify this
To communicate between the DSP and the UI in an LV2 plugin, I send Lv2:Atom
events. These Atom events allow me to pass arbitrary data between the
DSP and UI: Fabla's waveforms are one possible example.
To build a hardware device as a custom UI for an existing LV2 DSP backend,
ControlChain connects the custom hardware to the MOD (and the DSP backend).
Previously (with a "normal" software LV2 UI), Lv2:Atom's are used to
communicate the DSP state to the UI. DSP state is not only control ports:
DSP state can be waveforms, menus, routing-matrix adjustments etc. Custom
data that cannot be identified yet must be able to pass trough the
ControlChain, in both directions.
So the ControlChain needs to facilitate transporting these Lv2:Atoms
between the custom-hardware UI, and the LV2 DSP backend.
I guess i'm trying to ask the question:
How does the control-chain transport Atom's between DSP and "hardware-UI"?
 David Robillard (the LV2 guy) wrote a great paper explaining them for
the Linux Audio Conference of this year, Paper:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Developers