- a menu-based UI for editing chainsetup files
- support for setting up inputs, outputs, chainops,
controllers, general options... ie. pretty much
everything!
- integrated with tuteca so you get a context-sensitive
help visible at all times!

.. so yup, it already does a _lot_ of things!

One big problem is usability. It's basicly the same problem as with
qtecasound. If you don't know how ecasound works, it's not very easy to
create a new chainsetup from scratch. Adding objects one by one is slow,
and you have to know how chainsetups work (what's a valid cs, etc).

I've tried to think about this problem from enduser perspective, ie. what
kind of tasks would people want to do with qtecasound/ecasetupedit. Most
common uses are probably:
- mixing multiple inputs to file (mixdown)
- mixing multiple inputs to soundcard (effect processing)
- multitrack recording
- realtime effect processing

In other uses (simple recording or playback), you really don't need
complex chainsetups. One possible solution would be to have templates.
This works approach quite well for instance Roxen webserver. Roxen
provides a fancy web-GUI for configuring websites, but it's really painful
to create new sites from scratch (the web-GUI is slow when remotely
operated, lots of menus and different options...). But when you have
templates for most common webserver types, you just have to pick the
closest template, and then make a few edits to customize the server for
your needs.

This approach might also work for ecasound chainsetups (and the user
interfaces). Comments?