View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000280 | ardour | bugs | public | 2004-02-26 03:24 | 2004-12-24 21:44 |
| Reporter | dbergst | Assigned To | paul | ||
| Priority | normal | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Summary | 0000280: Automation May Incur Excess IO and/or CPU Usage in adour-0.9_beta11 | ||||
| Description | I recently ran into some problems whenever automation is enabled on any track with ardour-0.9_beta11. These were usually indicated as disktream errors in the ardour log window, and when checking the log generated from jackd and ardour (this is run as an sudo session on a script in my home directory), there were playback underruns shown that seemed to correlate with the log window errors. A sample of these errors is copied below: transport Starting, sync poll of 1 clients for 2.000000 secs transport Rolling, 2.000000 sec left for poll load = 35.2009 max usecs: 4043.000, spare = 6623.000 load = 36.4079 max usecs: 4012.000, spare = 6654.000 load = 37.3161 max usecs: 4077.000, spare = 6589.000 load = 38.3140 max usecs: 4193.000, spare = 6473.000 load = 38.1988 max usecs: 4062.000, spare = 6604.000 load = 37.9818 max usecs: 4028.000, spare = 6638.000 DiskStream Vocals:0: playback underrun (called with 512 samples but only 0 available; other half: 0) [speed=1] load = 47.0099 max usecs: 5977.000, spare = 4689.000 transport command: STOP transport Stopped This occurred when I enabled automation recording on one track, then pressing the play transport. | ||||
| Additional Information | My system is an Abit BX6-R2 with a Pentuum III 450 (Katmai), 768 MB RAM, Hammerfall DSP 9652, using reiserfs as the filestore for my audio files, and jack-audio-connection-kit-0.94.0 compiled /dev/shm on tmpfs. Please note that I have already optimized my IRQs and hdparm settings based on the FAQs I read for linux audio, and to reduce the possibility PCI bus contention I am running an Nvidia AGP card with the open source (nv) driver in XFree86 (build from gentoo ebuild xfree-4.3.0-r5). While investigating this issue, I have also set my startup script for jack ardour to shutdown local services that might be in contention, and I have set all of my reiserfs filesystems in /etc/fstab to run with the notail,noatime parameters (noatime was added during my diagnostic sessions), however, the disk stream errors persist whenever automation is enabled and my system latency is set any lower than 11ms (p=1024,n=2@48KHz). My current workaround is to run the gentoo development kernel 2.6.3-r1, and use low latencies as low as 3 ms for recording or non-automated mixdowns, and a setting of 11ms latency or greater if I am mixing down with automnation. | ||||
| Tags | No tags attached. | ||||
|
|
Please test again with the official 0.9beta11.2 release. Automation handling from the audio thread has been redesigned. May not be perfect yet, but it should be much better. You may need to start with a new session or you just try clearing existing automation. The old design stored too many data points and suffered from O(logN) behaviour, which is not real-time safe. |
|
|
I rebuilt and installed ardour using the official 0.9beta11.2 release, unfortunately a new problem with the ardour GUI is preventing me from testing out the new automation fixes in 0.9beta11.2. I cleared out the automation data from the old session, however the GUI is now freezing up whenever I try to use basic features like zoom to session width or show/hide automation tracks. This behavior was identical whether I ran a 2.4 or 2.6 kernel, or if I ran low latency, e.g., 3 ms or high latency, e.g., 48 ms. This problem also persisted after I replaced the ardour.rc file in my home directory with a new copy generated by the new version of ardour. edited on: 03-03-04 20:28 |
|
|
Automation appears to be much less of an issue now. In a recent cvs build of ardour, i.e., Ardour/GTK 0.461.0 running with libardour 0.735.1, after clearing up the GUI issues with zoom, et. al., I was able to use automation since with the new design there is no appreciable CPU load being added when it is enabled. FYI the resolution on the GUI problem is documented in my bugnote of 04Apr04 in the report referenced below. http://ardour.org/mantis/bug_view_page.php?bug_id=0000298 Given the above, I recommend this bug be marked as closed. |
|
|
as per user comment, bug resolved. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2004-02-26 03:24 | dbergst | New Issue | |
| 2004-03-03 13:25 | paul | Note Added: 0000501 | |
| 2004-03-04 04:26 | dbergst | Note Added: 0000502 | |
| 2004-03-04 04:28 | dbergst | Note Edited: 0000502 | |
| 2004-04-04 16:07 | dbergst | Note Added: 0000597 | |
| 2004-04-10 03:37 | paul | Status | new => resolved |
| 2004-04-10 03:37 | paul | Resolution | open => fixed |
| 2004-04-10 03:37 | paul | Assigned To | => paul |
| 2004-04-10 03:37 | paul | Note Added: 0000602 | |
| 2004-12-24 21:44 | dbergst | Status | resolved => closed |
| 2004-12-24 21:44 | dbergst | Fixed in Version | => 0.9beta19 |
