Subject: Re: [ecasound] ECI standalone in action
From: S. Massy (theanaloguekid_AT_tak.net.dhis.org)
Date: Mon Oct 07 2002 - 00:21:23 EEST
On Sat, 05 Oct 2002, Kai Vehmanen <kai.vehmanen_AT_wakkanet.fi> wrote:
> I've implemented a C-version of edi-28 up to the point where I can run
> most ECI C apps without any major problems. I'm currently putting
> this to the CVS-tree. It will replace the current C implementation.
> The best thing about this is:
>
> # ecalength linked to the current C ECI
> [kaiv_AT_hed040-169 ecasound-cvs]$ ldd ecatools/.libs/ecalength
> libecasoundc2.so.2 => /home/kaiv/apps/ecasound-cvs/lib/libecasoundc2.so.2 (0x40018000)
> libecasound8.so.8 => /home/kaiv/apps/ecasound-cvs/lib/libecasound8.so.8 (0x40026000)
> libkvutils3.so.3 => /home/kaiv/apps/ecasound-cvs/lib/libkvutils3.so.3 (0x40372000)
> libdl.so.2 => /lib/libdl.so.2 (0x403b0000)
> libpthread.so.0 => /lib/i686/libpthread.so.0 (0x403b4000)
> libstdc++-libc6.2-2.so.3 => /usr/lib/libstdc++-libc6.2-2.so.3 (0x403c9000)
> libm.so.6 => /lib/i686/libm.so.6 (0x4040c000)
> libc.so.6 => /lib/i686/libc.so.6 (0x40430000)
> /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
>
> # ecalength linked to my new SA ECI impl
> [kaiv_AT_hed040-169 ecasound-cvs]$ ldd libecasoundc/ecalength
> libc.so.6 => /lib/i686/libc.so.6 (0x4002e000)
> /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
Yes, that was a problem with the ECI implementation up till now: linkage
against many libraries (including libstdc++ even for non-C++ apps.)
The new scheme for ECI really seems straightforward and powerful.
BTW, have you thought of making ecasound shell script friendly? Something like
providing raw access to the command parser (i.e with readline and
ncurses disabled) so that a shell could interact
directly with ecasound. Of course, another alternative might be to use
netECI to do just that: spawn an instance of ecasound in daemon
mode and then talk to it using netcat or another tool of the kind.
I know shell scripting with ecasound might seem useless when you can
already use python and perl to do the same, but shell scripting is
more widely known and is best of all for quick and dirty hacks. :)
Unfortunately I haven't been doing much recording lately so I haven't
really had a chance to test all the new improvements, but they certainly
seem very interesting.
Regards,
S. massy
This archive was generated by hypermail 2b28 : Mon Oct 07 2002 - 00:14:50 EEST