> >> - object maps
> >> - get list of supported audio object, chain op and
> >> controller types
> > These are related to the -register commands?
>
> Yup. Same information content, but in a more usable format. This is a very
> powerful feature, and shouldn't be too difficult to add. A good example of
> this is ecawave's effects dialog. Ecawave doesn't directly handle
> any effect code. Still its able to provide a usable effect GUI (including
> support for native and LADSPA effects + presets!).
>
> For instance with effects, you'd need to get a list of items containing
> the following info
> - effect identifier
> - name
> - comma-separated list of parameters
>
> Let's take the new pulse gate as an example. You'd get the following info:
> - eepm
> - "Pulse Gate"
> - Pulse Gate:freq-Hz,on-time-%

Even more usable format would be: (thinking in python)
- name (string)
- effect identifier (string?)
- number of parameters (int)
- list of parameters (list of strings)
- list of parameter hint ranges, if available (list of lists of numbers (float?))

This conversion from the one above to the one below is easily done, (except for the parameter hints) so it is no issue.

> So now you know
> 1) how to add a new effect of this type (-eepm:arg1,arg2)
> 2) effect's name (for building a user-interface)
> 3) how many parameters (2 in this case -> you can start
> using the cop-set ia-mode command)
> 4) description of each parameter (for the user-interface)
>
> Additionally, a more verbose description of the effect could also be
> provided (this is already covered by the C++ APIs, although not
> implemented for many effect types).

This would be nice. In addition to some parameters to adjust, there could be a short verbal description of the effect..? (or some other general info)

> Same procedure can be applied to audio objects, controllers,
> effect presets and LADSPA plugins.