Process a folder of dribbling videos
Coaches can do this entirely in the browser. There is no script to install or command to type.
- Open Process a folder from Basketball Dribbling Analysis in desktop Chrome or Edge.
- Choose a folder of dribbling clips and allow the browser to read and write it.
- Confirm the capture FPS. Override it for individual videos if some were filmed in slow motion.
- Optionally choose the pose model, ball detection accuracy and highlight layout. Press Process videos and keep this tab open.
- Find the MP4 highlight, PDF report and Markdown text beside each original. Review each row for warnings or failures.
What gets saved
For dribble.mp4, the app creates results_dribble.mp4, results_dribble.pdf and results_dribble.md. A results_dribble.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 dribble.mp4 and dribble.mov, must be renamed first. Files beginning results_ or reslts_ are excluded. Subfolders are not processed.
Recording settings that matter
- Camera: keep the athlete’s full body and the ball in frame for several dribbles, in bright light from a stable camera.
- Whole clip: every frame of the clip is analyzed, as in the app. A clip with no complete dribble 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, so the dribble rate and pound speed come out in real time. 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.
For AI agents and developers: browser interface
Everything runs in the browser at https://apopt.com/dribble/automation.html. There is nothing to download or install. An AI agent or script that controls a browser (for example a browser-automation tool) can use the page’s versioned interface, window.apoptAutomation, instead of the folder picker.
- Open
https://apopt.com/dribble/automation.htmland wait untilwindow.apoptAutomation.version === 1. - Put one local video on the file input
#automation-video; the browser reads it locally. - Start the job, poll until it finishes, then read the Markdown or download the outputs.
const api = window.apoptAutomation;
api.capabilities(); // app "dribble", 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
| Option | Values |
|---|---|
| captureFps | "auto" or the recorded FPS, 1–2000 |
| model | movenet_thunder, blazepose, or a YOLO26 pose size: yolo26n_pose, yolo26s_pose, yolo26m_pose, yolo26l_pose, yolo26x_pose |
| ballModelSize | n, s, m, l or x (ball detection accuracy); default n |
| outputFormat | vertical or person-crop; metricCycleSeconds 2–10 |
There is no camera-view option. One job runs at a time, and only the latest job’s outputs are kept, so save every output before starting another. Unknown options and out-of-range values are rejected before processing. Video stays in the browser; an agent that reads the Markdown receives that derived text.
Example agent request: “Open the dribble automation page, analyze dribble.mp4 at 120 capture FPS, save the three outputs and read the Markdown.”