Subject: Re: [ecasound] extending the C-API design
From: Kai Vehmanen (email@example.com)
Date: Wed Nov 08 2000 - 00:08:05 EET
On Tue, 7 Nov 2000, janne halttunen wrote:
>> - read access to ecasound per-user resources (~/.ecasoundrc)
> What does this mean exactly?
A function for querying the value-key pairs stored in
~/.ecasoundrc (see 'man ecasoundrc' for the complete list of possible
>> - 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
- comma-separated list of parameters
Let's take the new pulse gate as an example. You'd get the following info:
- "Pulse Gate"
- Pulse Gate:freq-Hz,on-time-%
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).
Same procedure can be applied to audio objects, controllers,
effect presets and LADSPA plugins.
-- . http://www.eca.cx ... [ audio software for linux ] /\ . . http://www.eca.cx/sculpscape [ my armchair-tunes mp3/ra/wav ]
-- To unsubscribe send message 'unsubscribe' in the body of the message to <firstname.lastname@example.org>.
This archive was generated by hypermail 2b28 : Wed Nov 08 2000 - 00:26:04 EET