1
------------------------------------------------------------------------
4
(edi-29): Ecamonitor - ecasound monitor client implemented using NetECI.
5
- submitted: kaiv, 29.09.2002
8
------------------------------------------------------------------------
12
- there's a need for better real-time status monitoring than that
13
provided by current ecasound frontends
14
- list of goals/requirements that should be reached
15
- ability to monitor (in real-time) at least the following:
16
- lists of chains, inputs and outputs of the connected cs
17
- current position and overall length of the connected cs
18
- engine status (running/stopped/finished/notready/error)
19
- list of chainops and ctrls plus their current parameter
21
- no need to restart if ecasound is restarted; ie. ability to
22
automatically reconnect if connection is lost
24
- monitoring central cs-params: srate, buffersize, raisedpriority, ...
25
- MIDI-activity monitoring
26
- monitoring volume levels
28
- edi-27: NetECI - network interface for controlling ecasound operation.
30
------------------------------------------------------------------------