Subject: Re: [ecasound] Re: writable port and client names
From: Kai Vehmanen (kai.vehmanen_AT_wakkanet.fi)
Date: Thu Dec 20 2001 - 01:09:17 EET
As this is pretty much 100% ecasound-specific stuff, I dropped
jackit-devel from the cc-list.
On Tue, 18 Dec 2001, Jeremy Hall wrote:
>> Usually this kind of situation means that our design is too limited for
>> what we want to do.
> I have wondered this for years.
What exactly?
>> One thing I've been thinking about is adding a generic driver type to
>> ecasound. This would also solve the problem of how to use
> hmm I think we may be saying the same thing?
Probably we are. I've now written the first version of manager-based jack
client. It's different from the driver-based design ardourd/jackd uses,
but should deliver same kind of behaviour.
>> But this wouldn't be a small change. The basic design of ecasound's engine
>> and types has not been changed since early 1.x versions, and that's a
>> _long_ time as pretty much everything else has changed during that time.
> but over the years things have gotten slower and that delay is quite hard
> to swallow. Maybe it is time to relook at the engine design.
What has gotten slower? For what uses current ecasound versions are
designed, I think the engine code does its job well. Of course now that
we'd like to extend the scope of functionality, the design needs
rethinking.
-- http://www.eca.cx Audio software for Linux!-- To unsubscribe send message 'unsubscribe' in the body of the message to <ecasound-list-request_AT_wakkanet.fi>.
This archive was generated by hypermail 2b28 : Thu Dec 20 2001 - 01:01:32 EET