Full Manual

1. What Capture Pro is for

Capture Pro is a Mac workflow for recording, coding, reviewing, organizing, presenting, and exporting sports video clips. Most work begins in a local `.kaishcapturepro` package, then moves through capture or review, clip organization, presentations, and exports.

2. Package and app-level data

A package stores package-scoped Review Games, Package Clips, Package Presentations, package media references, the package Tag Matrix copy, and capture session data. App-level data includes Clip Hub libraries, Global Presentations, Global Tag Matrix entries, and Coach Clips / Quick Flags.

3. First setup

1. Create or open a `.kaishcapturepro` package.
2. Choose whether you are recording live, coding existing media, or reviewing imported coding data.
3. Confirm media paths before meetings or exports.
4. Pick the right coding surface: Coach Clips / Quick Flags for fast marks, or Tag Matrix / Code Window for detailed event coding.

4. Live Capture and Live DVR

Live Capture records from supported hardware such as Blackmagic devices. Install Blackmagic Desktop Video, connect the device and source, close other apps using the device, then confirm preview and signal status before recording. Live DVR uses finalized DVR media for review and does not replace the main recording file.

5. Review Coding

Review Coding can start from attached media, an opened `.kaishcode` project, imported Review XML, or a finalized capture sent from Live Capture. `.kaishcode` stores Review rows, tags, timing, labels, notes, and references, but it does not include the video file.

6. Timing and playback

Review supports clip-relative playback and Full Video mode. Imported XML preserves raw timing. Fullscreen Review drawing is runtime-only and is not exported unless a future export explicitly adds that support.

7. Labels, notes, and coding

Notes and labels help carry teaching context through review and clip workflows. Label metadata can be stored inside note text using `Labels:` conventions when imported or exported through supported coding workflows.

8. Package Clips and Clip Hub

Package Clips are saved inside the active package. Clip Hub is app-level and can organize reusable libraries across work. Review clips do not auto-sync into Package Clips or Clip Hub; send or add clips intentionally when you want them available there.

9. Presentations and coach drawing

Package Presentations live inside the package. Global Presentations are app-level. Presentation timing is separate from source timing, and coach drawing is used during presentation/review rather than being burned into exported video by default.

10. Reports and Output Windows

Summary Reports and Output Windows are calculated from package clips and active presentation rows. Player and on-ice reporting depends on clean player metadata. CSV export is available for supported report workflows.

11. Exporting and file types

Capture Pro uses several file types. `.kaishcapturepro` packages hold the main local project. `.kaishcode` stores editable Review coding without video. `.kaishcliphub`, `.kaishcliphub.json`, and `.kaishclippack` are clip-library or clip-pack metadata formats. Presentation Share Files, XML, and CSV are used for supported sharing and compatibility workflows.

12. Media included vs metadata only

Some workflows include media for a self-contained handoff. Others are metadata-only and require the receiver to have or relink the original media. Confirm the receiving workflow before sending game-day or meeting material.

13. Settings and shortcuts

Settings include capture hardware, shortcuts, Coach Clips / Quick Flags, app defaults, file type maintenance, and diagnostics. Code Window shortcuts depend on focus and armed state. Display Only buttons never write tags.

14. Troubleshooting checklist

1. If Blackmagic hardware is missing, check Desktop Video, cabling, macOS permissions, and other apps using the device.
2. If video is missing, relink moved media before review, presentation, or export.
3. If Live DVR is pending, wait for finalized media before using the DVR review path.
4. If imports are slow, test with a smaller sample before a full event file.
5. If shortcuts are not firing, confirm the intended window has focus and typing fields are not active.

15. Best practices

1. Test hardware preview and audio/video signal before game day.
2. Save packages before major edits.
3. Keep source media in stable folders.
4. Verify imported timing against sample clips.
5. Export a small sample before sending a complete handoff.