Analyst Manual

1. Prepare the Mac and working files

1. Install the exact Analyst release you intend to use and open the Applications copy.
2. Keep original videos and Kaish documents in stable folders with enough free space.
3. Sign in with an identity intended to have Analyst access, then verify the project and document names before editing.
4. For live work, grant the required Camera, Microphone, Local Network, and folder permissions.
5. For Blackmagic, install Desktop Video, match the source format, close competing capture apps, and test the device.
6. For OBS, create the scene and start OBS Virtual Camera before selecting it in Analyst.

Never move an active capture folder, unplug its destination drive, or delete source media while recording or finalizing.

2. Verify account access without risking local work

Analyst requires a valid signed-in entitlement before protected project, capture, edit, save, import, Find, Combine, presentation, report, and export commands run. Signing out should not delete local documents.

1. Launch Analyst while online and complete sign-in.
2. Confirm the account and access result in the Project Browser.
3. Open a disposable test project and verify an allowed command.
4. Sign out and verify protected commands remain blocked while the local file still exists.
5. Sign back in and reopen the test file before using customer work.

If a protected workflow runs while signed out, stop and contact support with the command and app version.

3. Use Project Browser once, then work from windows and menus

1. Create a project or open the intended Analyst project/package.
2. Verify the project name, package name, storage location, and media summary.
3. Open only the professional windows needed for the task.
4. Minimize or leave Project Browser behind the work.
5. Use the macOS menu bar, command palette, Window menu, or shortcuts to reopen/focus tools.

• Command-0: Project Browser.
• Command-1 through Command-9: professional tool windows.
• Command-K: command palette.
• Command-F: Find in Analyst.
• Option-Command-W: close specialist windows.

Menu commands remain available while Project Browser is minimized. Use Command-0 when you need to bring it forward again.

4. Keep different jobs in independent windows

Review Workspace, Code Window, Tag Matrix Editor, Live Capture, DVR Review, Media Manager, Reports, Clips, Presentation Builder, and Export Center are intended to open independently.

1. Open two different .kaishcode files and confirm each has its own review timeline window.
2. Open more than two documents when the task requires it; no artificial two-document limit is intended.
3. Open different presentations at the same time.
4. Use the Window menu to switch among them.
5. Open the same document again and verify Analyst focuses the existing window instead of duplicating it.

Each window must keep its own document context. Before editing, adding clips, or exporting, read the document name shown in that window.

5. Create, open, and verify a timeline

Start a standalone timeline from one video

1. In Review Workspace, choose New Timeline…, or choose File → New Review Timeline from Video….
2. Select one MOV or MP4 source.
3. Name and save the new .kaishcode.
4. Wait for Analyst to copy the selected movie into the portable package and open it for coding.
5. Create a disposable tag, save, close, reopen, and verify both media and tag.

New Timeline is save-first and transactional: the package is built and checked before the current Review window is replaced. Canceling or a failed write leaves the current Review and source movie unchanged.

Open or extend existing Review work

1. Choose File → Open Timeline…, open a Kaish document from Finder, or use the Project Browser.
2. If the package includes portable media, let Analyst resolve it from the package.
3. Use Add Video… to add another MOV or MP4 segment to the active timeline.
4. Use Import XML / Tags… only after source order and media duration are correct.
5. Use Relink / Resync Video… to choose the media again for the active segment when a file moved or the wrong source is attached.
6. Confirm total duration, media part order, row count, and the first/last event.
7. Play an early, middle, and late event, then save the active Review project.

The four Review Timeline actions are also available from the File menu while Project Browser is minimized. A current .kaishcode may contain media when created as a portable package. Older or reference-style timelines may contain metadata and paths only.

6. Play one clip, a row, or a selected set

1. Single-click an event to inspect its source and displayed timing.
2. Double-click a row or clip to open that row’s chronological playlist.
3. Select several events and use Review Selection for the selected set.
4. Use row/lane and visibility controls to define what belongs in the playback list.
5. Switch to full-video playback only when you need unbounded source review.
6. Verify lead/lag and any edited displayed timing without changing protected source timing.

Play a representative row and a cross-segment selection before a meeting. If a row stops after one event or plays the full source segment, preserve the file and report the selection, grouping, source-part boundary, and timing shown.

7. Find matching metadata across files

Find searches supported Analyst metadata—not video pixels, speech, or OCR.

1. Choose Workspace → Find or press Command-F.
2. Select Open Files to inspect currently loaded documents, or choose a folder.
3. Enable Include Subfolders only when the wider scan is intended.
4. Enter a player, code/tag, label, note, source filename, presentation name, or clip/bin name.
5. Review results grouped by source document.
6. Open/focus a result and confirm the correct row or clip is selected.
7. To collect clips, focus the intended presentation first, then add selected playable results.

Folder scans are read-only and do not copy large media merely to index it. Open a result in its source Review Workspace and confirm its media before adding the clip to a presentation.

8. Keep clip references and portable media distinct

• Project/package clips: stay with the active Analyst project.
• Reference clip library: keeps links to source video and remains small.
• Portable clip library: copies the required selected clip media when validation succeeds.
• Clip pack: moves a selected set with the media required by that export.

