More rephrasing, detailing the interchange page
This commit is contained in:
Ed Ward
parent
232842fa08
commit
5c572efabd
|
|
@ -1,49 +1,87 @@
|
|||
|
||||
<p>
|
||||
Recording and editing any serious session might leave the session with some unused or misplaced files here and there. Ardour can help deal with this clutter thanks to the tools located in the <kbd class="menu">Session > Clean-up</kbd> menu.
|
||||
Recording and editing any serious session might leave the session with some
|
||||
unused or misplaced files here and there. Ardour can help deal with this clutter
|
||||
thanks to the tools located in the <kbd class="menu">Session > Clean-up</kbd>
|
||||
menu.
|
||||
</p>
|
||||
|
||||
<h2 id="bring_all_media_into_session_folder">Bring all media into session folder</h2>
|
||||
|
||||
<p>
|
||||
When <a href="@@adding-pre-existing-material">importing media files</a>, if the <kbd class="option">Copy files to session</kbd> hasn't been checked, Ardour uses the source file from its original destination, which can help avoiding file duplication. Nevertheless, when the session needs to be archived or transfered to another computer, moving the session folder won't move those <em>external</em> files as they are not in the folder, as seen in <a href="@@backup-and-sharing-of-sessions">Backup and sharing of sessions</a>.
|
||||
When <a href="@@adding-pre-existing-material">importing media files</a>, if
|
||||
the <kbd class="option">Copy files to session</kbd> has not been checked, Ardour
|
||||
uses the source file from its original destination, which can help avoiding file
|
||||
duplication. Nevertheless, when the session needs to be archived or transfered
|
||||
to another computer, moving the session folder will not move those
|
||||
<em>external</em> files as they are not in the folder, as seen in <a
|
||||
href="@@backup-and-sharing-of-sessions">Backup and sharing of sessions</a>.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
Using the <kbd class="menu">Bring all media into session folder</kbd> menu ensures that all media files used in the session are located inside the session's folder, hence avoiding any missing files when copied.
|
||||
Using the <kbd class="menu">Bring all media into session folder</kbd> menu
|
||||
ensures that all media files used in the session are located inside the
|
||||
session's folder, hence avoiding any missing files when copied.
|
||||
</p>
|
||||
|
||||
<h2 id="reset_peak_files">Reset Peak Files</h2>
|
||||
|
||||
<p>
|
||||
Ardour represents audio waveforms with peak files, that are graphical images generated from the sound files. This generation can be time and CPU consuming, so it uses a cache of the generated images to speed up the display process. To watch for files modification, Ardour relies on the file-modification time. If an external file is embedded in the session and that file changes, but the system-clock is skewed or it is stored on an external USB disk (VFAT), Ardour can't know the change happend, and will still use its deprecated peak files.
|
||||
Ardour represents audio waveforms with peak files, that are graphical images
|
||||
generated from the sound files. This generation can be time and CPU consuming,
|
||||
so it uses a cache of the generated images to speed up the display process. To
|
||||
watch for files modification, Ardour relies on the file-modification time. If an
|
||||
external file is embedded in the session and that file changes, but the
|
||||
system-clock is skewed or it is stored on an external USB disk (VFAT), Ardour
|
||||
can't know the change happend, and will still use its deprecated peak files.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
Using the <kbd class="menu">Reset Peak Files</kbd> menu allows to reset this cache, which frees up disk space, and forces the re-creation of the peak files used in the session. It can prove useful if some waveforms are not used anymore, or if a graphical or time glitch happens.
|
||||
Using the <kbd class="menu">Reset Peak Files</kbd> menu allows to reset this
|
||||
cache, which frees up disk space, and forces the re-creation of the peak files
|
||||
used in the session. It can prove useful if some waveforms are not used anymore,
|
||||
or if a graphical or time glitch happens.
|
||||
</p>
|
||||
|
||||
<h2 id="clean_up_unused_sources">Clean-up Unused Sources…</h2>
|
||||
|
||||
<p>
|
||||
Recording usually lefts a lot of unused takes behind, be it in midi or audio form, that can clutter the Region List, and eat up a lot of hard drive space. While its generally a good practice to keep as many things as possible while recording, when transferring or archiving the session, some clean up can help a lot in reducing the sessions clutter and size.
|
||||
<p>
|
||||
Recording usually leaves a lot of unused takes behind, be it in midi or audio
|
||||
form, that can clutter the Region List, and eat up a lot of hard drive space.
|
||||
While its generally a good practice to keep as many things as possible while
|
||||
recording, when transferring or archiving the session, some clean up can help a
|
||||
lot in reducing the sessions clutter and size.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
Selecting <kbd class="menu">Clean-up Unused Sources…</kbd> will force Ardour to detect those unused waveforms by looking for unused regions, and (through a prompt) for unused playlists. The media files won't be destroyed, though. At this stage, they are just copied in a particular place of the session path (namely, in the <code>dead sounds/</code> sub-folder).
|
||||
Selecting <kbd class="menu">Clean-up Unused Sources…</kbd> will force
|
||||
Ardour to detect those unused waveforms by looking for unused regions, and
|
||||
(through a prompt) for unused playlists. The media files will not be destroyed,
|
||||
though. At this stage, they are just copied in a particular place of the session
|
||||
path (namely, in the <code>dead sounds/</code> sub-folder).
|
||||
</p>
|
||||
|
||||
<h2 id="flush_wastebasket">Flush Wastebasket</h2>
|
||||
|
||||
<p>
|
||||
Although Ardour is a <em>non-destructive</em> audio-editor, it allows for a very careful destruction of unused media materials. This function is closely linked to the previous one. When the unused sources have been cleaned up and quarantined, the <kbd class="menu">Flush Wastebasket</kbd> menu will allow for their physical destruction.
|
||||
Although Ardour is a <em>non-destructive</em> audio-editor, it allows for a
|
||||
very careful destruction of unused media materials. This function is closely
|
||||
linked to the previous one. When the unused sources have been cleaned up and
|
||||
quarantined, the <kbd class="menu">Flush Wastebasket</kbd> menu will allow for
|
||||
their physical destruction.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
As a safeguarding mechanism though, Flushing the wastebasket in impossible in the same working session as the Cleaning up of unused sources: the user needs to close the session and reload it before flushing. It allows to test the playback of the session and ensure both that Ardour didn't commit any mistake (unlikely, but better safe than sorry), and that the user is absolutely sure of what he does.
|
||||
As a safeguarding mechanism though, Flushing the wastebasket in impossible
|
||||
in the same working session as the Cleaning up of unused sources: the user needs
|
||||
to close the session and reload it before flushing. It allows to test the
|
||||
playback of the session and ensure both that Ardour did not commit any mistake
|
||||
(unlikely, but better safe than sorry), and that the user is absolutely sure of
|
||||
what he does.
|
||||
</p>
|
||||
|
||||
<p class="warning">
|
||||
Notice that all media destroyed this way is not sent to the system's <em>trash can</em> but permanently deleted. If a file is mistakenly destroyed this way, the user will have to rely on data recovery techniques to try getting it back.
|
||||
All media destroyed this way is not sent to the system's <em>trash can</em> but
|
||||
permanently deleted. If a file is mistakenly destroyed this way, the user will
|
||||
have to rely on data recovery techniques to try getting it back.
|
||||
</p>
|
||||
|
||||
|
|
|
|||
|
|
@ -1,13 +0,0 @@
|
|||
|
||||
<p>
|
||||
All media in a session folder is stored in a sub-folder called
|
||||
<samp>interchange</samp>. Below that is another folder with the name
|
||||
of the session. You can copy either of these to another location and
|
||||
use the files within them with any other application, importing them
|
||||
all into a project/session. You will lose all information about regions,
|
||||
tracks, and timeline positioning, but all the data that Ardour was working
|
||||
with will be present in the other DAW. Nothing below the interchange
|
||||
folder is specific to Ardour—any DAW or other audio/MIDI
|
||||
application should be able to handle the files without any issues.
|
||||
</p>
|
||||
|
||||
|
|
@ -14,17 +14,60 @@
|
|||
specifications that different DAWs support them only partially,
|
||||
differently, or not at all.
|
||||
</p>
|
||||
<h2>Moving an Ardour session to another DAW</h2>
|
||||
<p>To move an Ardour session to another DAW, you have 3 basic choices:</p>
|
||||
|
||||
<h2>Transfering an Ardour session from / to another DAW</h2>
|
||||
|
||||
<p>
|
||||
To move a session from another DAW to Ardour, or from Ardour to another DAW,
|
||||
there are two basic choices:
|
||||
</p>
|
||||
<ul>
|
||||
<li>Stem exports</li>
|
||||
<li>Copy the interchange folder</li>
|
||||
<li>Use AATranslator</li>
|
||||
</ul>
|
||||
<h3>Moving another DAW session to Ardour</h3>
|
||||
<p>To move a session from another DAW to Ardour, you have 2 basic choices:</p>
|
||||
<ul>
|
||||
<li>Stem exports</li>
|
||||
<li>Use AATranslator</li>
|
||||
<li><a href="@@stem-exports">Stem exports</a></li>
|
||||
<li><a href="#using-aatranslator">Using AATranslator</a></li>
|
||||
</ul>
|
||||
|
||||
<h2>Importing ProTools® files</h2>
|
||||
<p>
|
||||
Ardour provides a basic import tool for ProTools® sessions, in the
|
||||
<kbd class="menu">Session > Import PT Session</kbd> menu.
|
||||
</p>
|
||||
<p>
|
||||
Though incomplete, this import is intended for ptf and ptx files.
|
||||
Protools® 5, 8, 9, 10, 11 have been tested with varying degrees of success.
|
||||
(versions 6 and 7 are not supported).
|
||||
</p>
|
||||
<p>
|
||||
The elements of the files that are imported are:
|
||||
</p>
|
||||
<ul>
|
||||
<li>Audio regions data & position</li>
|
||||
<li>MIDI notes (fused to a unique region).</li>
|
||||
</ul>
|
||||
|
||||
<h2 id="using-aatranslator">Using AATranslator</h2>
|
||||
|
||||
<p>
|
||||
<dfn>AATranslator</dfn> is a Windows application that can convert
|
||||
sessions/projects from many diffferent DAWs into other formats. At the present
|
||||
time (December 2016), it can read and write Ardour 2.X sessions, and can read
|
||||
Ardour 3 sessions.
|
||||
</p>
|
||||
|
||||
<p> The program runs very well on Linux using <a href="http://www.winehq.org/">Wine</a>
|
||||
(a Windows environment for Linux). There are equivalent solutions for running
|
||||
Windows applications on OS X, but we have no experience with them at this time.
|
||||
Ardour users have reported great results using AATranslator on Ardour 2.X
|
||||
sessions.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
The <a href="http://www.aatranslator.com.au/">AATranslator website</a> has
|
||||
full details on supported formats and DAWs. The list includes ProTools, Live,
|
||||
Reaper, OMF, AAF and many more.
|
||||
</p>
|
||||
|
||||
<p class="warning">
|
||||
AATranslator is closed-source, non-free software (as of this writing, June 2017,
|
||||
the cost is 59 USD for the "Standard" version, and 199 USD for the "Enhanced"
|
||||
version).
|
||||
</p>
|
||||
|
|
|
|||
|
|
@ -1,7 +1,8 @@
|
|||
|
||||
<p>
|
||||
<dfn>Session templates</dfn> are a way to store the setup of a session
|
||||
for future use. They do not store any <em>audio</em> data but can store:</p>
|
||||
for future use. They do not store any <em>audio</em> data but can store:
|
||||
</p>
|
||||
<ul>
|
||||
<li>The number of tracks and busses, along with their names</li>
|
||||
<li>The plugins present on each track or bus (if any)</li>
|
||||
|
|
@ -10,22 +11,22 @@
|
|||
|
||||
<h2>Creating a Session Template</h2>
|
||||
<p>
|
||||
Choose <kbd class="menu">Session > Save Template</kbd>. A dialog will ask
|
||||
you for the name of the new template.
|
||||
</p>
|
||||
<h2>Using a Session Template</h2>
|
||||
<p>
|
||||
In the New Session dialog, choose the desired template from the combo
|
||||
selector.
|
||||
</p>
|
||||
<p>
|
||||
Note that you can also use an existing session as a template, without
|
||||
saving it as one. This is available as an option in the New Session dialog.
|
||||
Doing this will not alter the existing session at all, but will use its track,
|
||||
bus and plugin configuration just like a template.
|
||||
</p>
|
||||
<p>
|
||||
See also <a href="@@adding-tracks-busses-and-vcas">Adding Tracks and Busses</a> for information
|
||||
on templates for individual tracks or busses.
|
||||
The <kbd class="menu">Session > Save Template</kbd> shows a dialog asking
|
||||
for the name of the new template.
|
||||
</p>
|
||||
|
||||
<h2>Using a Session Template</h2>
|
||||
<p>
|
||||
In the New Session dialog, a combo selector allows to choose the desired
|
||||
template.
|
||||
</p>
|
||||
<p class="note">
|
||||
An existing session can also be used as a template, without saving it as one.
|
||||
This is available as an option in the New Session dialog. Doing this will not
|
||||
alter the existing session at all, but will use its track, bus and plugin
|
||||
configuration just like a template.
|
||||
</p>
|
||||
<p>
|
||||
See also <a href="@@adding-tracks-busses-and-vcas">Adding Tracks and Busses</a>
|
||||
for information on templates for individual tracks or busses.
|
||||
</p>
|
||||
|
|
|
|||
|
|
@ -1,57 +1,62 @@
|
|||
|
||||
<p>
|
||||
Sometimes you will want to save a <dfn>snapshot</dfn> of the current state of a session for possible
|
||||
use in the future. For example, you may be about to change the entire
|
||||
arrangement of a piece, or drastically alter the signal processing, and
|
||||
want a reference to come back to, should that not work out.
|
||||
A <dfn>snapshot</dfn> is a backup of the current state of a session. It differs
|
||||
from a simple save by allowing branching. It is a "frozen" version of the session
|
||||
at a certain point in time.
|
||||
</p>
|
||||
<p>
|
||||
This is easily accomplished using <kbd class="menu">Session >
|
||||
Snapshot</kbd>.
|
||||
A small dialog will appear, allowing you to enter a name for the snapshot.
|
||||
The default name is based on the current date and time.<br>
|
||||
You can create any number of snapshots.
|
||||
For example, creating a snapshot before changing the entire arrangement of a
|
||||
piece, or drastically altering the signal processing provides a reference to
|
||||
come back to, should that not work out.
|
||||
</p>
|
||||
<p>
|
||||
This is accomplished by using either of the <kbd class="menu">Session >
|
||||
Snapshot</kbd> menus. A small dialog will appear, allowing to enter a name for
|
||||
the snapshot. The default name is based on the current date and time.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
The difference between the two snapshot menus is:
|
||||
</p>
|
||||
<table>
|
||||
<tr>
|
||||
<td><kbd class="menu">Snapshot (& keep working on current version)...</kbd></td>
|
||||
<td>Saves a snapshot of the session, but keeps the current session active, i.e. any
|
||||
subsequent <kbd class="menu">Session > Save</kbd> will overwrite the original
|
||||
session, and the snapshot will remain unchanged.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><kbd class="menu">Snapshot (& switch to new version)...</kbd></td>
|
||||
<td>Saves a snapshot of the session, and uses this snapshot as the current
|
||||
active session, i.e. any subsequent <kbd class="menu">Session > Save</kbd>
|
||||
will overwrite the snapshot, and the original session will remain unchanged.</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
<p>
|
||||
Any number of snapshots can be created.
|
||||
</p>
|
||||
<p class="warning">
|
||||
Creating a snapshot does <strong>not</strong> modify your session,
|
||||
nor does it save your session. Instead, it saves an alternate version
|
||||
Creating a snapshot does <strong>not</strong> modify the session,
|
||||
nor does it save the session. Instead, it saves an alternate version
|
||||
of the session, within the session folder. The snapshot shares all data
|
||||
present in the session.
|
||||
</p>
|
||||
<p>
|
||||
After creating a snapshot, you can continue working on the session and
|
||||
save it normally using <kbd class="menu">Session > Save</kbd> and any
|
||||
existing snapshots will remain unchanged.
|
||||
</p>
|
||||
|
||||
<h2>Switching to a Snapshot</h2>
|
||||
<p>
|
||||
If you are already working on a session and want to to switch to an
|
||||
existing snapshot, navigate the <a href="@@the-snapshot-list">Snapshot List</a>.
|
||||
Find the name of the snapshot in the list and click it. Ardour will switch
|
||||
to the snapshot. If there are unsaved changes in the current session, Ardour
|
||||
will ask what you want to do.
|
||||
Switching to an existing snapshot is done by navigating the
|
||||
<a href="@@the-snapshot-list">Snapshot List</a> and clicking the the name of
|
||||
the desired snapshot. Ardour will switch to the snapshot, and, if there are
|
||||
unsaved changes in the current session, offer to save them.
|
||||
</p>
|
||||
|
||||
<h2>Starting Ardour With a Snapshot</h2>
|
||||
<p>
|
||||
Since a snapshot is just another session file stored within the session
|
||||
folder, you can specify that "version" when loading an existing session.
|
||||
folder, that "version" can be chosen when loading an existing session.
|
||||
The browser in the "Open Session" dialog will show an expander arrow for
|
||||
sessions that have more than 1 session file (i.e. snapshots)
|
||||
present—click on it to see the list, and then click on the name of the
|
||||
snapshot you want to load.
|
||||
sessions that have more than one session file (i.e. snapshots)
|
||||
present. Clicking on it shows the list, and then clicking on the name of the
|
||||
snapshot loads it.
|
||||
</p>
|
||||
|
||||
<h2>Saving and Switching to a Snapshot</h2>
|
||||
<p>
|
||||
Sometimes you may want to create a snapshot and then have all future
|
||||
edits and modifications saved to that snapshot rather than the main
|
||||
session. This is easily done using <kbd class="menu">Session > Save
|
||||
As</kbd>. This does not create a new session folder, but saves your
|
||||
session as a new snapshot and then switches the "current snapshot"
|
||||
to the newly created one. All subsequent saves of the session will
|
||||
be stored in this new snapshot, and existing snapshots (and the main
|
||||
session) will be left unaffected.
|
||||
</p>
|
||||
|
||||
|
|
|
|||
|
|
@ -1,10 +1,11 @@
|
|||
|
||||
<p>
|
||||
<dfn>Stem exports</dfn> are covered fully in the
|
||||
<a href="@@mixdown">Export</a> chapter. A stem export creates one file
|
||||
per track, starting at the beginning of the session. You can then import
|
||||
each track into another DAW and begin working on it. You lose all data
|
||||
except the actual audio/MIDI (no plugins, no automation). This is one of
|
||||
the most common methods of interchange because it works between all DAWs.
|
||||
<dfn>Stem exports</dfn> are covered fully in the <a href="@@mixdown">Export</a>
|
||||
chapter. A stem export creates one file per track, starting at the beginning of
|
||||
the session. Each track can then be imported into another DAW.
|
||||
</p>
|
||||
<p>
|
||||
All data will be lost except the actual audio/MIDI (no plugins, no automation).
|
||||
This is one of the most common methods of interchange because it works between
|
||||
all DAWs.
|
||||
</p>
|
||||
|
||||
|
|
|
|||
|
|
@ -1,17 +0,0 @@
|
|||
|
||||
<p>
|
||||
<dfn>AATranslator</dfn> is a Windows application that can convert sessions/projects from many diffferent DAWs into other formats. At the present time (December 2016), it can read and write Ardour 2.X sessions, and can read Ardour 3 sessions.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
The program runs very well on Linux using <a href="http://www.winehq.org/">Wine</a> (a Windows environment for Linux). There are equivalent solutions for running Windows applications on OS X, but we have no experience with them at this time. Ardour users have reported great results using AATranslator on Ardour 2.X sessions.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
The <a href="http://www.aatranslator.com.au/">AATranslator website</a> has full details on supported formats and DAWs. The list includes ProTools, Live, Reaper, OMF, AAF and many more.
|
||||
</p>
|
||||
|
||||
<p class="warning">
|
||||
AATranslator is closed-source, non-free software (as of this writing, Dec. 2016, the cost is 60 USD for the "Standard" version, and 200 USD for the "Enhanced" version).
|
||||
</p>
|
||||
|
||||
|
|
@ -1103,22 +1103,6 @@ uri: working-with-sessions/interchange-with-other-daws
|
|||
part: subchapter
|
||||
---
|
||||
|
||||
---
|
||||
title: Copying The Interchange Folder
|
||||
include: copying-the-interchange-folder.html
|
||||
link: copying-the-interchange-folder
|
||||
uri: working-with-sessions/interchange-with-other-daws/copying-the-interchange-folder
|
||||
part: subchapter
|
||||
---
|
||||
|
||||
---
|
||||
title: Using AATranslator
|
||||
include: using-aatranslator.html
|
||||
link: using-aatranslator
|
||||
uri: working-with-sessions/interchange-with-other-daws/using-aatranslator
|
||||
part: subchapter
|
||||
---
|
||||
|
||||
---
|
||||
title: Playback & Recording
|
||||
uri: recording
|
||||
|
|
|
|||
Loading…
Reference in New Issue