View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001191 | ardour | bugs | public | 2006-02-13 23:43 | 2008-11-20 23:57 |
| Reporter | jwoithe | Assigned To | paul | ||
| Priority | normal | Severity | crash | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Summary | 0001191: Moving gain automation points in large session crashes ardour | ||||
| Description | I have a large (2 hour) session comprising around 8 tracks and perhaps 50 regions. When I started adding automation to this project everything worked well. However, it seemed that as the number of automation points increased the stability of ardour decreased. The session has now reached the point where I can change precisely one automation point per ardour run. If I move to a second point and try to change that ardour crashes out with an "abort" as soon as the mouse button is released from the automation point. This was first observed in 0.99, but the behaviour is unchanged in 0.99.1. It doesn't seem to matter where in the session one tries to change automation - whether at the start, in the middle or the end, ardour still crashes as described above. No crash dump yet, but I'll see if I can produce one in the next few days. | ||||
| Additional Information | This *might* be related to another automation issue I observed while working on the above-mentioned session. Initially ardour was quite happy for me to record automation using the mixer while the session played. This worked well. As things progressed however, ardour became less and less responsive to fader changes on the mixer - it seemed it was taking ardour longer and longer to process each move. Eventually it became impossible to use the mixer for this - every move would consume so much time that audio dataflow was interrupted. | ||||
| Tags | No tags attached. | ||||
|
|
The session mentioned above still displays the problem in 0.99.2. It is impossible to add or change more than 3 automation control points without ardour crashing with "abort". Sometimes this occurs after one change, sometimes it takes 3 or so. There is no obvious pattern as to what precisely triggers the abort. |
|
|
ardour2 had at least a dozen major fixes to the code that manages automation data and display. i don't believe this issue exists any more. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2006-02-13 23:43 | jwoithe | New Issue | |
| 2006-04-05 00:45 | jwoithe | Note Added: 0002487 | |
| 2007-02-23 17:45 | paul | Status | new => resolved |
| 2007-02-23 17:45 | paul | Resolution | open => fixed |
| 2007-02-23 17:45 | paul | Assigned To | => paul |
| 2007-02-23 17:45 | paul | Note Added: 0003379 | |
| 2008-11-20 23:57 | seablade | Status | resolved => closed |
