View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000909 | ardour | bugs | public | 2005-02-24 05:16 | 2008-11-20 23:43 |
| Reporter | RossPJohnson | Assigned To | paul | ||
| Priority | normal | Severity | crash | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Summary | 0000909: ctrl-button1 in edit region causes termination | ||||
| Description | Ctrl-Button1 in any track in any sound region causes Ardour to exit with message:- terminate called after throwing an instance of 'ARDOUR::Crossfade::NoCrossfadeHere' The above does not require that there be overlapping regions and it occurs every time. Several other actions involving overlapped regions also produce the same termination and message. | ||||
| Additional Information | version 0.9beta26 Fedora Core 3 CCRMA built RPMs | ||||
| Tags | No tags attached. | ||||
|
|
this is hard to comment on. this exception is thrown from one place only - the crossfade constructor. its also caught in the only place that a new crossfade is created. i'll keep looking. btw. it doesn't happen for me, obviously ;) |
|
2005-02-25 02:25
|
|
|
|
More clues hopefully:- Got the same exception termination when I pressed the transport stop button after playing a track that I'd just recorded. I also got the same again when I restarted ardour and re-opened the session choosing 'recover from crash'. So maybe there's a clue in the session files that I've uploaded (.ardour and .pending files only - others needed. There were no crossfade regions or overlapping regions anywhere. There were only two tracks in the session where I had just trackjumped the first (channel named 'Mix') to the second track (named 'Final'). 'Mix' included a post-fade insert connected to Jamin. Prior to this I've spent several hours processing tracks this way without problems. I'm beginning to really like Ardour as I get to know it (after four days). So I'm posting bugs as I find them - before I get too familiar with it and start subconsciously avoiding problem areas. |
|
|
Do you use IRC? any chance of you joining us at #ardour on freenode.net? |
|
|
Maybe there was an overlap region in the 'Final' channel. A very short snip (a residue from something unintentional) at the start of the track. Don't know if that means anything except it possibly constitutes a cross fade region. |
|
|
I can now also reliably invoke termination as follows (following the clue in previous note):- Start ardour. Create a new session using no template. Create a track using defaults (mono track). Record a short region on this track - need not be connected to anything - records silence. Duplicate the region (places new region at the end the the original). Drag the duplicate region to the start of the track - overlapping original. Ardour terminates with the 'ARDOUR::Crossfade::NoCrossfadeHere' exception. |
|
|
I can confirm that 0.9beta27 (CCRMA build) does NOT crash as I've reported here for 0.9beta26. Thanks. |
|
|
see bugnotes for history. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2005-02-24 05:16 | RossPJohnson | New Issue | |
| 2005-02-24 16:40 | paul | Note Added: 0002048 | |
| 2005-02-25 02:25 | RossPJohnson | File Added: Session.tar.gz | |
| 2005-02-25 02:42 | RossPJohnson | Note Added: 0002052 | |
| 2005-02-25 02:52 | paul | Note Added: 0002053 | |
| 2005-02-25 02:55 | RossPJohnson | Note Added: 0002054 | |
| 2005-02-25 03:11 | RossPJohnson | Note Added: 0002055 | |
| 2005-02-28 22:15 | RossPJohnson | Note Added: 0002065 | |
| 2005-03-07 15:02 | paul | Status | new => resolved |
| 2005-03-07 15:02 | paul | Resolution | open => fixed |
| 2005-03-07 15:02 | paul | Assigned To | => paul |
| 2005-03-07 15:02 | paul | Note Added: 0002091 | |
| 2008-11-20 23:43 | seablade | Status | resolved => closed |
