Process a folder of golf swing 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 Golf Swing Analysis in desktop Chrome or Edge.
2. Choose a folder and allow the browser to read and write it. Each video should hold one swing, filmed from a fixed camera.
3. Confirm face-on or down-the-line, capture FPS and right- or left-handed golfer. Override view/FPS for individual videos if needed.
4. Press Process videos and keep this tab open. The whole clip is analyzed, as in the single-video app.
5. Find the MP4 highlight, PDF report and Markdown text beside each original. Review each row for warnings or failures.

What gets saved

For swing.mp4, the app creates results_swing.mp4, results_swing.pdf and results_swing.md. A results_swing.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 swing.mp4 and swing.mov, must be renamed first. Files beginning results_ or reslts_ are excluded. Subfolders are not processed.

Recording settings that matter

• Camera view: face-on scores all six metrics; down-the-line scores four (head sway and X-Factor need the face-on view). A wrong view gives wrong numbers, so use the per-video override for a mixed folder.
• 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. Backswing and downswing times use this rate. Auto fails if the file rate cannot be read, so you can choose a rate explicitly.
• Handedness: sets the lead and trail sides. Use separate browser batches for right- and left-handed golfers.
• Swing events: address, top and impact are detected automatically. The Markdown lists the frames found. To correct an event by hand, open the clip in the single-video app’s Advanced mode and use the manual phase overrides.
• Pose model: MoveNet Thunder is the default, as in the single-video app. YOLO26s and BlazePose Heavy are slower.

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 individual-video workflow.

const api = window.apoptAutomation;
api.capabilities();   // app "golf", views, options, defaults, outputs
const id = api.start({
  view: "face-on", captureFps: 120, handedness: "left"
});
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