Subject: [linux-audio-user] Problem recording 24/7
From: H. T. Hind (hirh_AT_comcast.net)
Date: Tue May 18 2004 - 06:37:07 EEST
Hi,
I'm trying to record 24/7 using Fedora Core 1, JACK 0.98,
ecasound 2.3.3 , python2.2.3, alsa-1.0.1 and
2.4.22-1.2140.nptl.caps.rhfc1.ccrma kernel and delta 1010. I'm
using the Planet CCRMA packages and kernel. Cron kicks off a
python script every hour, that starts ecasound and records 4 channels for 1
hour . The script also invokes lame to compress the recorded
files to mp3.
The Python script invokes jack_connect to connect the ecasound
instance with JACK. After a couple of days of perfect recording,
jack_connect just seems to hang while connecting and then all the
subsequent instances of recording invoked from CRON pile and no
more recording happens till JACK is restarted.
The JACK logs show the following entries -
subgraph starting at ecarecord_26319 timed out (subgraph_wait_
fd=13, status = 0, state = Triggered)
at 357895053385 client waiting on 13 took 1009935 usecs, status = 1 sig = 357894043446 awa = 0 fin = 0 dur=0
subgraph starting at ecarecord_26319 timed out (subgraph_wait_
fd=13, status = 0, state = Triggered)
at 357896063568 client waiting on 13 took 1009961 usecs, statu
s = 1 sig = 357895053603 awa = 0 fin = 0 dur=0
subgraph starting at ecarecord_26319 timed out (subgraph_wait_
fd=13, status = 0, state = Triggered)
The ecasound log for the instance ecarecord_26319 shows -
(ecasoundc_sa) Error='read() error', cmd='engine-halt'
last_error='' cmd_cnt=2192 last_cnt=2191.
(ecasoundc_sa) Error='sync error', cmd='cs-disconnect'
last_error='' cmd_cnt=2193 last_cnt=2191.
(ecasoundc_sa) Error='read() error', cmd='cs-disconnect'
last_error='' cmd_cnt=2193 last_cnt=2191.
I can't figure out what could be causing the jack_connect
instance to stall , whether it is JACK , jack_connect or ecasound
or python I can't figure out. Any pointers or suggestions on how
to solve the problem ?
hth
---
This archive was generated by hypermail 2b28 : Tue May 18 2004 - 06:31:53 EEST