On Tuesday 29 June 2004 09:51, Andres Toomsalu wrote:
I can see with qjackctl that when Im starting caed, it will connect
ports correctly but then it will disconnect ports and exit within 2-3
seconds.
How are you starting caed(8)? By using the init script? I've noticed some
quirky behavior sometimes when using the init script. On some systems it
works fine. On others, it seems to hang the graph in odd ways -- the ports
will show up in QJackConnect, but QJackConnect itself then becomes totally
unresponsive to user interaction until caed(8) is killed. I'm not sure if
the problem is in caed or jackd itself. I'm currently running a rather old
version of JACK (v0.80.0) in an effort to keep it stock SuSE 9.0, but I'm
planning to upgrade to the current release shortly to see if that makes a
difference. In the meantime, try the following experiment:
1) Make sure all Rivendell daemons are shut down.
2) Start up jackd
3) Open an xterm, 'su' to root and do 'caed -d'. The '-d' will keep it from
forking to the background.
4) Start up the rest of the Rivendell daemons normally (using the init script
if desired).
Does that make any difference?
Also, what kernel are you using? There are major issues right now with
running JACK on a 2.6.x kernel (appears to be related to the new NPTL
pthreads implementation, but the JACK developers don't really have a handle
on it yet). Check out the jack-devel list for details.
Cheers!
|-------------------------------------------------------------------------|
| Frederick F. Gleason, Jr. | Director of Broadcast Software Development |
| | Salem Radio Labs |
|-------------------------------------------------------------------------|
| A cynic is a person searching for an honest man, with a stolen lantern. |
| -- Edgar A. Shoaff |
|-------------------------------------------------------------------------|
-----------------------------------------------------------------------------
To unsubscribe to the rivendell-dev list, send mail to
'majordomo@xxxxxxxxxxxxxxxxxxxxxxxxxx' and put 'unsubscribe rivendell-dev'
in the message body (NOT the subject line).
-----------------------------------------------------------------------------