View Issue Details

IDProjectCategoryView StatusLast Update
0002583ardourbugspublic2020-04-19 20:13
ReporterStealth Assigned Topaul  
PrioritynormalSeveritycrashReproducibilityalways
Status closedResolutionwon't fix 
Product Version2.7.1 
Summary0002583: Ardour and jack2 with D-Bus enabled
DescriptionHello there!

I've just found a problem while running Ardour (2.7.1 atm) and jack2 (1.9.1 atm) compiled with dbus support.

When I run Ardour first time it starts jackd with some parameters (including '-T', non-configurable-by-user). Then I have this:

stealth@carrier:~$ ps aux | grep jack
stealth 3271 0.1 0.5 23860 5972 ? Ssl 16:18 0:02 /usr/bin/jackdbus auto

Ardour starts successfully, but I can't hear any sound. And jackd isn't really running (Ardour says it is though). When I try to reconnect (via JACK -> [Disconnet, Reconnect]):

[ERROR]: could not reconnect system:capture_1 and ardour:Audio 1/in 1 (err = -1)
[ERROR]: could not reconnect system:capture_2 and ardour:Audio 1/in 2 (err = -1)
[ERROR]: could not reconnect ardour:Audio 1/out 1 and ardour:master/in 1 (err = -1)
[ERROR]: could not reconnect ardour:Audio 1/out 2 and ardour:master/in 2 (err = -1)

I tried to launch jackd separately from Ardour:
stealth@carrier:~$ /usr/bin/jackd -p 128 -T -d alsa -n 2 -r 48000 -p 1024 -d hw:0,0
jackdmp 1.9.1
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2008 Grame.
jackdmp 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 server starting in non-realtime mode
creating alsa driver ... hw:0,0|hw:0,0|1024|2|48000|0|0|nomon|swmeter|-|32bit
Using ALSA driver HDA-Intel running on HDA Intel at 0xfc400000 irq 16
configuring for 48000Hz, period = 1024 frames (21.3 ms), buffer = 2 periods
ALSA: final selected sample format for capture: 32bit integer little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 32bit integer little-endian
ALSA: use 2 periods for playback

And when I start Ardour, jackd just exits (returning no error, even in debug mode).

Finally, I tried to remove '-T' ('--temporary') while starting jackd:
stealth@carrier:~$ /usr/bin/jackd -p 128 -d alsa -n 2 -r 48000 -p 1024 -d hw:0,0

and Voila! Ardour starts successfully and disconnects/reconnects from/to jackd just fine.

Prolly it's not Ardour's problem (I'm not deeply-involved in D-Bus work).

Since it's impossible to remove '-T' from the command Ardour runs (I grepped the sources), by now I've compiled jack2 without dbus support, but it'll be nice to see this bug fixed in near future :)

Thanks!
TagsNo tags attached.

Activities

paul

2009-10-13 14:58

administrator   ~0006700

this is not really an ardour bug, more of a conceptual problem. the -T flag is really intended ONLY for use by applications that are starting JACK for their own use. what happens is that ardour attempts connects to JACK to see if it is running, then immediately disconnects. if that instance of JACK was run with -T, it will exit if there are no other JACK clients. i can see no reason why you would run JACK with -T from the command line or from a control app like qjackctl.

if JACK was not running when ardour tried to connect, then ardour will indeed start JACK, and will start it with the -T flag. this means that when ardour exits, if there are no other JACK clients, that instance of JACK will exit too.

system

2020-04-19 20:13

developer   ~0021879

Issue has been closed automatically, by Trigger Close Plugin.
Feel free to re-open with additional information if you think the issue is not resolved.

Issue History

Date Modified Username Field Change
2009-03-14 14:24 Stealth New Issue
2009-10-13 14:58 paul Note Added: 0006700
2009-10-13 14:59 paul cost => 0.00
2009-10-13 14:59 paul Status new => resolved
2009-10-13 14:59 paul Resolution open => won't fix
2009-10-13 14:59 paul Assigned To => paul
2010-04-24 10:28 cth103 Category bugs => bugs2
2010-04-24 10:31 cth103 Category bugs2 => bugs
2020-04-19 20:13 system Note Added: 0021879
2020-04-19 20:13 system Status resolved => closed