Ticket #121 (reopened defect)
too short timeout for JACK server startup when using certain FireWire devices
|Reported by:||http://wayne.in-giro.org/||Owned by:||-|
Description (last modified by http://nedko.arnaudov.name/) (diff)
i mainly use an external FireWire? audio interface, and it takes a the JACK server/FFADO/etc. a few seconds to start up and return everything is OK. not sure if it is specific to my Edirol FA-66, or the FireWire? bus in general. every time i start a Studio, and thus the JACK server (with the FireWire? driver/interface), via Gladish or LadiTray?, ladishd (i assume) pops up a message saying that starting the JACK server failed, but then immediately after another message pops up saying that the Studio is started, and the JACK server did indeed start and is running fine. however, i think it took too long for ladishd/DBus. here is the relevant info from the ladishd log:
Tue Nov 30 20:44:48 2010: [31mERROR: [0mrun: Starting JACK server failed.
Tue Nov 30 20:44:49 2010: JACK server start detected.
Tue Nov 30 20:44:49 2010: jack conf successfully retrieved
Tue Nov 30 20:44:49 2010: setting connection handlers for graph '/org/ladish/Studio'
Tue Nov 30 20:44:49 2010: setting connection handlers for graph '/org/ladish/Room1'
is it possible to change the timeout in ladishd/DBus service spec/etc. to prevent the slow startup of the JACK server as being flagged as an error?