Guide contents
Simple mode

Simple mode

Simple mode is for the everyday job: get this card onto these disks, verified, right now. It's three columns — the live Disks browser, a source-over-destination editor with an action panel, and the Jobs queue — driving the exact same copy-and-verify engine as Advanced mode.

IngestDeck Simple mode — Disks column on the left, source-over-destination editor in the middle, job queue on the right.
The three columns. Both side columns are resizable and their widths are remembered.

Building a job

Sources

Drag into the Sources zone from the Disks browser or straight from the Finder:

  • A whole disk — copies the entire volume; the card's name becomes its folder at the destination.
  • A folder — copies that folder's contents under a folder named after it (expand the disk in the browser and drag any subfolder).
  • A single file — yes, one file is a valid job.
  • Several of any of these — a multi-source job; sources read in parallel lanes, each into its own folder at the destination.

Selection is validated at drop time, with a toast explaining any refusal: role-locked disks bounce, unmounted paths bounce, overlapping selections bounce — and a destination can never be the same volume as a source or sit inside a source (that would copy a folder into itself). Copying between two different folders on the same disk is fine.

Destinations

Drop one or more destination disks or folders below. Two destinations = every source copied to both. The pencil button on a destination row picks a subfolder as this job's copy root instead of the volume root. Rows are removable (×) and clearable while idle.

Where files land — and the no-overwrite rule: each source is copied into a folder named after it at the copy root — drop the card A001 and you get A001/… on every destination. Copying into the same place again is always safe: folders merge, and a name collision keeps both files — the incoming one gets a numbered name. Simple never overwrites and never skips; choosing a different collision behavior (run folders, skip, overwrite…) is an Advanced Copy node setting, and the Settings default policy applies only there.

The action panel

Above the editor sit the job's actions — combine them freely:

ActionWhat it adds to the job
CopyThe verified offload of the originals. The bread and butter.
ConvertTranscodes review proxies. Convert settings… opens the same output editor as Advanced (codec, quality, resolution — see Convert); the summary line shows the current target. With Copy on, proxies land in a Proxies subfolder next to the originals; Convert alone transcodes straight to the destination.
VerifyFull checksum verification — hash the source during the read, read every destination file back from disk, compare. See Verification & MHL. (File sizes are always verified, even with this off.)
EjectEject the source card automatically after the job completes.

Queue it — or run it

The floating pill under the editor commits the draft: Add to queue normally, Add waiting job when sources are empty (a waiting job for Watch mode), or Save changes when editing an existing queued job. Then Run processes the queue top-to-bottom — or Watch arms it (see Watch mode).

The Jobs queue

The right column is the day's ledger, in three sections:

  • Waiting — queued jobs, in run order. Drag rows to reorder (also while a run is active, for the jobs behind it). Click a row while idle to load it back into the editor and change anything. Remove with ×.
  • Running — the active job with its live progress (below). Jobs run strictly one at a time, top to bottom.
  • Finished — this session's completed/failed/stopped jobs. Click one to browse its result or reload its setup as a fresh draft. Clear empties the list — it's a session view; the permanent record lives in History.
The Jobs queue after a run — a skipped waiting job and completed copies, each with its outcome and timestamp.
The queue as the day's ledger: a source-less job skipped by a manual run (Watch would have held it), and completed jobs with their outcomes.

While a job runs

  • Preflight first. Before a byte moves, IngestDeck checks your access, walks the source (you see a live file count), checks destination free space, and — for network destinations — probes that the share actually accepts writes. Problems surface as a toast + log entry before the copy, not as a surprise at 80%.
  • Per-file progress. The running row shows the phase (preparing / copying / verifying / converting), the current file, per-file and overall progress, elapsed time and ETA, and real read/write throughput (MB/s — or frames/sec while converting).
  • Editor locks. Sources/destinations are read-only during a run; queued rows behind the active job stay reorderable.
  • Stop, don't fear. Stop finishes gracefully: everything already copied stays (no rollback, ever), only the in-flight partial file is removed, and the stopped run remains fully browsable. Remaining queued jobs stay queued. Pause/resume is an Advanced-mode feature — Simple offers Stop.
  • Network hiccups are watched. A destination on a network share gets a connectivity watchdog: a soft warning after ~8 seconds of no progress, and a clean, diagnosed failure (destination disconnected) at ~45 — instead of an endless hang.
A multi-source copy mid-run — one source done, the second at 58% with live read speed, the destination write rate, and the running job card with progress, ETA and current file.
Mid-run, two sources: the first already Done, the second reading at 345 MB/s, the destination's write rate below — and the job card with overall progress, elapsed, ETA and the current file.

When it finishes

  • The completion dialog summarizes the job — files, bytes, verification — with Open destination (reveals the copied files in the Finder) and Eject for the source card.
  • The result browser opens the copied tree file by file: ✓/✗ per file, the reason on any failure, hashes when verified. Space QuickLooks a file; double-click opens the media player. Edit as new reloads the job's setup as a fresh draft — tomorrow's identical offload in two clicks.
  • The run is archived to the global History with its full per-file record and metadata — browsable offline, forever.
A finished, verified copy result — three files with SHA-256 hashes and double check marks, and the Edit as new button.
The receipt: 3 copied · 3 verified, each file with its confirmed SHA-256 hash and ✓✓ — copied and verified.

When something fails

Failures are diagnosed, not generic: source disconnected, destination disconnected, destination full, destination read-only, permission denied. The toast says what happened; the activity log holds the technical detail; the partial run stays browsable so you can see exactly what made it. Re-running the same job is safe — everything already copied is kept and collisions are renamed, never overwritten. To copy only the missing remainder instead, run it as an Advanced Copy with the Skip policy.

Where Simple ends. Multiple destinations with different policies, relay copies, manifests with chain continuation, PDF reports, scheduled ejects — that's Advanced mode. And if you're re-building the same Simple job every morning, that's a sign you want a saved template or a standing watched station.