Written around the shooting day.

Your first offload

Card in, footage safe, evidence written. Five minutes end to end.

1. Create a project File → New Project. Pick where the project package lives — Olycen suggests your largest external disk, and warns if you put it on the boot drive. The project owns your destinations, day structure and reports.
2. Add destinations In the right column, add at least two. Two folders on the same physical disk are one copy, not two, and Olycen says so rather than letting you believe otherwise.
3. Insert the card It appears on the left with its camera type, size and reel name. If the reader is slow (USB 2.0), you are told before you start, not after four hours.
4. Offload Press Offload. Every byte is read once, written to every destination, then read back from each destination and compared. The bar shows copied and verified separately — they are not the same claim.
5. Read the evidence When it finishes, the panel shows checksums, destinations, and whether the card is safe to erase. Format only when Olycen says the evidence is complete.

Proving footage is intact — later

The verification does not end when the job does.

1. Re-verify from MHL Sidebar → Verify from MHL. Point it at any folder with an ascmhl directory — ours or another vendor's. Every file is re-read from disk and compared, and you get a PDF report whether it passes or fails.
2. Hand post a standard We write ASC MHL v2 next to the media. Any MHL tool can verify it without Olycen. That is deliberate: you should not need us to prove your footage is good.
3. Chain of custody Every transfer, verification and format is journaled. The custody report shows who had the material and what was proven, with times.

The rest of the night

Proxies, dailies and reports run after the offload, never competing with it.

1. Proxies Settings → Automation. H.264 or HEVC, written to <Master>/Proxies at the lowest priority.
2. Dailies with your LUT Settings → Automation → Dailies. Load a .cube, choose burn-ins (clip name, timecode, watermark). Olycen is not a grading tool — this is a viewing copy, and if the LUT does not match the log format the colour will be wrong and that is the LUT, not the render.
3. Reports A PDF and CSV are written automatically when a job verifies, into the project package and onto the Master. The report travels with the material.
4. Shot report reconciliation Sidebar → Reconcile. Feed it the script supervisor's CSV; Olycen matches takes to clips by reel and timecode and tells you what is on the report but on no card — the line worth finding before wrap.

Handing it over

Shuttle drives, editorial, or your own cloud.

1. Delivery profiles Editorial, full OCF or a dailies package. The profile decides what goes in; the manifest records what actually went.
2. Your own cloud S3-compatible storage or SFTP, with your keys. There is no Olycen server in the middle — your media never touches our infrastructure.
3. Offline-first A delivery with no connection waits and resumes. It does not fail and it does not lie about having sent something.

On set

The things that matter at 2am.

1. Set dashboard Sidebar → Dashboard. A page on your local network that anyone on the crew can open on a phone. No cloud, no account.
2. Card library Every card Olycen has seen, with fill count and wear level. Cards do not last forever and the library remembers what you cannot.
3. Eject protection A card or disk with a live job will refuse to eject, and macOS shows you the reason in our words. Force-eject still works — the journal is what protects your data, not this.
4. When a card will not mount Olycen tells you it saw the device but could not read it, and walks you through a read-only decision tree. It never suggests initialising or formatting.

Still stuck?

In the app: Help → Export Diagnostics. The file holds app and OS versions, your settings and a summary of transfers — never your media, never your licence, never a secret. Open the zip and read it before you send it; you should not have to take our word for that.

Contact support