Help & Documentation

Offline-first guidance for safe gear lists.

Advanced Features

Features that pay off once real projects pile up

A tour of four features that earn their place on day five, not day one: the Camera Package with its auto-generated Connection Diagram, Device Library favorites, project versioning with revert, and the Auto Gear rules engine. Each section links to its dedicated topic for deeper detail.

Camera Package & Connection Diagram

The Camera Package tab in a project workspace lets you pick a body, monitor, wireless video, battery, and FIZ system. From those selections it generates an interactive Connection Diagram showing power, video, and data links between the devices.

  • Pick a camera body first — most of the diagram anchors to it.
  • Add monitor, wireless video, battery, and FIZ as needed. Each field is a searchable picker: click it to list every device of that kind, or type to narrow it down.
  • Switch to the Connection Diagram view in the same tab — devices appear as tiles, connections as colored lines.
  • Drag tiles to rearrange the layout; positions persist on the project.
  • Double-click a tile to open a popover with voltage, power draw, and other specs.
  • Line color encodes connection type (power / video / data).
Tips
  • An empty diagram usually means no camera body is picked yet.
  • Search the pickers by any part of the name, in any order: "mini" finds the ALEXA Mini LF, and a catalogue alias finds its device too. A small typo still finds it.
  • Popover details come straight from the device catalog — wrong specs are fixed in the Device Library, not in the diagram.
See also

Favorites in Device Library

Star items so they surface at the top of every dropdown and category list. Used heavily on prep days when speed matters more than browsing.

  • Click the star icon on any item in the Device Library to favorite it.
  • Favorited items appear in a ★ Favorites group at the top of category dropdowns.
  • Favorites are a single global list, shared across all projects.
  • Unstar from any dropdown to demote an item.
Tips
  • Favorite the camera bodies, primary lens sets, and media formats you actually use — that's where the time savings come from.
  • If a favorited item disappears, check whether it was deleted or hidden in the catalog.
See also

Project Version Numbers & Revert

Every project carries a numeric version (v1, v2, v3 …). The version badge in the workspace header opens the history and the bump / revert flows. This is NOT git-style branching — it's a single linear history per project.

  • The 'v{N} edit' badge lives in the project header.
  • Single click: a dropdown lists the current version plus historical versions with timestamps.
  • Click 'edit' on the badge: a modal sets the Next version number and optionally updates the baseline.
  • Setting a number below the current version triggers a confirm dialog (decreases are destructive in spirit).
  • Revert is a two-step confirmation flow from the dropdown — it replaces the current project state.
  • Edit history is logged automatically — see it via the Edit History panel.
Tips
  • Bump the version before sending a PDF to a client so the recipient and you both have a clear reference.
  • 'Update baseline' resets the comparison anchor — useful when subsequent diffs should start from the new version.
  • Revert is destructive — two confirms exist on purpose. Read them.
Common Pitfalls
  • Treating versions like git branches — they're linear, not a tree.
  • Reverting and being surprised that the current state is gone — that's exactly what revert means.
  • Forgetting to bump when sending an external PDF — the recipient sees 'v3' on a doc that no longer reflects v3.
See also

Auto Gear Rules Engine

Auto Gear watches the project state (cameras, crew, frame rates, properties) and adds or removes gear automatically when triggers match. Rules live on the project's Auto Gear tab, alongside shared Presets and Factory defaults.

  • Project workspace → Auto Gear tab.
  • Each rule has triggers (conditions), an action (Add or Remove gear), and the affected devices.
  • Combine multiple triggers with AND / OR combinators.
  • Smart computed actions (the ⚡ items) match chargers, cables, power plates, and monitors dynamically against the device catalog.
  • Save favorite rule sets as Presets and load them on other projects.
  • Factory Rules cover common cases (chargers for batteries, cables for cameras) — disable or override per project.
Tips
  • Start with the Factory Rule Catalog enabled before writing your own — most setups only need a few overrides.
  • Smart computed actions read from the live catalog; adding a new battery to the Device Library can change what Auto Gear adds.
  • Use the Preset Manager Modal to share rule sets between projects — JSON export is also supported there.
Common Pitfalls
  • Writing very broad triggers and getting unexpected gear additions — start narrow and widen as needed.
  • Forgetting Auto Gear runs against the catalog — if a smart action's match list looks wrong, the Device Library is the source of truth.
See also

For depth on any of these, jump to the dedicated topic: Device Library, Auto Gear, Projects. This page is the high-leverage tour, not the reference.

Was this helpful?

Related Topics

See also