View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001192 | ardour | bugs | public | 2006-02-14 00:08 | 2020-04-19 20:12 |
| Reporter | jwoithe | Assigned To | seablade | ||
| Priority | normal | Severity | minor | Reproducibility | random |
| Status | closed | Resolution | fixed | ||
| Product Version | 0.99 | ||||
| Summary | 0001192: Importing multiple files at once confuses region list | ||||
| Description | The region import dialog allows multiple audio files to be selected with <shift>-click. If this is done it seems that the resulting region list can get confused. The correct number of regions are created (one per audio file selected for import) but at times the regions do not end up referring to the audio file they should. For example, if you select 4 files for import you end up with 4 regions - a, b, c and d for instance, corresponding to files a.wav, b.wav, c.wav and d.wav respectively. In the fault condition, dragging region c to a track might result in the audio from b.wav appearing instead. On reloading a session affected by this, ardour sometimes decides that it needs to recreate peak files for some of the imported files. With multiple session opens, this has in the past resulted in more than 10 peak files being created in the sounds/ directory for an affected source. Each one seems to be identical in content and each subsequently created one has an additional underscore appended to the name to differentiate it from the others. The result: files with 1, 2, 3, ..., 10 underscores. | ||||
| Additional Information | Not yet verified with 0.99.1. | ||||
| Tags | No tags attached. | ||||
|
|
This bug has not been seen in any recent version of Ardour(2.x) so I am going to go ahead and resolve this issue in about a week unless you can recreate it and post here to confirm it with Ardour 2.7 or newer? Thank you. Seablade |
|
|
I am happy for this to be marked as "resolved in 2.x". While I haven't explicitly tested for it under 2.x I haven't noticed any issues in this area when using 2.x. Thus the evidence is strongly suggestive that it is no longer a problem in the 2.x codebase. |
|
|
Ok going ahead and resolving this issue then. Thank you for getting back to me. Seablade |
|
|
Issue has been closed automatically, by Trigger Close Plugin. Feel free to re-open with additional information if you think the issue is not resolved. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2006-02-14 00:08 | jwoithe | New Issue | |
| 2008-12-03 20:16 | seablade | Note Added: 0005486 | |
| 2008-12-03 20:16 | seablade | Status | new => feedback |
| 2008-12-03 20:16 | seablade | cost | => 0.00 |
| 2008-12-03 20:16 | seablade | Product Version | 0.99 => |
| 2008-12-03 20:17 | seablade | Product Version | => 0.99 |
| 2008-12-03 22:21 | jwoithe | Note Added: 0005488 | |
| 2008-12-03 22:53 | seablade | Status | feedback => resolved |
| 2008-12-03 22:53 | seablade | Resolution | open => fixed |
| 2008-12-03 22:53 | seablade | Assigned To | => seablade |
| 2008-12-03 22:53 | seablade | Note Added: 0005489 | |
| 2020-04-19 20:12 | system | Note Added: 0021477 | |
| 2020-04-19 20:12 | system | Status | resolved => closed |
