View Issue Details
|ID||Category||Date Submitted||Last Update|
|0008478||bugs||2020-11-27 15:38||2021-07-20 11:19|
|Fixed in Version|
|Summary||0008478: Regular disk read errors|
|Description||Since using Ardour 6.5 I have started getting disk read errors in a large-ish editing project. I've never had any of these errors before (on any hardware). The error is:|
"The disk system on your computer was not able to keep up with Ardour. Specifically, it failed to read data from disk quickly enough to keep up with playback."
I've git bisected this to find that commit 8b048bb35155e992ddead37cfd00aedc94ec71b5 is the first bad commit.
|Steps To Reproduce||The error seems to most often happen when adjusting the start point of a region backwards as the playhead is approaching. i.e. while playing or looping:|
|Additional Information||Fairly certain this is not a hardware issue as:|
1. I've never had this error before
2. It doesn't happen with builds before commit 8b048bb
3. I've got the error with the session files copied to 3 different disks including an NVMe SSD
|Tags||No tags attached.|
||I have the same experience as mkp.|
I'm experiencing the same behaviour on macOS when playback returns to the beginning of a loop in 6.6-359.
Looking at the patch the original reporter referenced, all it really does is improve error reporting, so it's revealing an issue that was already present rather than causing it.
I'm still getting this error with 6.8.0. It makes Ardour unusable when doing detailed editing with loop playback.
For the past 6 months I've been building from git and reverting commit 8b048bb, however this no longer works as too much has changed in session_transport.cc.
I'd love to help fix this and am available to assist in debugging.