Subject: Re: [linux-audio-dev] Newbie: searching a good library for audio + midi (fwd)
From: Kai Vehmanen (kaiv_AT_wakkanet.fi)
Date: Wed Jan 24 2001 - 00:05:20 EET
Oops, a whole message about ecasound design without even one use of
'simple'. :) Seriously, when compared to other alternatives mentioned
during this thread (aRts, jMax, csound, cmix, keykit, Ardour, etc),
ecasound really is simple. And I'm not talking about ease of use. Ecasound
is design-wise based around a single use-case (multitrack audio
processor), which just happens to fit a number of common real-life uses
(multitrack recording, mixing, single-track recording and playback, etc).
Hopefully this simplicity of design also results in ease of use (for
end-users) and faster development (for projects built on top of ecasound).
In other words I try to target between the real one purpose only apps and
the abovementioned extendable monsters. ;)
--
---------- Forwarded message ----------
Date: Tue, 23 Jan 2001 22:26:52 +0200 (EET)
From: Kai Vehmanen <kaiv_AT_wakkanet.fi>
To: Thomas Guettler <guettli_AT_interface-business.de>
Cc: linux-audio-dev_AT_ginette.musique.umontreal.ca, ecasound-list_AT_wakkanet.fi
Subject: Re: [linux-audio-dev] Newbie: searching a good library for audio +
midi
On Tue, 23 Jan 2001, Thomas Guettler wrote:
> I searched for something like this on www.python.org yesterday. I will
> try it as soon as I have time.
[...]
> Would a combination of ardour and midithing give me the possibilty to
> add audio data which I manipulate with effects in realtime?
This doesn't necessarily fit your needs, but I'd still like to mention
pyeca, python API to access ecasound functionality. It comes with the main
ecasound package (ecasound 1.8.5 and newer, not yet in stable releases).
I'm still trying to come up with good marketing phrases, but in short you
can...
- set up a group of inputs and outputs (files, soundcard capture/playback)
- set up effects, LADSPA plugins, gates, etc
- issue start, stop, seek, affecting the above setup
- modify effect params during processing (near-realtime)
... you cannot generate sound data with pyeca (and ecasound in general),
so all audio material must be in files or come from a rt-source such as a
soundcard. Ecasound does have support for aRts (via its C-API), but I'm
not sure how well piping soft-synth output from aRts to ecasound works in
practise. As someone already mentioned, looping and offsetting files
(playing certain audio file at a certain point of time) is possible with
ecasound (using the ewf-format). Hmm, you could say that ecasound is a
'multitrack audio processor', not a 'sw synthesizer' or 'sequencer'.
As for MIDI, you can connect a MIDI-source to a effect parameter, but
you can't generate or interpret MIDI-data using pyeca.
If interested, here's a few links:
- the pyeca API (part of ECI):
http://www.wakkanet.fi/~kaiv/ecasound/Documentation/programmers_guide/eci_doc.html
- pyeca is built on top of Ecasound Interactive Mode (EIAM) commands:
http://www.wakkanet.fi/~kaiv/ecasound/Documentation/ecasound-iam_manpage.html
--
. http://www.eca.cx ... [ audio software for linux ] /\ .
. http://www.eca.cx/sculpscape [ my armchair-tunes mp3/ra/wav ]
This archive was generated by hypermail 2b28 : Wed Jan 24 2001 - 00:25:13 EET