ClipHow does verified copy work?
Select the source and destinations in Ingest, review the planned operation, and run the copy. ClipLogger checks copied content and reports the outcome for the destinations it actually reached. Inspect the completion record and any verification failure before treating the copy as usable. A destination name, matching byte count, or progress bar alone is not a verified backup.
Do I get an MHL manifest?
The offload workflow can produce ASC MHL verification records. Keep those records with the copied material and inspect the report for the completed run. A manifest documents a particular copy and verification event; its presence does not prove that every later move, modification, or storage failure is covered.
Can I copy one card to multiple destinations at once?
Configure the destinations in Ingest and check which ones the run will use. Completion and verification are destination-specific. If one destination fails or disappears, do not infer its success from another destination finishing. Keep the camera card until the required copies have been verified under your production policy.
When does it say a card is safe to wipe?
Review the source's actual completion and verification state, including all required destinations and any unresolved warning. ClipLogger does not automatically format a card. A label in one run is not a substitute for the production's backup policy or confirmation that the required copies are durable and accessible.
Can it rename files while copying?
Yes. Rename-on-copy rebuilds the copied file's name from a token template (default {date:YYMMDD}_{reel}_{scene}_{shot}_{take}_{original}). It applies to the copies only; the card originals and their sidecars are untouched, and verification is content-based so renaming never weakens it. It is off unless you turn it on for the run or preset.
What happens if I plug in a card I already offloaded?
Ingest checks the card against available prior-run evidence and reports whether work appears to be complete, incomplete, or requires attention. Treat that result as scoped to the media and destinations it can verify now. A reused card name or matching folder name does not prove that a new card is already backed up.
What happens on a failed verify?
Keep the source intact. Inspect the named file, destination, and reported reason, then restore the destination's availability before retrying the affected work. Do not clear the warning by assuming a partial copy is complete. If the result is unclear, retain the run's diagnostics and verify the destination independently before releasing the card.
Can I eject a card while things are running?
Let the app settle active work before ejecting through its available controls. If a card disconnects unexpectedly, inspect Ingest and Jobs for the resulting state and reconnect it before attempting recovery. Do not interpret a disconnected source as a successfully completed offload.
How fast is it?
Transfer speed depends on the source, reader, filesystem, network, destination, and verification work. Use the measured throughput and completion record from your own run. A fast local SSD result does not establish performance on an SMB share or a different card reader.