Format Only when the data has been copied to two
independent devices and verified, should the
drive/card be formatted to clear all data. We
recommend that the person who verifies the
primary and back-up copies should also format
the media. The camera crew then always receives
an empty card and does not need to worry if the
footage has already been copied from the
drive/card. SxS cards can be formatted with any
file system, as it has to be reformatted by the
camera anyway. XR Capture Drives can be
formatted in the Codex software and do not
require to be reformatted in the camera.
File Structure for ProRes/DNxHD Recording
After an SxS card, CFast 2.0 card or XR Capture Drive is formatted for
compressed recording in the camera, it is named ARRI_UDF until the
first clip is recorded. Once a clip has been recorded, the name changes
to the camera index letter and reel number. Clips are stored in a folder
with the same name as the media.
In addition to the clips, recording writes an XML file and an ALE file.
The XML file is a Final Cut Pro 7 (FCP) XML file. When opened in Final
Cut Pro 7, all clips are imported as one bin. If the clips are copied from
the card to another destination, the file paths in the XML file have to be
adjusted to match the new file location. The XML file is not compatible
to FCP X.
The ALE file is an Avid Log Exchange file for Media Composer. It
contains all static clip metadata, which is also embedded in each
recorded clip.
For more information about ALEXA metadata, please refer to the
ALEXA Metadata Whitepaper, available at
http://www.arri.com/camera/digital_cameras/downloads.
File Structure for ARRIRAW Recording (Codex VFS)
When an XR Capture Drive with ARRIRAW footage is loaded on a
computer, it shows up like a regular external drive. Operating
underneath, however, is the Codex Virtual File System (VFS). The VFS
can present, for example, readily processed DPX files, MXF/DNxHD
and/or QuickTime/ProRes proxies next to the original ARI files on the
Codex volume. Except for the recorded data on the drive, none of these
additional files actually exist. It's only when these files are requested,
that they are generated, on-demand, and on the fly. Hence the term
"virtual".
To Next Page
Loading...
