[PlanetCCRMA] No Qjackctl, jackd from CLI works fine

Henrik Frisk frisk.h at gmail.com
Tue Sep 30 13:42:57 PDT 2008


Hi all,

After some issues with Qjackctl (crashes) it no longer wants to start
but issues the following:

JACK compiled with System V SHM support.
loading driver ..
SSE2 detected
apparent rate = 48000
creating alsa driver ... hw:1|hw:1|1024|4|48000|2|2|nomon|swmeter|-|32bit
control device hw:1
configuring for 48000Hz, period = 1024 frames (21.3 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: cannot set channel count to 2 for playback
ALSA: cannot configure playback channel
cannot load driver module alsa
no message buffer overruns
22:40:40.243 JACK was stopped successfully.
22:40:40.244 Post-shutdown script...
22:40:40.244 killall jackd
jackd: no process killed
22:40:40.654 Post-shutdown script terminated with exit status=256.
22:40:42.406 Could not connect to JACK server as client. - Overall
operation failed. - Unable to connect to server. Please check the
messages window for more info.

However, jackd started with the same backend (alsa) and the same
hardware and settings works fine:

JACK compiled with System V SHM support.
loading driver ..
SSE2 detected
creating alsa driver ... hw:1|hw:1|1024|4|48000|0|0|nomon|swmeter|-|32bit
control device hw:1
configuring for 48000Hz, period = 1024 frames (21.3 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

Any ideas as to why this may be?

Thanks,

/Henrik



More information about the PlanetCCRMA mailing list