View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002864 | ardour | bugs | public | 2009-10-14 19:38 | 2010-04-24 10:31 |
| Reporter | JayK | Assigned To | |||
| Priority | normal | Severity | major | Reproducibility | always |
| Status | new | Resolution | open | ||
| Product Version | 2.8.2 | ||||
| Summary | 0002864: Ardour and Jack lose connection when Ardours stops playback | ||||
| Description | When jack is run in realtime mode and Ardour stops playing (e.g. if you stop playback with the space bar or the end marker is reached, but it also happens if the end of one of the songs I'm working on is near but not yet reached) Ardour and jack lose their connection. Ardour displays the according dialog box assuming Ardour was too slow and on the console appears: subgraph starting at ardour timed out (subgraph_wait_fd=[some changing integer number, e.g. 14], status = 0, state = Running, pollret = 0, revents = 0x0) When I try to reconnect without closing Ardour it loses the connection right after I tell him to resume playback. The only chance is to exit Ardour completely to get it another time working until playback stops again. I tried it with a lot of different buffer/period size combinations including the one with the worst latency but the error is always reproducable. However if I disable realtime mode, it works. Even at low latency settings, but I assume it would be better not to do records with these settings without realtime mode enabled. I've got the impression this looks somewhat similar to this issue, but it is rather old (2005): http://tracker.ardour.org/view.php?id=1148 Note on the version number: this actually applies both to 2.7.? (which ships with Ubuntu Jaunty) and the brand new 2.8.3 which is not yet selectable in the appropriate checkbox here | ||||
| Tags | No tags attached. | ||||
|
|
I see this as well, but it's quite intermittent. If I'm recording it might happen once in 50 - 100 takes. |
|
|
In addition, Reconnect to JACK no longer works, ardours brings up a dialog box saying it can't reconnect. |
|
|
the reconnect issue was fixed by the time that 2.8.3 was released. |
|
|
i'm going to take a guess that this is due denormals. try two things: (1) enable the option that stops plugins when the transport stops (2) turn on various kinds of denormal protection. if you don't know what denormals are and want to, google is your friend. |
|
|
I've turned on both of those and it still happens. Reconnect is working again though! |
|
|
does adding -Z and -t 9000 to the jackd options help? btw, i've seen this too, sporadically. funny thing is, it doesn't happen after recording 16 channels for short periods, but when i do a live recording of more than an hour or so, ardour frequently kicks the bucket when i press "stop", same symptoms as described by OP. |
|
|
I'll try those options and report back! By the way, reconnecting to Jack works most of the time, but I had an instance today where it was unable to reconnect some of the tracks. I had to quit without saving to avoid having to redo the routing on a bunch of tracks. @paul: I've enabled the option to stop plugins when the transport stops, but the DSP status still shows ~ 20%. Is this expected? |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2009-10-14 19:38 | JayK | New Issue | |
| 2009-10-16 00:17 | nickm | Note Added: 0006712 | |
| 2009-10-16 00:18 | nickm | Note Added: 0006713 | |
| 2009-10-31 14:38 | paul | Note Added: 0007031 | |
| 2009-10-31 14:39 | paul | Note Added: 0007032 | |
| 2009-11-01 21:07 | nickm | Note Added: 0007064 | |
| 2009-11-03 14:17 | nettings | Note Added: 0007069 | |
| 2009-11-03 19:32 | nickm | Note Added: 0007070 | |
| 2010-04-24 10:28 | cth103 | Category | bugs => bugs2 |
| 2010-04-24 10:31 | cth103 | Category | bugs2 => bugs |
