Re: [ecasound] Using Nama (was: Re: Nama build issues (was: Re: Interactive mode, cut &) paste)

From: Joel Roth <joelz@email-addr-hidden>
Date: Sun Dec 02 2012 - 07:44:20 EET

On Sat, Dec 01, 2012 at 11:24:16PM +0100, Lars Bj??rndal wrote:
> Hi, and thank you very much for all your help! Now, I've successuflly
> built Nama, and I can start it in text mode. I've created a project
> and imported a WAV file. When pressing SPACE to play, I get the
> following error message: "Cannot start. Engine is not configured."

> I have the package ecasound-2.7.2-1.fc17.ccrma.i686 installed. What's
> the problem, do you think?

Hi Lars,

First, all this assumes a working ALSA or JACK setup.
You can check if Ecasound is okay by playing
a WAV file.

$ ecasound -i somefile.wav -o alsa,default

When running Nama, even without importing a .WAV file, you
should be able to create a track and record to it.

The command

nama> add vocals

should lead to a setup to get you a track that records from
your soundcard (channel 1), and provides a monitor output to
the soundcard.

Before attempting to start the engine (in response to
the SPACE bar or user start command), Nama runs the Ecasound
'cs-connected' command.

Your particular error is because Ecasound returned
false, i.e. no chain setup is connected, i.e. the
engine is not configured.

Nama spits out a new Ecasound configuration file and tells
Ecasound to load it at every change in setup, for example
when you create a new track, or change a track from

You can view Nama/Ecasound's audio network
in several ways:

show_tracks, show Nama's track view
chain_setup, chains The current chain setup file
fs, cs, es Various Ecasound status commands

Hope this helps...

> Regards,
> Lars

Joel Roth
Joel Roth
Keep yourself connected to Go Parallel: 
DESIGN Expert tips on starting your parallel project right.
Ecasound-list mailing list
Received on Sun Dec 2 08:15:01 2012

This archive was generated by hypermail 2.1.8 : Sun Dec 02 2012 - 08:15:01 EET