Thread: [qjackctl-devel] qjackctl dbus on Fedora 18, not obeying settings
JACK Audio Connection Kit Qt GUI Interface
Brought to you by:
rncbc
From: Ian M. <ibm...@gm...> - 2012-11-03 21:02:54
|
Hi, I'm having a number of problems with jack on Fedora 18 (development) and think they may be related to QJackCtl. I'm not sure if it's all the same problem or several different ones, it's also odd in that the behaviour changes, despite using a Live boot ISO. The first thing I'm noticing is that despite setting separate input and output devices in settings, qjackctl appears to start Jack with the same device for input and output. I don't know if that's a qjackctl problem, or something to do with jackdbus itself. At the same time, if pulse has been used then dbus fails to start, looking like this: 16:56:21.422 D-BUS: JACK server could not be started. Sorry Sat Nov 3 16:56:21 2012: Starting jack server... Sat Nov 3 16:56:21 2012: JACK server starting in realtime mode with priority 60 Sat Nov 3 16:56:21 2012: control device hw:1 Sat Nov 3 16:56:21 2012: control device hw:1 Sat Nov 3 16:56:21 2012: [1m[31mERROR: Failed to acquire device name : Audio1 error : Method "RequestRelease" with signature "i" on interface "org.freedesktop.ReserveDevice1" doesn't exist [0m Sat Nov 3 16:56:21 2012: [1m[31mERROR: Audio device hw:1 cannot be acquired...[0m Sat Nov 3 16:56:21 2012: [1m[31mERROR: Cannot initialize driver[0m 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 Sat Nov 3 16:56:21 2012: [1m[31mERROR: JackServer::Open() failed with -1[0m Sat Nov 3 16:56:21 2012: [1m[31mERROR: Failed to open server[0m Sat Nov 3 16:56:22 2012: Saving settings to "/home/liveuser/.config/jack/conf.xml" ... 16:56:36.981 D-BUS: JACK server could not be started. Sorry 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 Sat Nov 3 16:56:36 2012: Starting jack server... Sat Nov 3 16:56:36 2012: JACK server starting in realtime mode with priority 60 Sat Nov 3 16:56:36 2012: control device hw:1 Sat Nov 3 16:56:36 2012: control device hw:1 Sat Nov 3 16:56:36 2012: [1m[31mERROR: Failed to acquire device name : Audio1 error : Method "RequestRelease" with signature "i" on interface "org.freedesktop.ReserveDevice1" doesn't exist [0m Sat Nov 3 16:56:36 2012: [1m[31mERROR: Audio device hw:1 cannot be acquired...[0m Sat Nov 3 16:56:36 2012: [1m[31mERROR: Cannot initialize driver[0m Sat Nov 3 16:56:36 2012: [1m[31mERROR: JackServer::Open() failed with -1[0m Sat Nov 3 16:56:36 2012: [1m[31mERROR: Failed to open server[0m Sat Nov 3 16:56:38 2012: Saving settings to "/home/liveuser/.config/jack/conf.xml" ... (N.B. it's also trying to open hw:1 for both play and capture, though I've set them differently in the GUI) So it looks like the dbus release request is unsuccessful if the interface has already been claimed by pulse. Starting at the command line or without the dbus interface and separate -P and -C devices works as expected. Finally, it's possible, though I'm not 100% certain, that I've seen jackdbus used (pulse jack sinks/sources created automatically) when the 'Use DBUS' option is disabled (and qjackctl has been restarted). But I've been round this cycle quite a few times now, so I could be wrong. By the way, thanks very much for QJackCtl, been using it happily in earlier Fedora releases for a while now. It'll be the final piece of the puzzle in having all this working seemlessly if the dbus stuff can work properly. -- imalone http://ibmalone.blogspot.co.uk |
From: Rui N. C. <rn...@rn...> - 2012-11-03 21:41:13
|
On 11/03/2012 09:02 PM, Ian Malone wrote: > Hi, > > I'm having a number of problems with jack on Fedora 18 (development) > and think they may be related to QJackCtl. I'm not sure if it's all > the same problem or several different ones, it's also odd in that the > behaviour changes, despite using a Live boot ISO. > > The first thing I'm noticing is that despite setting separate input > and output devices in settings, qjackctl appears to start Jack with > the same device for input and output. I don't know if that's a > qjackctl problem, or something to do with jackdbus itself. > > At the same time, if pulse has been used then dbus fails to start, > looking like this: > 16:56:21.422 D-BUS: JACK server could not be started. Sorry > Sat Nov 3 16:56:21 2012: Starting jack server... > Sat Nov 3 16:56:21 2012: JACK server starting in realtime mode with priority 60 > Sat Nov 3 16:56:21 2012: control device hw:1 > Sat Nov 3 16:56:21 2012: control device hw:1 > Sat Nov 3 16:56:21 2012: [1m[31mERROR: Failed to acquire device > name : Audio1 error : Method "RequestRelease" with signature "i" on > interface "org.freedesktop.ReserveDevice1" doesn't exist > [0m > Sat Nov 3 16:56:21 2012: [1m[31mERROR: Audio device hw:1 cannot be > acquired...[0m > Sat Nov 3 16:56:21 2012: [1m[31mERROR: Cannot initialize driver[0m > 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 > Sat Nov 3 16:56:21 2012: [1m[31mERROR: JackServer::Open() failed with -1[0m > Sat Nov 3 16:56:21 2012: [1m[31mERROR: Failed to open server[0m > Sat Nov 3 16:56:22 2012: Saving settings to > "/home/liveuser/.config/jack/conf.xml" ... > 16:56:36.981 D-BUS: JACK server could not be started. Sorry > 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 > Sat Nov 3 16:56:36 2012: Starting jack server... > Sat Nov 3 16:56:36 2012: JACK server starting in realtime mode with priority 60 > Sat Nov 3 16:56:36 2012: control device hw:1 > Sat Nov 3 16:56:36 2012: control device hw:1 > Sat Nov 3 16:56:36 2012: [1m[31mERROR: Failed to acquire device > name : Audio1 error : Method "RequestRelease" with signature "i" on > interface "org.freedesktop.ReserveDevice1" doesn't exist > [0m > Sat Nov 3 16:56:36 2012: [1m[31mERROR: Audio device hw:1 cannot be > acquired...[0m > Sat Nov 3 16:56:36 2012: [1m[31mERROR: Cannot initialize driver[0m > Sat Nov 3 16:56:36 2012: [1m[31mERROR: JackServer::Open() failed with -1[0m > Sat Nov 3 16:56:36 2012: [1m[31mERROR: Failed to open server[0m > Sat Nov 3 16:56:38 2012: Saving settings to > "/home/liveuser/.config/jack/conf.xml" ... > > (N.B. it's also trying to open hw:1 for both play and capture, though > I've set them differently in the GUI) So it looks like the dbus > release request is unsuccessful if the interface has already been > claimed by pulse. > > Starting at the command line or without the dbus interface and > separate -P and -C devices works as expected. > > Finally, it's possible, though I'm not 100% certain, that I've seen > jackdbus used (pulse jack sinks/sources created automatically) when > the 'Use DBUS' option is disabled (and qjackctl has been restarted). > But I've been round this cycle quite a few times now, so I could be > wrong. > > By the way, thanks very much for QJackCtl, been using it happily in > earlier Fedora releases for a while now. It'll be the final piece of > the puzzle in having all this working seemlessly if the dbus stuff can > work properly. > apparently the same issue as in http://sourceforge.net/p/qjackctl/tickets/2/ workaround: do not set the number of input or output channels for a alsa device and while using jackdbus interface--always leave both to default byee -- rncbc aka Rui Nuno Capela rn...@rn... |
From: Ian M. <ibm...@gm...> - 2012-11-03 22:22:10
Attachments:
QjackCtl.conf
|
On 3 November 2012 17:42, Rui Nuno Capela <rn...@rn...> wrote: > On 11/03/2012 09:02 PM, Ian Malone wrote: >> Hi, >> >> I'm having a number of problems with jack on Fedora 18 (development) >> and think they may be related to QJackCtl. I'm not sure if it's all >> the same problem or several different ones, it's also odd in that the >> behaviour changes, despite using a Live boot ISO. >> >> The first thing I'm noticing is that despite setting separate input >> and output devices in settings, qjackctl appears to start Jack with >> the same device for input and output. I don't know if that's a >> qjackctl problem, or something to do with jackdbus itself. >> >> At the same time, if pulse has been used then dbus fails to start, >> looking like this: >> 16:56:21.422 D-BUS: JACK server could not be started. Sorry >> Sat Nov 3 16:56:21 2012: Starting jack server... >> Sat Nov 3 16:56:21 2012: JACK server starting in realtime mode with priority 60 >> Sat Nov 3 16:56:21 2012: control device hw:1 >> Sat Nov 3 16:56:21 2012: control device hw:1 >> Sat Nov 3 16:56:21 2012: [1m [31mERROR: Failed to acquire device >> name : Audio1 error : Method "RequestRelease" with signature "i" on >> interface "org.freedesktop.ReserveDevice1" doesn't exist >> [0m >> Sat Nov 3 16:56:21 2012: [1m [31mERROR: Audio device hw:1 cannot be >> acquired... [0m >> Sat Nov 3 16:56:21 2012: [1m [31mERROR: Cannot initialize driver [0m >> 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 >> Sat Nov 3 16:56:21 2012: [1m [31mERROR: JackServer::Open() failed with -1 [0m >> Sat Nov 3 16:56:21 2012: [1m [31mERROR: Failed to open server [0m >> Sat Nov 3 16:56:22 2012: Saving settings to >> "/home/liveuser/.config/jack/conf.xml" ... >> 16:56:36.981 D-BUS: JACK server could not be started. Sorry >> 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 >> Sat Nov 3 16:56:36 2012: Starting jack server... >> Sat Nov 3 16:56:36 2012: JACK server starting in realtime mode with priority 60 >> Sat Nov 3 16:56:36 2012: control device hw:1 >> Sat Nov 3 16:56:36 2012: control device hw:1 >> Sat Nov 3 16:56:36 2012: [1m [31mERROR: Failed to acquire device >> name : Audio1 error : Method "RequestRelease" with signature "i" on >> interface "org.freedesktop.ReserveDevice1" doesn't exist >> [0m >> Sat Nov 3 16:56:36 2012: [1m [31mERROR: Audio device hw:1 cannot be >> acquired... [0m >> Sat Nov 3 16:56:36 2012: [1m [31mERROR: Cannot initialize driver [0m >> Sat Nov 3 16:56:36 2012: [1m [31mERROR: JackServer::Open() failed with -1 [0m >> Sat Nov 3 16:56:36 2012: [1m [31mERROR: Failed to open server [0m >> Sat Nov 3 16:56:38 2012: Saving settings to >> "/home/liveuser/.config/jack/conf.xml" ... >> >> (N.B. it's also trying to open hw:1 for both play and capture, though >> I've set them differently in the GUI) So it looks like the dbus >> release request is unsuccessful if the interface has already been >> claimed by pulse. >> >> Starting at the command line or without the dbus interface and >> separate -P and -C devices works as expected. >> >> Finally, it's possible, though I'm not 100% certain, that I've seen >> jackdbus used (pulse jack sinks/sources created automatically) when >> the 'Use DBUS' option is disabled (and qjackctl has been restarted). >> But I've been round this cycle quite a few times now, so I could be >> wrong. >> >> By the way, thanks very much for QJackCtl, been using it happily in >> earlier Fedora releases for a while now. It'll be the final piece of >> the puzzle in having all this working seemlessly if the dbus stuff can >> work properly. >> > > apparently the same issue as in > http://sourceforge.net/p/qjackctl/tickets/2/ > workaround: do not set the number of input or output channels for a > alsa device and while using jackdbus interface--always leave both to default > Thanks, actually I'm not sure this is it, or at least that I can't use the work around as the channels are already set to 'default' in the qjackctl interface. My QjackCtl.conf is attached. If you think the issue is still in jackd then let me know and I can take the problem there. -- imalone http://ibmalone.blogspot.co.uk |