Subject: Re: [ecasound] Question about Interfaces
From: Kai Vehmanen (k_AT_eca.cx)
Date: Sat Oct 04 2003 - 13:37:23 EEST
On Fri, 3 Oct 2003, Jim Ramsay wrote:
> I am curious why the "object oriented" interfaces to ecasound (like the
> C++ and python ones) do not provide a more object-oriented idiom for
> accessing chains, inputs, outputs, effects, etc?
They are easier to maintain. It's also possibly to use the interfaces
provided by libecasound [1], but this is no longer encouraged. The
following mail explains some of the history and reasons for concentrating
on the simpler ECI interfaces:
http://eca.cx/ecasound-list/2002/10/0031.html
[1] http://www.wakkanet.fi/~kaiv/ecasound/Documentation/dg_libecasound/html/hierarchy.html
> For example, why not have a chain as an object, and a chainsetup as a
> container of chains? This to me seems to be a much more useful view of
> the actual data being used. There is obviously some sort of internal
Few example of the libecasound interface:
http://www.wakkanet.fi/~kaiv/ecasound/Documentation/dg_libecasound/html/class_c_h_a_i_n.html
http://www.wakkanet.fi/~kaiv/ecasound/Documentation/dg_libecasound/html/class_e_f_f_e_c_t___a_m_p_l_i_t_u_d_e.html
http://www.wakkanet.fi/~kaiv/ecasound/Documentation/dg_libecasound/html/class_e_c_a___c_h_a_i_n_s_e_t_u_p.html
-- http://www.eca.cx Audio software for Linux!
This archive was generated by hypermail 2b28 : Sat Oct 04 2003 - 13:41:36 EEST