Subject: Re: [linux-audio-dev] "pro" soundfile editors for linux
From: Kai Vehmanen (kaiv_AT_wakkanet.fi)
Date: ti helmi 08 2000 - 07:57:47 EST
On Mon, 7 Feb 2000, Paul Barton-Davis wrote:
>>develop apps for specific tasks. And of course, developing
>>inter-application communication (did I say MuCoS) is also important.
> I agree entirely, except that I prefer using C++ objects as the
> "interface point", rather than the Unix process level. however, those
Well, at least now, using language level communication seems to be
difficult. And C++ has its own problems. With ecasound, many people
have helped me in testing, writing autoconf/automake stuff, but I
haven't received a single line of actual code. I'm sure, if I had
written ecasound in C, there would have been many contributors.
Another problem is compile-time and inter-library compatibility
problems. Most problem-reports I receive are either g++ or
libstc++ related. And taking your Quasimodo as an example, I've
never been able to compile it. Same goes with aRts. And believe me,
I've tried both many, many times. I've have only a 14.4k modem
connection to Internet, so I can't afford to continuously update
my libraries. But I guess many people have gone through the same
thing with ecasound. This is why I prefer simple UNIX-style
communication between apps. At least for now.
-- Kai Vehmanen <kaiv_AT_wakkanet.fi> -------- CS, University of Turku, Finland . http://www.wakkanet.fi/ecasound/ - linux multitrack audio processing . http://www.wakkanet.fi/sculpscape/ - ambient-idm-rock-... mp3/ra/wav
This archive was generated by hypermail 2b28 : pe maalis 10 2000 - 07:23:27 EST