View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006485 | ardour | bugs | public | 2015-07-27 19:52 | 2020-04-17 21:35 |
| Reporter | mc888 | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | no change required | ||
| Product Version | 4.1 | ||||
| Summary | 0006485: xruns at session init | ||||
| Description | First appeared: 4.1 Status bar shows at least 1 xrun at every session init. This is not reported by JACK. | ||||
| Additional Information | Speculation on my part - this must be related to plugin init or disk I/O. Transport has never rolled, so xrun should not be possible. | ||||
| Tags | session, xrun | ||||
|
|
ardour x-runs are not jack x-runs. When adding effects, loading a session or performing similar other non-realtime operations, Ardour will not process audio and simply return in the jack callback (after silencing the output ports). Jack does not see an x-run, but from Ardour's point-of-view there's a dropout. This is intentional, non realtime operations in Ardour should not interfere with other jack clients or bring down all of jack. The x-run counter is cleared when loading a new session. Although probably a bit early (it's done after creating the ports). That could be a considered a bug. I don't always get a xrun in ardour when creating or opening a session and sometimes there's more than one (related to plugin instantiation and/or other things). For now it's left as a reminder that Ardour should one day support click-free insertion of plugins and only "activate" the session when it's ready. You can clear the counter by shift+click on it (shift+click is a general gesture in ardour to reset params). |
|
|
PS. it's a long standing issue and was worse in the past. "First appeared in 4.1" is only because Ardour before 4.1 had no xrun counter itself :) |
|
|
Right, I already know how to clear the counter - at this point I just ignore it and watch for JACK xruns and markers during recording. "Boy who cried wolf" and all.. which has gotten me in trouble. Because the log alert flashes red every time I open a session. It cant connect master out to system playback. Don't know why that's "critical" when master goes to tape (stereo mixdown track). Monitor out goes to system playback. The upshot is I ignore it, but it looks like something's wrong. Then when something really is wrong, I don't notice. > "First appeared in 4.1" is only because Ardour before 4.1 had no xrun counter itself :) Good to know, thanks. |
|
|
"..Because the log alert flashes red every time I open a session.." That's a related but different issue. The classification of many warnings in "info", "warning" and "error" is not really great. Some errors should really be warnings and vice versa, and yet some others should not be mentioned at all. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2015-07-27 19:52 | mc888 | New Issue | |
| 2015-07-27 19:53 | mc888 | Tag Attached: session | |
| 2015-07-27 19:53 | mc888 | Tag Attached: xrun | |
| 2015-07-28 01:53 | x42 | Note Added: 0016966 | |
| 2015-07-28 01:57 | x42 | Note Added: 0016967 | |
| 2015-07-28 16:29 | mc888 | Note Added: 0016968 | |
| 2015-07-28 16:29 | mc888 | Note Edited: 0016968 | |
| 2015-07-28 16:38 | mc888 | Note Edited: 0016968 | |
| 2015-07-28 17:41 | x42 | Note Added: 0016970 | |
| 2020-04-17 21:35 | mc888 | Status | new => closed |
| 2020-04-17 21:35 | mc888 | Resolution | open => no change required |
