View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006549 | ardour | bugs | public | 2015-08-29 11:20 | 2015-09-03 20:31 |
| Reporter | unfa | Assigned To | |||
| Priority | normal | Severity | major | Reproducibility | always |
| Status | new | Resolution | open | ||
| Summary | 0006549: Ardour nightly chokes on drawing waveforms | ||||
| Description | The version I'm running: Ardour 4.2.64 "Taking Tiger Mountain" (built from revision 4.2-64-g1387e75) On KX Studio. This happens both in optimized and debug build. This isn't an issue is Ardour 4.2 stable. | ||||
| Additional Information | Scrolling or zooming through the session is extremely slow, and makes Ardour's GUI stutter and lock up for short periods of time (ranging from a fraction of a second to a few seconds). This makes the work take a lot longer, because I need to wait for Ardour to refresh the view. | ||||
| Tags | No tags attached. | ||||
|
2015-08-29 12:46
|
|
|
|
Ok, I'm confused now. I managed to make a screenshot of the Htop window when Ardour is locked up for a moment during a zoom change. First: looks like it's not drawing the waveforms that's making Arodur stutter, it's some suspicious disk I/O activity that's causing that (I/O wait?). I'd expect Ardour to load waveform data into memory to display it, but instead its writing something to disk. No idea what and why. Sometimes I scroll through the session with no problems, other times I experience stutter. Zooming in and out causes the problem to always show up. |
|
|
This stutter happens the same no matter if I look at audio or MIDI regions. Also it doesn't matter if there's 100+ tracks in the session or just 6. |
|
|
GUI stutter but no Audio stutter, right? The waveforms are rendered in the background. and displayed later when they're ready. by default ardour renders the current viewport and one screen left and right. if you zoom or scroll large distances. the GUI won't hang but the waveforms may or may not appear in time. Ardour cannot keep the audio for rendering the waveforms in memory (that's too much data) so there is disk i/o involved. As for the deadlock when zooming. the backtrace in 0006550 is a lot more useful. Thanks. |
|
|
ardour mmap()s the waveform peak files and relies on the OS to cache the files. In your case htop shows that almost all memory is used and your system is even using swap. There's hardly anything left for disk-cache. 6GB RAM for an ardour session?! wow that's HUGE. Are there any heavy plugins involved? samplers or such? |
|
|
x42, the session has more than 120 tracks, probably around 300 plugins used (it'd be cool if Ardour could count these stats for me), mostly Calf EQs and Calf Deessers. No samplers. But the problem exists also when I load a much smaller session. I'll see if depends on the amount of available memory. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2015-08-29 11:20 | unfa | New Issue | |
| 2015-08-29 12:46 | unfa | File Added: IOWR1.png | |
| 2015-08-29 12:51 | unfa | Note Added: 0017119 | |
| 2015-08-29 16:20 | unfa | Note Added: 0017121 | |
| 2015-08-31 17:05 | x42 | Note Added: 0017125 | |
| 2015-08-31 17:10 | x42 | Note Added: 0017126 | |
| 2015-09-03 20:31 | unfa | Note Added: 0017138 |
