View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0005869ardourbugspublic2014-02-24 22:072015-04-05 13:31
ReporterLeatuspenguin Assigned Tox42  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Summary0005869: Ardour cannot find peak files after renaming sessions
DescriptionIf you rename a session, Ardour gives an error message when recording new material, or adding any new regions from the region list onto the timeline. This is the error is gives if you try to drag a region from the region list onto the timeline, after the session has been renamed -

[ERROR]: AudioSource: cannot open peakpath (b) "/home/conor/Desktop/Testttt/peaks/importedaudio-L%A.peak" (No such file or directory)
[ERROR]: AudioSource: cannot open peakpath (b) "/home/conor/Desktop/Testttt/peaks/importedaudio-R%A.peak" (No such file or directory)

The original name of the session was "Testttt". This was renamed to "Test", however, it still seems to be looking for the peak files using the old sessions name, "Testttt".

This is the error message when trying to record new material after the sessions name has been changed -

[ERROR]: importedaudio-1%R.wav: could not write peak file data (Bad file descriptor)
[ERROR]: importedaudio-1%L.wav: could not write peak file data (Bad file descriptor)
[ERROR]: importedaudio-1%R.wav: could not write peak file data (Bad file descriptor)
[ERROR]: importedaudio-1%L.wav: could not write peak file data (Bad file descriptor)
[ERROR]: importedaudio-1%R.wav: could not write peak file data (Bad file descriptor)
[ERROR]: importedaudio-1%L.wav: could not write peak file data (Bad file descriptor)
[ERROR]: importedaudio-1%R.wav: could not write peak file data (Bad file descriptor)
TagsNo tags attached.

Activities

Leatuspenguin

2014-02-24 22:15

reporter   ~0015684

Forgot to mention that I tested this using the latest Ardour bundle, 3.5.357

x42

2015-04-04 19:27

administrator   ~0016538

this has been fixed.

I can no longer reproduce with 4.0-rc2

Leatuspenguin

2015-04-04 23:41

reporter   ~0016540

Just tested this again using RC2 nightly build and I'm still having the same issue. Tried it on three separate computers and I'm getting the same issue on all of them. Steps to reproduce what you see in the attached images -

Import a file to the timeline
Rename the session
Move file on timeline

2015-04-04 23:42

 

rename_issue.png (47,717 bytes)   
rename_issue.png (47,717 bytes)   

2015-04-04 23:42

 

rename_issue_2.png (3,168 bytes)   
rename_issue_2.png (3,168 bytes)   

x42

2015-04-05 12:29

administrator   ~0016543

bummer. I renamed the session manually : ) That works fine.

Issue reproduced using Menu > Session > Rename.

x42

2015-04-05 12:54

administrator   ~0016544

Last edited: 2015-04-05 12:56

 should [really] be fixed in 4.0-rc2-24-g1395125

Issue History

Date Modified Username Field Change
2014-02-24 22:07 Leatuspenguin New Issue
2014-02-24 22:15 Leatuspenguin Note Added: 0015684
2015-04-04 19:27 x42 Note Added: 0016538
2015-04-04 19:27 x42 Status new => resolved
2015-04-04 19:27 x42 Resolution open => fixed
2015-04-04 19:27 x42 Assigned To => x42
2015-04-04 23:41 Leatuspenguin Note Added: 0016540
2015-04-04 23:41 Leatuspenguin Status resolved => feedback
2015-04-04 23:41 Leatuspenguin Resolution fixed => reopened
2015-04-04 23:42 Leatuspenguin File Added: rename_issue.png
2015-04-04 23:42 Leatuspenguin File Added: rename_issue_2.png
2015-04-05 12:22 x42 Assigned To x42 =>
2015-04-05 12:29 x42 Note Added: 0016543
2015-04-05 12:29 x42 Status feedback => confirmed
2015-04-05 12:54 x42 Note Added: 0016544
2015-04-05 12:54 x42 Status confirmed => resolved
2015-04-05 12:54 x42 Resolution reopened => fixed
2015-04-05 12:54 x42 Assigned To => x42
2015-04-05 12:56 x42 Note Edited: 0016544
2015-04-05 13:31 Leatuspenguin Status resolved => closed