View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0009697 | ardour | bugs | public | 2024-04-24 19:19 | 2024-04-24 19:32 |
| Reporter | Joysn71 | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | sometimes |
| Status | new | Resolution | open | ||
| Platform | Debian GNU | OS | Linux | OS Version | (any) |
| Product Version | 8.6 | ||||
| Summary | 0009697: Ardour reports “disk system was not able to keep up with Ardour” when moving MIDI note or loop end marker during looping | ||||
| Description | When a region is looping, and I move a MIDI note or the loop end marker, the message “disk system was not able to keep up with Ardour” is reported. It happens quite often, but not always. I attached a Ardour session where it happens. I muted the tracks as it does not matter. I can reproduce it starting with a small loop region, and while looping, move the loop end marker to increase the looping region. Ardour logs the following message to the console when the issue happens: underrun for player:Zyn Kick 1 1-10.1 Available samples: 0 required: 1024 During my attempts to force the issue, Ardour crashed with the following message while I was clicking into the MIDI track "Kick 1". Althouth this is not related :) terminate called after throwing an instance of 'std::logic_error' what(): basic_string::_M_construct null not valid Aborted | ||||
| Tags | No tags attached. | ||||
|
|
The Ardour session can found here: https://drive.google.com/file/d/1qHukFJuT8xsmNy5XncST0ixTeJ37UpVW/view?usp=sharing And, as I noticed it: can it be that Ardour keeps states of removed plugins in the sessions plugin folder? |
