PDA

View Full Version : qjackctl won't start, but jackd will



hawk1105
3rd December 2008, 05:05 PM
hi everyone,
I recently switched from Ubuntu to Fedora 10 for the pulseaudio glitch-free audio, and it has been the smoothest transition imaginable, and i even had jack working for some time, which never happened to me on ubuntu.:rolleyes:
however, i installed several tools for pulseaudio, like the pulseaudio manager, etc. and these tools are perfect, however, qjackctl has stopped working. strangely though, running jackd from the command line still works. but that's not how i want to control jack.

i'm running Fedora 10 x68_64 and the latest Gnome.

qjackctl gives me this:

17:00:29.571 Patchbay deactivated.
17:00:29.579 Statistics reset.
Cannot connect to server socket err = No such file or directory
Cannot connect to server socket
jack server is not running or cannot be started
no message buffer overruns
17:00:29.586 ALSA connection graph change.
17:00:30.136 ALSA connection change.
17:00:32.877 JACK is starting...
17:00:32.878 /usr/local/bin/jackd -R -dalsa -r44100 -p128 -n4 -D -Chw:0 -Phw:0 -S -i4 -o4 -Xseq
Cannot connect to server socket err = No such file or directory
Cannot connect to server socket
jack server is not running or cannot be started
no message buffer overruns
jackd 0.109.2
Copyright 2001-2005 Paul Davis and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
JACK compiled with System V SHM support.
loading driver ..
apparent rate = 44100
creating alsa driver ... hw:0|hw:0|128|4|44100|4|4|nomon|swmeter|-|16bit
control device hw:0
configuring for 44100Hz, period = 128 frames (2.9 ms), buffer = 4 periods
ALSA: final selected sample format for capture: 16bit little-endian
ALSA: use 4 periods for capture
ALSA: final selected sample format for playback: 16bit little-endian
ALSA: use 4 periods for playback
port created: in-14-0-Midi-Through-Port-0
port created: out-14-0-Midi-Through-Port-0
port created: in-20-0-E-MU-Xboard49-MIDI-1
17:00:32.932 ALSA connection graph change.
17:00:32.933 JACK was started with PID=4282.
port created: out-20-0-E-MU-Xboard49-MIDI-1
17:00:33.219 ALSA connection graph change.
17:00:34.127 Could not connect to JACK server as client. - Overall operation failed. - Unable to connect to server. Please check the messages window for more info.
Cannot connect to server socket err = No such file or directory
Cannot connect to server socket
jack server is not running or cannot be started
no message buffer overruns
17:00:35.731 JACK is stopping...
jack main caught signal 15
port deleted: in-20-0-E-MU-Xboard49-MIDI-1
port deleted: in-14-0-Midi-Through-Port-0
port deleted: out-20-0-E-MU-Xboard49-MIDI-1
port deleted: out-14-0-Midi-Through-Port-0
no message buffer overruns
17:00:35.871 ALSA connection graph change.
17:00:35.954 JACK was stopped successfully.
17:00:35.955 Post-shutdown script...
17:00:35.955 killall jackd
jackd: no process killed
17:00:36.363 Post-shutdown script terminated with exit status=256.

but running from the command line gives me:

$ /usr/local/bin/jackd -R -dalsa -r44100 -p128 -n4 -D -Chw:0 -Phw:0 -S -i4 -o4 -Xseq
jackd 0.109.2
Copyright 2001-2005 Paul Davis and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details

JACK compiled with System V SHM support.
loading driver ..
apparent rate = 44100
creating alsa driver ... hw:0|hw:0|128|4|44100|4|4|nomon|swmeter|-|16bit
control device hw:0
configuring for 44100Hz, period = 128 frames (2.9 ms), buffer = 4 periods
ALSA: final selected sample format for capture: 16bit little-endian
ALSA: use 4 periods for capture
ALSA: final selected sample format for playback: 16bit little-endian
ALSA: use 4 periods for playback
port created: in-14-0-Midi-Through-Port-0
port created: out-14-0-Midi-Through-Port-0
port created: in-20-0-E-MU-Xboard49-MIDI-1
port created: out-20-0-E-MU-Xboard49-MIDI-1

i'm anxious to find out why there is any difference and how i can get qjackctl to work.
realtime running should not be a problem, and turning the realtime feature off doesn't help (this is the advice i've seen most from googling for a solution)

hawk1105
3rd December 2008, 08:41 PM
i got it fixed!
i got there by removing jack-connection-kit, which was installed from planetccrma, removing planetccrma from my software sources and reinstalling jack-connection-kit from fedora!
still can't see the difference, but it worked! :)