Reference Manual

58 Managing Files and Sets
Lets suppose that, in the course of our work on “Tango with Piano.als,“ we get sidetracked: The
piece evolves towards something entirely different, and we feel that it should live in a Project of
its own. So, we “Save As...“ under a new name and in some location outside the current Project,
say the Desktop:
A New Project Was Added by Saving a Live Set Outside its Original Project.
Note that the new project folder has no Samples folder (yet). “Electro with Piano.als“ is still refer-
encing the piano sample from the original Tango Project. There is nothing wrong with this except
for when the Tango Project is moved away or deleted; then “Tango with Piano.als“ will be miss-
ing samples. You can prevent this by collecting external files (page 62). Even after the fact,
Live’s tools for searching missing files (page 59) can help solve this problem.
There is actually no need to keep a Projects Live Set exactly one level below the Project itself.
Within a project folder, you can create any number of sub-folders and move files around to or-
ganize them as desired, although you many need to use the File Manager to “teach“ the Project
about the changes you’ve made (page 66).
In general, Live will do what it can to prevent situations such as orphaned (Project-less) Live Sets,
which have the potential of confusing both the user and Live’s file management tools. It cannot,
however, control situations in which Sets or files are moved out of order and become disorga-
nized via the Explorer (Windows)/Finder (Mac).
A note for users of older Live versions: Live does not allow overwriting Live Sets that were cre-
ated by older major versions to prevent compatibility problems. Instead, you will be requested to
“Save As.... Doing this will insure that the newly saved Live Sets reside in project folders.