[LAU] Jack fails in QJackCtl but not in command line

[Anton Curl]

On 03/05/2015 00:06, Ralf Mardorf wrote:
> On Sat, 02 May 2015 23:51:22 +0200, Anton Curl wrote:
>> This is what I have in my .jackdrc.
>>
>> In command line, there is no problem. It works perfectly. But if I try
>> to launch Jack with this parameters through QJackCtl
> Do you use this settings, or do you expect that QjackCtl does use the
> settings stored in ~/.jackdrc?
>
> QjackCtl does not use the settings stored in ~/.jackdrc, it does use
> the settings stored in ~/.config/rncbc.org/QjackCtl.conf .
Yes, but QJackCtl wrote this file, not me. So if I run this command, I 
run the same command that QJackCtl uses to start jackd.

On 03/05/2015 02:05, Chris Caudle wrote:
> On Sat, May 2, 2015 4:51 pm, Anton Curl wrote:
>>      /usr/bin/jackd -P80 -dalsa -r44100 -p256 -n2 -Xseq -D -Chw:5,1
>> -Phw:5,0
>> In command line, there is no problem. It works perfectly. But if I try
>> to launch Jack with this parameters through QJackCtl, I get this in the
>> message window:
>>
>>      creating alsa driver ...
>>      hw:5,1|hw:5,1|256|3|44100|0|0|nomon|swmeter|-|32bit
>>
>> The 5.0 output becomes 5.1. I don't understand why.
>
> In the QJackControl setup dialog, did you select different input and
> output hardware device?
>
Yes,
Input: hw:5.1
Output: hw:5.0
And duplex is also set.

Anton Curl