On 06/08/2011 08:36 PM, Ralf Mardorf wrote: [SNIP] So, summa summarum: There were a few configure/compiler warnings and a few tweaks needed, but you got your [audio] system set up; with only one remaining issue: qjackctl fails to start jackd2. - but if jackd is started manually qjackctl can connect to it. Is that about right? When you start jackd manually you do not specify an interface (it uses "-dhw:0,0" as default) and that apparently works: > jackd --sync -Xalsarawmidi -dalsa -r48000 -p1024 correct? Yet with qjackctl you don't specify an interface globally but configure Input and Output devices separately: > jackd -dalsa -r48000 -p1024 -n2 -D -Chw:1 -Phw:1 Does the following command work starting jackd from the commandline? jackd -dalsa -r48000 -p1024 -n2 -dhw:1 If it fails: - try `aplay -Dhw:1 some_audio.wav` -> does the hw:1 soundcard work? - if the soundcard works: please tell us the version of jackd If launching jackd from the commandline works with -dhw:1 Did you try the suggestion to leave "Input Device" and "Output Device" as "default" and only set "Interface" = "hw:0" or "hw:1" (in qjackctl's setup dialog). Try to configure qjackctl so that it calls jackd -dalsa -r48000 -p1024 -n2 -dhw:1 instead of .... -Chw:1 -Phw:1 If you don't succeed: Please tell us the version of qjackctl and post your qjackctl config. (or make a screenshot of the setup window and send us _a link_ to the image. This email list won't allow large file attachments.) ciao, robin PS. You can specify the '--sync' and '-Xalsarawmidi' options as part of the "Server Path" in qjackctl. - but only do that later when everything else works. _______________________________________________ Linux-audio-user mailing list Linux-audio-user@xxxxxxxxxxxxxxxxxxxx http://lists.linuxaudio.org/listinfo/linux-audio-user
