Re: [ecasound] ecasound,jack,lame and processing finished problem

From: Kai Vehmanen <kvehmanen@email-addr-hidden>
Date: Fri Aug 24 2007 - 00:53:25 EEST


On Tue, 21 Aug 2007, Karol Zapolski wrote:

> I'm using ecasound with jack server on maudio 1010lt card
> First I start jack server with jack -d alsa command, then
> I start ecasound :
> ecasound \
> -a:1 -i jack_alsa -a:1 -f:32,1,44100 -o audio1.mp3 \
> -a:2 -i jack_alsa -a:2 -f:32,1,44100 -o audio2.mp3 \
> -a:3 -i jack_alsa -a:3 -f:32,1,44100 -o audio3.mp3 \
> -a:4 -i jack_alsa -a:4 -f:32,1,44100 -o audio4.mp3
> but sometimes ecasound or lame stops in the middle of the hour and on
> console i get :
> [* Controller/Batch processing finished (0) *]

hmm, that sounds like jackd is kicking ecasound out of the graph for some
reason. It would be interesting to see the jackd logs around the time
ecasound exits.

Alternatively, you could try recording directly without jackd:

ecasound -a:1,2,3,4 -f:32,12,44100 -i alsa,hw:0 \
          -a:1 -f:32,1,44100 -o audio1.mp3
          -a:2 -f:32,1,44100 -o audio2.mp3 -erc:2,1
          -a:3 -f:32,1,44100 -o audio3.mp3 -erc:3,1
          -a:3 -f:32,1,44100 -o audio4.mp3 -erc:4,1

If you get an error from ALSA, the '-f:32,12,44100' doesn't match your
soundcard's hw-capabilityies. You can either try to guess the correct
options, or use "-i alsa,default" or "-i alsa,default" instead of the
above (less efficient, but are more likely to work with different

Of course, the above should work with jackd as well, but if you are not
doing latency sensitive processing, recording directly from ALSA to lame
might be more reliable.

  links, my public keys, etc at
This email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>
Ecasound-list mailing list
Received on Fri Aug 24 04:15:01 2007

This archive was generated by hypermail 2.1.8 : Fri Aug 24 2007 - 04:15:02 EEST