View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001888 | ardour | bugs | public | 2007-09-24 13:05 | 2008-12-03 04:47 |
| Reporter | artone | Assigned To | |||
| Priority | normal | Severity | major | Reproducibility | always |
| Status | confirmed | Resolution | open | ||
| Product Version | 2.0 | ||||
| Summary | 0001888: Ardour produces corrupted CUE/TOC files when ranges overlap. | ||||
| Description | I was recently working on a project that was a single 1 hour audio file. I was setting up ranges for CD tracks and noticed that the exported files were wrong. Some tracks were missing entirely and other tracks started at offsets > 1600 hours. This seems to happen when ranges overlap, it's easy to reproduce on at least 2.0.3 on freebsd x86 and 2.0.5 OS X PPC. | ||||
| Tags | No tags attached. | ||||
|
|
Confirmed that this is still a problem in Ardour 2.7 on OS X. The way I see it one of a couple of things should probably happen... either a dialog warning that the track marker locations are illegal and export will stop should appear and export should fail in a 'pleasant' way(Aka, not crash) or Ardour needs to automatically modify the track locations to fix it in the export, informing the user that this was done. Between these two I think the earlier one is probably the better solution, as it is the user's responsibility in my opinion, to make sure that the track locations are where they want them. Seablade |
