I have an issue with the suggested protocols as I understand them. In fact, I would like to be able to say "take this engine and pass those parameters" with generic GUIs. Because if someone comes with a cool XML-GUI reader, and that I'm too lazy to provide an ad hoc GUI, it would be interesting to write a simple XML GUI description and specifiy that the GUI program should be /usr/bin/xmlread with option plugin.xml
- Re: [linux-audio-dev] LADSPA C... Taybin Rutkin
- Re: [linux-audio-dev] LADSPA C... Richard Guenther
- Re: [linux-audio-dev] LADSPA C... Paul Davis
- Re: [linux-audio-dev] LADSPA C... Steve Harris
- Re: [linux-audio-dev] LADSPA C... Richard Guenther
- Re: [linux-audio-dev] LADSPA C... Steve Harris
- [linux-audio-dev] MARSYAS framework for Compute... George Tzanetakis
- [linux-audio-dev] examples? Tony Lambley
- Re: [linux-audio-dev] examples? Paul Davis
- RE: [linux-audio-dev] examples? Guenther Sohler
- Re: [linux-audio-dev] LADSPA Control GUI metadata xfm
- Re: [linux-audio-dev] LADSPA Control GUI metadata Steve Harris
- Re: [linux-audio-dev] LADSPA Control GUI metadata xfm
- Re: [linux-audio-dev] LADSPA Control GUI metadata xfm
