29 Nov
2005
29 Nov
'05
12:09 a.m.
ecasound is way too complicated for me. All I want to do is open jack
stereo ins and outs, load the LADSPA amp_stereo plugin, and control
that plugin's gain parameter via alsa midi.
The -Md:alsaseq parameter is apparently ignored, and I get some error
about a plate reverb?!
[paul@localhost paul]$ ecasound -i jack -o jack
-G:jack,ecasound,notransport -el:amp_stereo,1 -Md:alsaseq
-km:1,0,1,1,1
*********************************************************************************
ecasound v2.4.2 (C) 1997-2005 Kai Vehmanen and others
********************************************************************************-
[ Session created ]
----------------------------------------------------------- [
Chainsetup created (cmdline) ]
---------------------------------------------(eca-object-map) WARNING:
Keyword plate doesn't match to regex ^plate$ for
... object 'Plate reverb' ().
- [ Connecting chainsetup ]
----------------------------------------------------(eca-chainsetup)
'rt' buffering mode selected.
(eca-chainsetup) Audio object "jack", mode "read".
(audio-io) Format: f32_le, channels 2, srate 44100, noninterleaved.
(eca-chainsetup) Audio object "jack", mode "write".
(audio-io) Format: f32_le, channels 2, srate 44100, noninterleaved.
ERROR: Connecting chainsetup failed: "Unable to open MIDI-device: rawmidi."
(audioio_jack_manager) Connection closed!
29 Nov
29 Nov
5:07 a.m.
Hi Paul,
On Mon, 28 Nov 2005, Paul Coccoli wrote:
ecasound is way too complicated for me. All I want to
do is open jack
stereo ins and outs, load the LADSPA amp_stereo plugin, and control
that plugin's gain parameter via alsa midi.
[...]
The -Md:alsaseq parameter is apparently ignored, and I
get some error
about a plate reverb?!
the problem is that ALSA sequencer support was added to ecasound-2.4.3 and
you are using ecasound-2.4.2. So you'll need to upgrade. Otherwise your
setup looks ok.
[paul@localhost paul]$ ecasound -i jack -o jack
-G:jack,ecasound,notransport -el:amp_stereo,1 -Md:alsaseq
-km:1,0,1,1,1
[...]
ERROR: Connecting chainsetup failed: "Unable to
open MIDI-device: rawmidi."
This is perhaps not the best possible error message for the situation... will
be fixed in a later release.
--
links, my public keys, etc at http://eca.cx/kv
11:41 a.m.
On 11/29/05, Kai Vehmanen <kvehmanen(a)eca.cx> wrote:
Thanks Kai.
By the way, I'm just trying to use ecasound as a command line ladspa
host. Is there a simpler way to do this, or will I just have to write
some scripts? Is it possible to use the interactive mode to add a
ladspa plugin on the fly?
One last comment: I was surprised that ecasound exits when the jack
mode is "recv" and I stop the transport. I suppose that is the
intended behavior?
--
paul
Hi Paul,
On Mon, 28 Nov 2005, Paul Coccoli wrote:
Oops; my bad. 2.4.2 is the latest in Planet CCRMA. I was wondering
why the man page had so little to say about alsaseq.
I get that plate reverb error no matter what options I use. Is that
something in my system configuration?
ecasound is way too complicated for me. All I
want to do is open jack
stereo ins and outs, load the LADSPA amp_stereo plugin, and control
that plugin's gain parameter via alsa midi.
[...]
The -Md:alsaseq parameter is apparently ignored,
and I get some error
about a plate reverb?!
the problem is that ALSA sequencer support was added to ecasound-2.4.3 and
you are using ecasound-2.4.2. So you'll need to upgrade. Otherwise your
setup looks ok.
[paul@localhost paul]$ ecasound -i jack -o jack
-G:jack,ecasound,notransport -el:amp_stereo,1 -Md:alsaseq
-km:1,0,1,1,1
[...]
ERROR: Connecting chainsetup failed: "Unable
to open MIDI-device: rawmidi."
This is perhaps not the best possible error message for the situation... will
be fixed in a later release.
--
links, my public keys, etc at http://eca.cx/kv
30 Nov
30 Nov
5:56 a.m.
On Tue, 29 Nov 2005, Paul Coccoli wrote:
Oops; my bad. 2.4.2 is the latest in Planet CCRMA. I
was wondering
why the man page had so little to say about alsaseq.
:) The man page should be a reliable reference - it should always be up to
date (updated at commit time when features are changed/added CVS).
I get that plate reverb error no matter what options I
use. Is that
something in my system configuration?
Hmm, which plate reverb that is? That warning msg seems a bit strange --
something wrong with the description the plate reverb reports to ecasound.
Btw, you can get a listing of all LADSPA plugins ecasound finds with:
sh> echo ladspa-register |ecasound -c
That can be fed to a file, more/less, etc. Can you see the plate reverb in
the list?
By the way, I'm just trying to use ecasound as a
command line ladspa
host. Is there a simpler way to do this, or will I just have to write
some scripts?
This is the way to run a basic 'one plugin host'. For more complex stuff,
you need to write scripts (or a simple python/ruby/perl app) which
controls the ecasound engine. Ecamegapedal (a LADSPA/JACK host with Qt
interface) is built on top of ecasound, so it's certainly doable.
Is it possible to use the interactive mode to add a
ladspa plugin on the fly?
Yes, although you'll need to disconnect from JACK, modify the
configuration, and then connect back (this is how ecamegapedal does
the plugin changes).
One last comment: I was surprised that ecasound exits
when the jack
mode is "recv" and I stop the transport. I suppose that is the
intended behavior?
Yes, this issue has been discussed a few times on ecasound-list. As a
result, the "--keep-running/-K" option was added to ecasound-2.4.2. This
tells ecasound, runnin in batch (non-interactive -> no -c), not to exit
when processing is finished (JACK transport goes from running to stopped).
Another way to prevent exiting, is to run ecasound in interactive mode (-c).
--
links, my public keys, etc at http://eca.cx/kv
2 Dec
2 Dec
12:43 a.m.
On 11/30/05, Kai Vehmanen <kvehmanen(a)eca.cx> wrote:
On Tue, 29 Nov 2005, Paul Coccoli wrote:
I see three plate reverbs:
152. Versatile plate reverb
-el:Plate,'bandwidth','tail','damping','blend'
153. Versatile plate reverb,
... 2x2
-el:Plate2x2,'bandwidth','tail','damping','blend'
222. Plate reverb
-el:plate,'Reverb time','Damping','Dry/wet mix'
I get that plate reverb error no matter what
options I use. Is that
something in my system configuration?
Hmm, which plate reverb that is? That warning msg seems a bit strange --
something wrong with the description the plate reverb reports to ecasound.
Btw, you can get a listing of all LADSPA plugins ecasound finds with:
sh> echo ladspa-register |ecasound -c
That can be fed to a file, more/less, etc. Can you see the plate reverb in
the list?
18 Dec
18 Dec
5:57 a.m.
On Thu, 1 Dec 2005, Paul Coccoli wrote:
Hmm, ok, that's the problem, "Plate" vs "plate" as the plugin
name. This
is valid use of LADSPA, so I'll have to add some workaround to new
versions of ecasound. You can still use the plugins via their numerical id
(-eli:num-id,params,... to ecasound).
--
links, my public keys, etc at http://eca.cx/kv
On Tue, 29 Nov
2005, Paul Coccoli wrote:
> I get that plate reverb error no matter what options I use. Is that
> something in my system configuration?
I see three plate reverbs:
152. Versatile plate reverb
-el:Plate,'bandwidth','tail','damping','blend'
222. Plate reverb
-el:plate,'Reverb time','Damping','Dry/wet mix'
6948
days inactive
6968
days old
linux-audio-user@lists.linuxaudio.org
5 comments
2 participants
participants (2)
-
Kai Vehmanen -
Paul Coccoli