View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000160 | ardour | bugs | public | 2003-11-29 06:16 | 2008-11-20 23:37 |
| Reporter | oripessach | Assigned To | paul | ||
| Priority | normal | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Summary | 0000160: Jack kicks ardour when loading a large(ish) project. | ||||
| Description | When I start ardour (the CCRMA RPM release) under Fedora Core 1 with a 2.6 kernel, and load an existing project, this is the result: jackd 0.80.0 [... copyright info ...] JACK compiled with System V SHM support loading driver .. creating alsa driver ... ice1712|ice1712|512|2|48000|nomon|swmeter|soft-mode open starting engine Ardour/GTK 0.401.0 running with libardour 0.690.0 Loading UI configuration file /etc/ardour/ardour_ui.rc Loading system configuration file /etc/ardour/ardour_system.rc Loading user configuration file /root/.ardour/ardour.rc Loading session /mnt/extra2/tape1/sedated2/ using snapshot sedated2 client ardour error: awake_at = 983165317 state = 2 timed_out = 0 zombified - calling shutdown handler JACK has shutdown Ardour. jackd: signal 2 received jack main caught signal 2 received signal 15 during shutdown (ignored) Signal 2 received ardour is killing itself for a clean exit Killed Ardour takes a long time to load this project. Since loading a project is not a real-time operation, I don't think it's appropriate for jackd to expect ardour to keep its deadlines. | ||||
| Additional Information | Jackd 0.80, Ardour/GTK 0.401.0 running with libardour 0.690.0, Kernel 2.6.0-test11 (didn't happen with a 2.4 kernel!) The output shown in the description above shows jackd running in soft-mode. I tried doing this as a workaround, and obviously it didn't work. | ||||
| Tags | No tags attached. | ||||
|
|
ori - does this happen every time you try to load the session? does it happen if ardour is already running and you load it from the GUI? answers to these questions will help me track down why this happens. --p |
|
|
This happens every time I load the session, and when I load the session from the GUI. I've seen it happen now with a relatively small session - three tracks, with a moderate number of takes (less then 10). The session worked fine until I saved it and tried to reload it later on. Under the 2.6 preemptable kernel ardour tends to be kicked by jackd a lot more than under 2.4 with the low-latency patch, by the way. |
|
|
I just wanted to add that this still happens with the CVS versions of Jack and Ardour, both compiled on my machine, so this isn't a problem with the specific packages I was using. I am unable to load even small projects - I created a project with four tracks, recorded one take, saved it, and then quit ardour and tried to reload the project. ardour got kicked, with the following output on the xterm: jackd 0.91.3 Copyright 2001-2003 Paul Davis and others. jackd 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 loading driver .. creating alsa driver ... ice1712|ice1712|512|2|48000|0|0|nomon|swmeter|rt|32bit configuring for 48000Hz, period = 512 frames, buffer = 2 periods Ardour/GTK 0.424.0 running with libardour 0.708.0 Loading UI configuration file /usr/local/etc/ardour/ardour_ui.rc Loading system configuration file /usr/local/etc/ardour/ardour_system.rc Loading user configuration file /root/.ardour/ardour.rc MIDI: MTC on port trident MMC on port trident 0 2 0 0 0 0 0 2 0 0 0 0 0 504 0 251 503 0 0 504 0 251 503 0 subgraph starting at ardour timed out (subgraph_wait_fd=9, status = 0, state = T riggered) **** alsa_pcm: xrun of at least 1.488 msecs 0 554 0 277 504 0 0 555 0 277 554 0 0 555 0 277 554 0 Loading session /mnt/extra2/tape1/bee/ using snapshot bee **** alsa_pcm: xrun of at least 0.579 msecs subgraph starting at ardour timed out (subgraph_wait_fd=9, status = 0, state = R unning) client ardour error: awake_at = 420811597971 state = 2 timed_out = 0 **** alsa_pcm: xrun of at least 1.311 msecs zombified - calling shutdown handler JACK has shutdown Ardour. |
|
|
Has anyone had this happen to them lately? I haven't seen it for a while. |
|
|
It sometimes happens to me, too. I use a periodsize of 2*512 and a timeout of 20000[20secs]. I cannot reproduce deterministically but i have observed this with bet19.. |
|
|
I haven't had this happen with fairly large projects for a long time. |
|
|
see bugnotes. this was mostly fixed by handling all initial session events in the GUI thread while locking out the process callback. this is a duplicate of another closed bug |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2003-11-29 06:16 | oripessach | New Issue | |
| 2003-12-02 13:24 | paul | Note Added: 0000211 | |
| 2003-12-02 13:24 | paul | Status | new => feedback |
| 2003-12-02 16:04 | oripessach | Note Added: 0000215 | |
| 2003-12-08 20:35 | taybin | Summary | Jack kicks ardour shen loading a large(ish) project. => Jack kicks ardour when loading a large(ish) project. |
| 2003-12-14 19:08 | oripessach | Note Added: 0000299 | |
| 2004-07-31 23:07 | taybin | Note Added: 0001321 | |
| 2004-08-25 11:56 | mistatapas | Note Added: 0001447 | |
| 2004-12-08 21:51 | vandongen | Note Added: 0001690 | |
| 2004-12-08 22:00 | paul | Status | feedback => resolved |
| 2004-12-08 22:00 | paul | Resolution | open => fixed |
| 2004-12-08 22:00 | paul | Assigned To | => paul |
| 2004-12-08 22:00 | paul | Note Added: 0001691 | |
| 2008-11-20 23:37 | seablade | Status | resolved => closed |
