Re: [ecasound] future of qtecasound?

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

Subject: Re: [ecasound] future of qtecasound?
From: Jeremy Hall (jhall@UU.NET)
Date: Thu May 04 2000 - 23:53:41 EEST

Kai,

How difficult would it be to write two new interfaces, 1: make a socket in
/var/run/ecasound.$$

2: bind at a port if the -p or some such option exists.

what this buys you:

1: a client can connect to a socket on a local machine with standard unix
procedure calls. This allows an ecasound to run in the background until a
user needs to talk to it. If ecasound starts in interactive mode, the
socket would not be created. This allows a front-end program to drive
ecasound easily by sending/receiving on a pipe, rather than having to
launch a new one.

2: bind to a port: If a cli program is running on a remote machine, it may
wish to talk to an ecasound running on this machine. Make it use
hosts.allow/hosts.deny or some such. I'll write up the RFC describing the
protocol. In this way, interactive mode might be able to be removed
completely from ecasound and moved to ecacli, ecasound becomes ecasoundd

just a thought.

_J

In the new year, Kai Vehmanen wrote:
> On Wed, 3 May 2000, Neil E. Klepeis wrote:
>
> > I've made a little Perl/Tk prototype front-end to ecasound. A
> > screenshot and the source are available at:
> [...]
> > http://socrates.berkeley.edu/~nklepeis/ECO/
>
> Hmm, looks a lot like Janne Halttunen's gteca (written in Python). Maybe
> you could join forces? Btw; can I add a link to your project on
> http://eca.cx/eca_links.html ...?
>
> > This is just an example to illustrate a type of interface that might be
> > incorporated into a GTK front-end.
>
> Compared to qtecasound, there's one big difference. Unlike qtecasound,
> your front-end is clearly focused (mixing and multitrack recording).
> Qtecasound on the other hand tries to be a generic user-interface
> (player, conversions, effects, mixing, recording, signal recycling, etc).
> Unfortunately combining GUI and genericity causes all kinds of
> problems (complexity, if nothing else).
>
> If you, or someone else, manages to write a good front-end for recording
> and mixing (these are both areas where GUI is most needed), I could
> concentrate on improving the current qtecasound design:
> - "graphical ia-mode"
> - all configuration is done using ia-mode commands and
> external chainsetup editing
> - graphical widgets are used only for visualization and monitoring
>
> --
> Kai Vehmanen <k@eca.cx> ---------------- CS, University of Turku .
> . audio software for linux ... http://www.eca.cx .
> . armchair-tunes mp3/wav/ra .. http://www.wakkanet.fi/sculpcave .
>
>
> --
> To unsubscribe send message 'unsubscribe' in the body of the
> message to <ecasound-list-request@wakkanet.fi>.
> 

--
To unsubscribe send message 'unsubscribe' in the body of the
message to <ecasound-list-request@wakkanet.fi>.

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

This archive was generated by hypermail 2b28 : Thu May 04 2000 - 23:54:45 EEST