Absolute paths for external files a big problem

[Taiis]

I'm a software developer and I'm deeply dissatisfied with the idea that Live saves its files with absolute file references eg. "z:\mymusic\project 4\track dingeling\sounds\mywave.wav" instead of "track dingeling\sounds\mywave.wav" (given that the project file was placed in the project 4 directory).

It is extremely bad practice to save file references this way. Always use relative paths instead of absolute ones. Always save file references as relative to the project file.

I hate to sound bitching - but please go read a book on good code practice.

[Robert Henke]

Hi Talis,

we are aware of this issue and we plan changes in the project / file handling.
I cannot promise this for the next release, but it is obvious that there is
room for improvement here.

Robert Henke
Ableton

[musick]

.... we are aware of this issue and we plan changes in the project / file handling ....

When making these changes it might be an idea to also add a 'unique id' based on a hash of e.g. the first 1k bytes to an audiofile reference so Live can distinguish between more files with the same name (like ProTools style relinking).

[Friedemann]

Hi All,

File references are saved absolute *and* relative. If the
absolute reference cannot be resolved, the relative one
is used.

For sets within Live's Library, relative means relative to
the Library's root.

For sets outside of the Library, relative means relative to
the referencing document.

However, we are aware of the limitations of these rules
as Robert said.

Kind regards, Friedemann

[live(atpompeii)]

to me the way live saves files makes sense. I use two pcs with the same loop library on C:, all I do to work on the same sessions on the two is save all my .als and relative sounds on an external drive...
if ableton's going to change this please leave an option to save files "the old way"... thanks!