ecasound,jack,lame and processing finished problem

[Karol Zapolski]

Hello,

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

then I connect jack with ecasound :
jack_connect alsa_pcm:capture_3 ecasound:in_2
jack_connect alsa_pcm:capture_4 ecasound:in_3
jack_connect alsa_pcm:capture_5 ecasound:in_4
jack_connect alsa_pcm:capture_6 ecasound:in_5

I do 1h recording then I kill ecasound and lame processes

but sometimes ecasound or lame stops in the middle of the hour and on console i get :
[* Controller/Batch processing finished (0) *]

when I type ps ax I still see lame and ecasound processes but no cpu load at lame proceses and audio*.mp3 files are not growing...

Has anyone experienced it? is there any solution for that?

I'm using ecasound  v2.4.6.1, jackd 0.103.0 and LAME 64bits version 3.97 on FC7 with 2.6.21-1.3194.fc7 kernel...

Regards
Karol Zapolski
-------------------------------------------------------------------------
This SF.net 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 >>  http://get.splunk.com/
_______________________________________________
Ecasound-list mailing list
Ecasound-list@...
https://lists.sourceforge.net/lists/listinfo/ecasound-list

[Kai Vehmanen]

Hi,

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
soundcards).

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 http://eca.cx/kv

-------------------------------------------------------------------------
This SF.net 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 >>  http://get.splunk.com/
_______________________________________________
Ecasound-list mailing list
Ecasound-list@...
https://lists.sourceforge.net/lists/listinfo/ecasound-list