Re: [linux-audio-user] puzzling ecasound error

From: Paul Coccoli <pcoccoli@email-addr-hidden>
Date: Tue Nov 29 2005 - 17:41:45 EET

On 11/29/05, Kai Vehmanen <kvehmanen@email-addr-hidden> wrote:
> 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.
>

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?

> > [paul@email-addr-hidden 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
>

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
Received on Tue Nov 29 20:15:06 2005

This archive was generated by hypermail 2.1.8 : Tue Nov 29 2005 - 20:15:07 EET