Complete Kaish User Manual

Choose the right Kaish product

Sign in before opening protected work

1. Use the email assigned to the correct Kaish workspace.
2. Complete email verification or password recovery when requested.
3. Choose the intended workspace if the account belongs to more than one.
4. Confirm the identity, workspace role, and expected product access.
5. Confirm that the product opens before game day.

Sign in before using protected project, capture, review, presentation, report, save, or export commands. Signing out should not remove local documents; contact support if account access or a protected command behaves unexpectedly.

Main Kaish and Scout currently use separate login and access-control paths, and Hockey intentionally uses its own sign-in and data scope. The same email does not prove linked access. When a Team or Elite plan includes Scout, Kaish support activates the separate Scout team workspace during onboarding; confirm that activation before game day.

Install Kaish Capture or Kaish Analyst

1. Download the current public DMG from kaish.app.
2. Open the DMG and drag the app into Applications.
3. Launch the copy in Applications, not the copy mounted inside the DMG.
4. Allow Camera, Microphone, Local Network, and file-folder permissions only when the workflow needs them.
5. Sign in and confirm the correct product access.

The public installer uses the product name. If support asks for release details, use the information shown inside the installed app. Install a newer public DMG over the prior Applications copy when directed.

Record a live session

1. Open Live Capture.
2. Choose New Session or Capture → New Capture Session….
3. Enter Session Name and optional Opponent / Event, then choose Sport Profile, Quality, and a save folder.
4. Choose the video and audio sources in Setup.
5. Wait for Ready to Record.
6. Press Record, code moments in the Code Window, then press Stop.
7. Wait for finalization before moving, combining, or sending the session.

The current Capture workflow can save a portable .kaishcode package with media. Legacy or reference-style .kaishcode documents may retain external paths instead. Starting recording again creates another segment inside the session; stopped time is not included.

Choose exactly where Code Window tags go

1. Open the current Code Window or a saved .kaishcodewindow from Finder or the app menu.
2. Open the intended Live Capture or Review destination.
3. In Analyst, use the Code Window Target selector to choose the exact named open destination. If no destination should receive tags, choose Display Only.
4. Confirm the selected destination is ready before coding.
5. Use instant buttons for a point event, or manual buttons for an event with a start and end.
6. Set lead and lag only when the code needs pre-roll or post-roll.
7. Add notes, labels, states, and actions where the layout requires them.

An independent Analyst Code Window does not route tags solely from window focus. Closing its selected destination returns it to Display Only. Recheck the target whenever more than one Review or Live window is open.

Review live action without changing the main recording

Turn on Bench DVR Stream before a Blackmagic recording. Kaish creates short finalized DVR chunks alongside the protected main recording. The first ready media normally appears after the first chunk finalizes.

1. On Mac, choose Review DVR or Open DVR Review.
2. Use Back 15s, Play/Pause, Forward 15s, scrub within ready media, or select a finalized tag.
3. Choose Return to Live when the review is finished.
4. On an iPad with Kaish App, open Bench DVR, choose the Mac on the same network, and enter the current six-digit code shown by the Mac.
5. After pairing, tap a live tag to replay it or use the transport controls.

The main preview remains live while the separate DVR player reviews finalized media. Pairing may need to be repeated after the Mac DVR server restarts.

Review recorded video and choose the correct handoff

1. Open Review Video.
2. Add one video or multiple ordered segment videos, or open an existing .kaishcode.
3. Choose Current Segment or Full Game, then code or review the timeline.
4. Select timeline rows, select individual clips, or leave the full set available.
5. Open Send to Analyst and choose Selected Rows…, Selected Clips…, or Complete Timeline….
6. Choose a destination for the portable .kaishcode; Capture copies the available source video required by that scoped handoff.
7. Open the resulting package in Analyst and verify segment media, continuous timing, notes, labels, and representative clips before removing the Capture source.

Capture Share File JSON is different: use it to import Capture markers and video references into Kaish App. Use the scoped portable .kaishcode actions for Analyst. Opening a saved .kaishcode restores its Review rows and available package media; relink missing external media and save again.

Combine any compatible .kaishcode sessions

1. Choose File → Combine .kaishcode Files….
2. Add two or more valid files. There is no two-file maximum.
3. Arrange the sessions in the intended game order.
4. Enter a title and choose a new destination.
5. Choose Combine and Save.
6. Open the combined package and verify segment order, tags, and media.

The files do not need to come from Capture. The combined output is a new portable package; the originals remain unchanged. Missing source media is reported instead of silently discarded.

Use Project Browser as a home, not a required foreground window

Use Project Browser to create, open, save, and recover projects. Open it once, then minimize or leave it behind specialist windows. Timeline, Presentation Builder, Code Window, Tag Matrix, Clips, Reports, Media Manager, Live Capture, and Export Center open as independent windows.

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

Keep different .kaishcode files in separate windows and use the Window menu to focus an open document without creating a duplicate.

Create, attach, import, relink, and play Review work

1. To begin from one MOV or MP4, choose New Timeline… in Review or File → New Review Timeline from Video…. Name the new .kaishcode; Analyst copies the video into the portable package before opening it.
2. To extend the active timeline, choose Add Video… and select the next MOV or MP4 segment.
3. After checking media order and duration, choose Import XML / Tags… for supported Review data.
4. If the active segment moved or is wrong, choose Relink / Resync Video…, select the correct source, verify timing, and save.
5. Click a row or lane to select it. Double-click a row or clip to open its chronological row playlist.
6. Use Review Selection to play selected clips chronologically.
7. Choose Full Video when you need continuous source playback instead of bounded clips.

The four Review Timeline actions are also available from the File menu while Project Browser is minimized. New Timeline is save-first: canceling or a failed package write leaves the current Review and source movie unchanged. Source timing remains the truth; notes, labels, and displayed timing can be edited without changing the original media.

