View Issue Details

IDProjectCategoryView StatusLast Update
0004568ardourbugspublic2020-04-19 20:15
Reporterin0giro Assigned Tocth103  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
PlatformIntel Core2 DuoOSGentoo amd64 + Pro-Audio overlayOS Versionstable/unstable
Target Version3.0 
Summary0004568: audio-search-path & midi-search-path are quadrupled when session-dir includes sym-link
Descriptionwhen creating a new session when the session directory is located in a path that includes a symlink, the audio-search-path & midi-search-path contain the default session path (perhaps already a bug http://tracker.ardour.org/view.php?id=4552 ) 4 times for each.
Steps To Reproduce1. create a new session somewhere below a symlink
2. create an audio track
3. create a MIDI track
4. save session

look at the session file or go to Session/Preferences Media tab to confirm the extra duplicates of the audio & MIDI search paths
TagsNo tags attached.

Activities

cth103

2012-03-05 00:34

administrator   ~0012851

Fixed in SVN 11592.

in0giro

2012-03-05 18:14

reporter   ~0012854

yes, the quadrupling of the media search paths seems to be fixed in SVN 11592. however, the media search paths still include absolute path, even for the default session file, as filed in http://tracker.ardour.org/view.php?id=4552 . i think it is important for the default session search path to use relative positions so that the session folder can be moved w/out breaking the session.

thanks

in0giro

2012-03-05 18:18

reporter   ~0012855

actually, on a second look, yes the quadrupling is fixed, and the Session/Properties/Media dialog indicates that the default "session" location is there, but the absolute path to the default session file is added as a location anyway, which seems redundant. again, this only happens when the session folder path includes a symbolic link.

system

2020-04-19 20:15

developer   ~0022894

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.

Issue History

Date Modified Username Field Change
2011-12-16 04:27 in0giro New Issue
2011-12-16 13:49 cth103 cost => 0.00
2011-12-16 13:49 cth103 Target Version => 3.0-beta2
2012-01-10 20:45 cth103 Target Version 3.0-beta2 => 3.0-beta3
2012-02-14 17:20 paul Target Version 3.0-beta3 => 3.0 beta4
2012-03-05 00:34 cth103 Note Added: 0012851
2012-03-05 00:34 cth103 Status new => resolved
2012-03-05 00:34 cth103 Resolution open => fixed
2012-03-05 00:34 cth103 Assigned To => cth103
2012-03-05 18:14 in0giro Note Added: 0012854
2012-03-05 18:18 in0giro Note Added: 0012855
2012-05-23 15:09 cth103 Target Version 3.0 beta4 => 3.0
2020-04-19 20:15 system Note Added: 0022894
2020-04-19 20:15 system Status resolved => closed