1. Open or create the intended library.
2. Choose precise timeline events or Find results.
3. Add only the selected clips.
4. Reopen and play early/middle/late items.
5. For portable output, move a copy to another folder and verify it without relying on the original path.

9. Build, focus, and convert presentations

1. Create or open the presentation that should receive clips.
2. Click its window so it is the active/focused presentation.
3. Return to a timeline, library, or Find results and add the selected clips.
4. Verify the destination presentation name and new rows.
5. Reorder, trim displayed ranges, add notes/slides/drawings, and rehearse.
6. Save and reopen before a meeting.

Save Presentation As → Standalone (Portable)… creates a .kaishdeckpack with selected bounded clips and required assets. If a range cannot be copied, keep the original presentation unchanged and resolve the source-media or destination issue before trying again.

Focus the intended reference or standalone presentation before adding clips. After adding later clips to an existing standalone, move a copy and play representative ranges before sharing it.

10. Route an independent Code Window safely

1. Open the intended saved .kaishcodewindow from Finder or the Analyst File menu, or open a Code Window from the workspace.
2. Open the Review or Live Capture destination that should receive new tags.
3. Use the Code Window Target selector to choose the exact named destination, not merely the last window that had focus.
4. Confirm the status says the destination is ready before pressing a code button.
5. Choose Display Only when no open destination should receive tags.
6. Verify button labels, colors, hotkeys, instant/manual behavior, lead, lag, labels, and actions.
7. Run a disposable sample, then save the code-window document after intentional changes.

Closing the selected destination returns the Code Window to Display Only. Hotkeys should not fire while typing in a text field. Recheck the target when several Review or Live windows are open.

11. Keep live preview separate from DVR playback

1. Create the session and choose video, audio, quality, and destination.
2. Wait for source, format, audio, and storage readiness.
3. Record a one-minute test and hit several tags with realistic lead/lag.
4. Confirm the input preview remains continuous.
5. For direct Blackmagic capture, enable DVR before recording and wait for ready media.
6. Open DVR Review as a separate resizable window so playback does not replace the live input view.
7. Stop and wait for finalization before opening the package in Review.

OBS Virtual Camera, FaceTime, USB/UVC, and Continuity cameras can be capture sources where shown, but the protected DVR path remains Blackmagic-only. iPad Bench DVR is included with eligible Elite and Team access and uses same-network pairing to the Mac. Pairing may need to be repeated after the DVR server restarts, so keep the six-digit pairing code available.

12. Combine compatible Kaish timelines

1. Choose File → Combine .kaishcode Files….
2. Add any number of compatible Kaish timeline files from supported Capture, Analyst, or other Kaish workflows.
3. Arrange periods, halves, or segments in game order.
4. Save a new result without overwriting the sources.
5. Open the combined output and verify duration, segment order, tags, notes, labels, and media.
6. Keep original files until the combined package passes playback checks.

The combine process should not alter capture or coding behavior in the source packages.

13. Build output from verified data

1. Choose the intended timeline/package and report template.
2. Set game, segment, team, player, code, label, or date scope.
3. Check that required player and label metadata exists.
4. Compare a small known sample against timeline events.
5. Only then generate the full summary, CSV, or supported output.

A report cannot reconstruct context that was never coded. If numbers look wrong, inspect the underlying event, player, segment, and filter before changing the report layout.

14. Export a short sample before a full job

Choose the format expected by the receiving application, then create and open a short sample before exporting a complete job.

1. Choose the destination through the macOS save panel so Analyst receives permission.
2. Export one or two items first.
3. Open the output in its destination application.
4. Confirm exact ranges—not full source segments—where the format is clip-based.
5. Keep the Analyst source until the receiver verifies the full export.

15. Use the right document type

Use a Finder folder chosen through Analyst when writing exports or portable documents. If a security-scoped permission error appears, choose a fresh authorized destination instead of retrying an old moved path.

16. Preserve originals while diagnosing

17. Run the Analyst readiness checklist

1. Install and open the current public release.
2. Verify sign-in and the signed-out protected-command gate.
3. Open several .kaishcode files in separate windows.
4. Play one clip, a full row playlist, and a multi-row selection across segment boundaries.
5. Find metadata in open files and a folder with subfolders; open and play results.
6. Add timeline and Find clips to the currently focused reference and standalone presentations.
7. Convert reference to standalone and verify only selected clip ranges after moving the output.
8. Export short MP4, Sportscode, Focus, and data samples and open each in the receiver.
9. Keep Project Browser minimized and verify menu commands remain available.
10. If using capture, confirm continuous preview, finalization, Blackmagic DVR, and iPad pairing with the current Kaish App.

18. Know the current boundaries

• Folder Find searches supported document metadata; it does not interpret video or audio content.
• Reference documents depend on stable source paths until converted to validated portable output.
• Portable package size grows with copied clip media.
• Blackmagic DVR is not provided through OBS or generic camera capture.
• Interchange formats support the Kaish-tested subset; verify them in the exact receiving version.
• Hardware, operating-system permissions, and external storage still require a real-device test.

Open the focused workflow