X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=_manual%2F12_adding-pre-existing-material%2F02_copying-versus-linking.html;h=359c9b26753fc5229c965779571fa12ba018dae9;hb=65e1ae1ce84238e6118addee59391dbf869bc86b;hp=3167c252ab6b265a0b160fc1fe649d0bb2ff53b9;hpb=e3adb8ef44a7daf61312b42f86c547357ecfbb15;p=ardour-manual diff --git a/_manual/12_adding-pre-existing-material/02_copying-versus-linking.html b/_manual/12_adding-pre-existing-material/02_copying-versus-linking.html index 3167c25..359c9b2 100644 --- a/_manual/12_adding-pre-existing-material/02_copying-versus-linking.html +++ b/_manual/12_adding-pre-existing-material/02_copying-versus-linking.html @@ -6,11 +6,13 @@ title: Copying versus Linking

Copying and linking are two different methods of using existing audio files on your computer (or network file system) - within a session. They differ in one key aspect:

+ within a session. They differ in one key aspect: +

+

Copying

An existing media file is copied to the session's audio folder, and - if necessary is converted into the session's native format.
+ if necessary converted into the session's native format.
For audio files, you can control the choice of this format (eg. WAVE or Broadcast WAVE). Audio files will also be converted to the session sample rate if necessary (which can take several minutes for larger @@ -20,10 +22,11 @@ title: Copying versus Linking MIDI files will already be in SMF format, and are simply copied into the session's MIDI folder.

+

Linking

A link to an existing media file somewhere on the disk is used as a the - source for a region, but the data isnot copied or modified + source for a region, but the data is not copied or modified in any way.