Subject: RE: [linux-audio-dev] Problem with XML for LADSPA GUI?
From: Richard W.E. Furse (richard_AT_muse.demon.co.uk)
Date: Fri May 26 2000 - 03:36:51 EEST
I don't think this is quite what I meant (I may have misunderstood).
The GUI library API would allow the host to set and examine the state of
the GUI controls. Whether the host uses TCP, direct memory access or a ball
of string to communicate this data with the DSP (if there is one) is
something the GUI does not need to know about. I don't think we need a
communication 'lib', just an API so the host can talk to the GUI.
-- Richard
-----Original Message-----
From: Benno Senoner [SMTP:sbenno_AT_gardena.net]
Sent: Friday, May 26, 2000 1:05 AM
To: Richard W.E. Furse; Linux Audio Developer Mailing List (E-mail)
Subject: Re: [linux-audio-dev] Problem with XML for LADSPA GUI?
[...]
And yes, about your proposed LADSPA GUI communication features
(get control value etc), I was thinking exactly along these lines.
This lib would use shared mem for local connections and TCP for
remote connecions.
That means full networking support, and full speed (no overhead
compared to monolithic DSP+GUI plugin) in case of DSP part
and GUI part running on the same machine.
thoughts ?
[...]
This archive was generated by hypermail 2b28 : Fri May 26 2000 - 05:57:33 EEST