On Tue, May 18, 2004 at 01:19:50PM +0100, Martin Habets wrote:
On Mon, May 17, 2004 at 08:37:07PM -0700, H. T. Hind
wrote:
[snip]
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 ?
Maybe it's a memory or resource issue. Have a look at 'free' to see if
you're using swap or low on free memory. A 'sync' or two in your cron
script may help too, or expose the problem sooner (which also tells us
something...).
Hmm, resources doesn't seem to be the problem. The system has 512
MB ram, 1 GB Swap and is running a 2400 Athlon . When ecasound
and Jack are running the system is idle 95% and when lame is
running , the system is 15-20% idle.