Find clips across open files or an entire folder

1. Choose Workspace → Find or press Command-F.
2. Search title, code, label, note, or filename.
3. Choose Open Files or Choose Folder….
4. Enable Include subfolders when needed.
5. Open the source result, or select the matching playable clips.
6. Focus the intended presentation, then choose Add Clip(s) to Presentation.

Find reads supported Kaish document metadata without loading every full video. It does not search video pixels, OCR, or speech. Open the source result and confirm its media is available before adding clips to a presentation.

Choose reference or standalone on purpose

1. Open or focus the Presentation Builder you want to receive clips.
2. Select timeline rows, library clips, or Find results.
3. Choose Add to Presentation and verify the destination name.
4. Reorder, trim, annotate, and add coach drawings.
5. Use Save Presentation As → Standalone (Portable)… to convert a reference deck.
6. After saving, move a copy to a test folder and verify every range and total package size.

If a standalone save cannot copy a selected range, keep the original unchanged and choose a different destination or resolve the source-media issue before trying again.

Export the format the receiver expects

Choose a destination through the macOS save panel so the app receives permission to write there. Export and open a short sample in the receiving application before a full job.

Move from game setup to coaching review

1. Sign in and choose the correct Team Space.
2. Create a game with the opponent and sport; add date, location, home/away, season, game type, and segments as needed.
3. Prepare the roster, lineup, groups, lines, or units.
4. Use Live Tag during the game.
5. Open Review and attach the full game or its period files.
6. Use Set Sync for tags created on the iPad. Capture-imported tags preserve Capture timing.
7. Filter the timeline, play clips, add notes, and create coach clips or presentations.
8. Publish only to the intended audience.

With eligible Elite or Team access, Bench DVR is available when Kaish App can see a compatible Kaish Capture or Analyst Blackmagic DVR server on the same network.

Use local files or a connected Dropbox library

Local drag-and-drop remains the fastest path when a .kaishcode or presentation package is already on the computer. A connected Dropbox workspace adds a browsable library for games and presentations.

1. Sign in and choose the correct workspace.
2. Connect Dropbox in the workspace settings if it is not already connected.
3. In Review or Presentations, choose the Dropbox library.
4. Select the complete Kaish package—not an individual raw video segment.
5. Wait for the document, sequence, tags/presentation rows, and available authorized media.
6. Open an early and late item to confirm the correct sources are available.

A raw video by itself opens as video only; it cannot recreate tags or a presentation that were never included in a Kaish document. Dropbox authorization can expire, so the browser may ask you to reconnect a package or source media.

Research players inside the assigned scope

1. Sign in through Scout and verify its personal, team, or organization workspace, sport, team, season, and role.
2. Search existing players before creating a new or unrostered prospect.
3. Write notes, structured evaluations, and reports against the correct player.
4. Use watchlists and tracking statuses to organize follow-up.
5. For permitted team roles, verify roster, lineup, game, and Game Prep context before sharing.

Individual Scout, Single-Team, and Organization access have different boundaries. Main Kaish access does not automatically provide Scout access. When Team or Elite includes Scout, Kaish support separately activates the team workspace during onboarding. Use the dedicated Scout manual and confirm the Scout plan and signed-in role before using share, export, or cross-team permissions.

Manage workspace access with customer-facing controls

1. Sign in to your own owner or admin account and choose the intended workspace.
2. Confirm the current owner before changing member access.
3. Invite the exact email each member will use and assign the least-privileged role that supports their job.
4. Confirm any required product seat, sport, team, and season scope.
5. Ask the member to sign in to their own account and test the expected workflow.
6. Transfer ownership and preserve team work before removing a departing owner.
7. Contact Kaish Support if an expected account or workspace control is unavailable.

Never ask a member for a password, verification code, recovery link, or access token.

Verify the account, team, and season scope

Kaish Hockey currently uses a separate sign-in and data boundary. Confirm the identity, access dates, organization, team, role, current season, and any approved historical seasons. Never expose prior league data by reassigning ownership or assuming Kaish App access applies.

Keep an independent known-good copy

• Keep active capture packages and recovery sidecars together until finalization and playback checks pass.
• Use stable paths for reference presentations and libraries.
• Move portable packages to another folder/device and play representative items before deleting sources.
• Use Browser Backup before clearing site data, changing browsers, or moving computers.
• Verify Dropbox/package contents and cross-browser reopen behavior before treating cloud storage as the only copy.
• Archive old sessions only after confirming destination, file count, size, and playback.

Share with players using an explicit audience

Owners and admins can invite player accounts, link them to roster players, choose the whole team or selected groups and individuals, set an expiration, and review viewing activity. Kaish App’s whole-team shortcut always requires confirmation.

Know what each Kaish file contains

Finder displays dedicated Kaish document icons for the supported document types. If Finder still shows a generic icon immediately after installing a new app, relaunch Finder or sign out and back in so macOS refreshes document associations.

Start with the failure boundary

Verify before the venue

1. Install and open the current public release for each product you intend to use.
2. Sign in and confirm the correct workspace and product access.
3. Connect the capture device, power, source cable, and external storage.
4. Confirm live video, audio, frame rate, destination, free space, and a short test recording.
5. Hit several tags with the intended lead and lag; confirm preview remains continuous.
6. If using DVR, wait for a ready chunk and test both Mac and iPad playback.
7. Stop and finalize the test, open its .kaishcode, play a clip, and send one clip to a presentation.
8. Keep a backup cable and a fallback local recording plan.

Open the product in front of you

Send enough detail to reproduce the issue

Include the product, exact app version and build, macOS or iPadOS version, capture source, video format, storage destination, file type, project name, exact error text, and the last action that worked.