> it would be great for people to be able to make controllers for
plugins, without the author of RoseGarden or Seq24 needing to ad some
OM-style OSC-query-of-plugin-namespace
In my mind every plugin parameter should be automatable, therefore every
parameter update should be visible to the host
...therefore every plugin GUI should connect to the host (not directly
to the plugin)...therefore to support such GUIs every host *SHOULD*
provide some kind of query-of-plugin-namespace.
Jeff
Message: 3
Date: Mon, 26 Jun 2006 18:05:37 +0000
From: carmen <[EMAIL PROTECTED]>
Subject: Re: [linux-audio-dev] LADSPA Extension for Extra GUI Data
To: linux-audio-dev@music.columbia.edu
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=us-ascii
To ensure consistency the GUI should get its plugin descriptions from
the host anyway. This works even with POL (Plain Old Ladspa).
rather a more general format that it could use to describe its
internal modules or other plugin formats as well. The GUI doesn't
in theory, this (client-readable metadata) shouldnt be a selling point. i mean
if most hosts provided a nice API to query for plugin parameters. most don't..
it would be great for people to be able to make controllers for plugins,
without the author of RoseGarden or Seq24 needing to ad some OM-style
OSC-query-of-plugin-namespace
..
