Treat each P2 card as a structured recording package. A dependable offload preserves that structure, checks the footage and creates a second verified copy before the card returns to production.
Identify the card, camera and reading route
Record the camera model, card type, recording format and the reader or camera connection you will use. P2 is a recording-media family; the card label alone does not tell you the picture codec, frame rate or audio layout. Reader, driver, computer and application support must all match the actual material.
Check Panasonic’s P2 Viewer Plus requirements and driver links against the exact operating system. The page lists playback, search, copying and metadata functions, but support differs by platform. Its Mac section describes older systems and explicitly excludes macOS Catalina; that listing should not be read as support for newer macOS releases. Test a representative card on the intended workstation before a large offload.
Keep a source ID such as CameraA_Card003 in the log and on the outer destination folder. Record who supplied the card, the expected shoot and whether the recording may continue onto another card. If the computer asks to initialize or format an unfamiliar card, cancel and resolve compatibility first.
Keep the whole card structure together
Panasonic’s P2 copying guidance (PDF, January 2008) describes the classic layout: a CONTENTS folder, its component folders and LASTCLIP.TXT. The audio, picture, clip metadata and other files form a set. Copying only a visible video MXF can leave essential companions behind.
The VariCam HS data-handling instructions likewise require CONTENTS and LASTCLIP.TXT together and a separate destination folder for each card. That manual also describes an AVCLIP variation associated with microP2-compatible devices. Preserve the structure actually recorded by the camera instead of reconstructing it from a simplified diagram.
- Create a fresh outer folder for this card. Keep the card’s internal filenames and subfolders unchanged.
- Use a compatible P2-aware copying application or the copying method documented for the equipment. Copy every required top-level item and its contents.
- Save the copy report, including errors and the source/destination paths. Keep logs outside the preserved card tree.
- Make an independent second copy and compare it with the source or verified baseline. Record the verification method and its result.
Import spanned clips as complete recordings
A long take can cross a file boundary or continue onto another card. Collect all cards belonging to the take before judging its completeness. Place their intact copies in separate folders at the same level so a compatible importer can see the group.
Adobe’s Premiere Pro 2015 reference (PDF, printed pages 138–139) documents how its Media Browser assembles P2 spanned clips when the component files and XML are present. This is a useful explanation of the dependency, while the current Premiere format-support page is the place to check current P2 support. Use the import workflow for your installed editor and verify the resulting clip, rather than assuming every MXF is an independent take.
Compare the expected take duration with the imported duration. Watch and listen through every card boundary. A clip that opens successfully may still represent only the first part of the recording. Missing audio can be an import, routing or missing-companion-file issue; keep the originals intact while investigating.
Check both files and content
| Check | Record the evidence |
|---|---|
| Complete file set | Source and destination paths, file inventory, copy errors and retained folder structure. |
| Byte integrity | Checksum algorithm, manifest or verified-copy report, and comparison result. |
| Complete recordings | Expected takes, durations, all card-spanning joins, beginning and ending. |
| Picture and sound | Representative playback, required audio channels, sync and any visible or audible faults. |
| Metadata and backups | Clip IDs, timecode needed for the project, camera notes and independent backup locations. |
Checksums answer whether files match a baseline. Playback and an inventory answer whether the expected recording is present and usable. Record the scope of review: sampling a few clips is a different result from reviewing an entire shoot.
Use the P2 card-offload log for each card, and cross-reference all cards in a spanned take. Keep verification reports with the project. A practical release decision names the person who reviewed the results and identifies any unresolved issue.
Separate preserved sources from editing files
Import or transcode from a working copy after the retained card copies are checked. Store proxies, renders and project files outside the source tree. Keep a record connecting derivatives to the original card and clip IDs so an edit can be relinked later.
Release a card for reuse only after the agreed copy and content checks are complete and independent backups are available. Follow the camera’s documented card-management procedure at that point. A copy failure or missing take calls for investigation before any erase or repair operation.
For choosing retained masters and viewing copies, see lossless codecs and file strategy. For recordings on an older external hard-disk recorder, use the FireStore transfer guide.