It's some difficult to share a project between different computers or systems installed, because in the ".kdenlive" project files the paths are stored as absolute address to media files.

I think that the paths written and interpreted at the project file would be better to be relative to the directory where the ".kdenlive" file is, when the referred files are in the same tree.

Some examples for a "/media/sda3/mywork/myproject.kdenlive"

"/media/sda3/mywork/speech1.mpg" -> "speech1.mpg"

"/media/sda3/mywork/intros/letters1.mpg" -> "intros/letters1.mpg"

"/home/me/hello.avi" -> "/home/me/hello.avi"

"/media/sda3/materials/laugh.ogg" -> "/media/sda3/materials/laugh.ogg"

This is still a severe lack as of Kdenlive 0.9.10 and much important to share or move projects.

If a problem is that some external tool need those absolute paths written somewhere, Kdenlive should act as path parser to maintain relative paths support.

No free lunch. Storing paths relatively brings with it its own issues. One that comes to mind off the top is the location of media spread about on different mount points. Relative paths would have to incorporate symbolic links in order to provide this kind of support. Do-able but yucky.

What may work is the ability to store paths as either relative or absolute values - upon the choice of the user. But that too has issues...

Currently, if absolute paths are replaced by relative ones in .kdenlive file, the applications doesn't find media files.

The «relative paths» feature should combine relative with absolute ones. For example, if one media path is not in the project's file path, then absolute one must be used. In much cases, absolute paths aren't useful for anybody.

/home/user/Videos/myparty/myproject.kdenlive
/home/user/Music/song.wav -> (Maintain absolute if necessary)
/home/user/Videos/myparty/pictures/photo1.jpg -> pictures/photo1.jpg
/home/user/Videos/myparty/scene1.avi -> scene1.avi

Is the responsability of the user to have a good organization of the project.