Process a folder of basketball shot videos

Coaches can do this entirely in the browser. There is no script to install or command to type.

1. Open Process a folder from AI Basketball Analysis in desktop Chrome or Edge.
2. Choose a folder of shot clips and allow the browser to read and write it.
3. Confirm the capture FPS. Override it for individual videos if some were filmed in slow motion.
4. Optionally choose the pose model, ball detection accuracy and highlight layout. Press Process videos and keep this tab open.
5. Find the MP4 highlight, PDF report and Markdown text beside each original. Review each row for warnings or failures.

What gets saved

For shot.mp4, the app creates results_shot.mp4, results_shot.pdf and results_shot.md. A results_shot.json receipt records the settings, actual frame rates, analyzed range and output sizes. The MP4 is a metric highlight reel, with 30 FPS output.

Originals are not changed. Existing result files are skipped, including incomplete sets. Move old or partial results before retrying. Videos with the same base name, such as shot.mp4 and shot.mov, must be renamed first. Files beginning results_ or reslts_ are excluded. Subfolders are not processed.

Recording settings that matter

• Camera: film from the side, or up to 45 degrees off the side, with the full body and the ball in frame, in bright light from a stable camera.
• One shot per clip works best: the whole clip is analyzed, as in Basic mode. Trim each clip from just before the catch or final dribble to a few frames after the ball leaves; a clip with several shots reports each detected shot. A clip with no detected shot fails with a message and the queue continues.
• Capture FPS: Auto reads the encoded file rate. Slow motion filmed at 120 FPS may be saved at 30 FPS; enter 120 in that case. 60 FPS or higher is recommended. Auto fails if the file rate cannot be read, so you can choose a rate explicitly.
• Models: Thunder pose and the fastest ball detector are the app’s defaults. Larger YOLO26 models can track better and take longer.

Local processing and recovery

Video analysis and export happen in your browser. Static app code and model files may download from the internet. Folder permissions are granted by you in the browser, and you may need to grant them again after reopening the page.

One video runs at a time. A failure does not stop the rest. Stop batch cancels the active analysis/export; a save already in progress finishes before the queue stops. Closing the browser can leave partial results. Move these before retrying. Avoid concurrent programs writing to the same folder.

If the folder picker is unavailable, use a supported desktop browser such as Chrome or Edge, or return to the single-video app. MP4 export requires H.264 WebCodecs support; an unsupported encoder produces an error. Results are the same estimates and coaching guidance offered by the app’s individual-video workflow.

const api = window.apoptAutomation;
api.capabilities();   // app "hoops", options, defaults, outputs
const id = api.start({
  captureFps: 120, model: "movenet_thunder", ballModelSize: "n"
});
api.getJob(id);       // state: running → succeeded / failed / cancelled
// After state === "succeeded":
await api.markdown(id);   // the text results
api.download(id, "mp4");  // also "pdf" and "md"
api.cancel(id);           // stops a running job