Re: [ecasound] Re: ecamegapedal 0.1dev6 released

New Message Reply Date view Thread view Subject view Author view Other groups

Subject: Re: [ecasound] Re: ecamegapedal 0.1dev6 released
From: Kai Vehmanen (
Date: Wed Jun 27 2001 - 00:04:46 EEST

On Mon, 25 Jun 2001, Junichi Uekawa wrote:

>> Ecamegapedal uses different default values. You should get identical
>> performance with:
>> ecasound -i /dev/dsp -o /dev/dsp -b:256 -z:nointbuf
> That seems to answer my question.
> -b:256 does not run reliably on this system I am
> currently using...

Ok, I should add options for selecting the buffersize and possibly other
ecasound related params. Even better, there should be a graphical
configuraion dialog. And this should be added to all Qt eca apps
(qtecasound, ecawave and ecamegapedal).

I've been thinking about adding a hierarchy-based config-file system,
where you could have multiple levels of configuration files. For instance,
you could have the following files:


Now these files could contain both app-specific, and ecasound-wide
settings. Let's take 'default-buffersize' for an example. When
ecamegapedal is started, it first goes through ~/.ecamegapedal, if d-bsize
is not found, it goes to /usr/local/share/ecamegapedal, then to
~/.ecasoundrc, then to /usr/local/share/ecasound, and only then falls back
to hardcoded (in the src code) defaults. If the user changes his
preferences, the new values would be stored in ~/.ecamegapedal.

Other apps (qtecasound, ecawave, possibly others) could use a similar

Btw; any comments on the software itself? I have got very
little feedback concerning ecamegapedal. Is it usable, a good start, or
something I should not waste my time on...?

 Audio software for Linux!

-- To unsubscribe send message 'unsubscribe' in the body of the message to <>.

New Message Reply Date view Thread view Subject view Author view Other groups

This archive was generated by hypermail 2b28 : Wed Jun 27 2001 - 00:47:11 EEST