Process a folder of running videos

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

Open Process a folder from Form Analysis in desktop Chrome or Edge.
Choose a folder and allow the browser to read and write it.
Confirm side (sagittal) or back (posterior), capture FPS, height, surface and run type. Override view/FPS for individual videos if needed.
Choose the middle 12 seconds or the entire video. 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 runner.mp4, the app creates results_runner.mp4, results_runner.pdf and results_runner.md. A results_runner.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 runner.mp4 and runner.mov, must be renamed first. Files beginning results_ or reslts_ are excluded. Subfolders are not processed.

Recording settings that matter

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. Auto fails if the file rate cannot be read, so you can choose a rate explicitly.
Height: 1.75 m is a starting estimate; enter the athlete’s height. Use separate browser batches for different athlete heights.
Treadmill: select the surface and optionally enter speed in meters per second. Leave speed blank if unknown.
Segment: the middle 12 seconds is the default. Full video takes longer. The analysis can trim untrackable edges; the receipt records the actual range.

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

For AI agents and developers: browser interface

Everything runs in the browser at https://apopt.com/form/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/form/automation.html and wait until window.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 "form", views, options, defaults, outputs
const id = api.start({
  view: "sagittal", captureFps: 120, heightMeters: 1.82,
  surface: "treadmill", treadmillSpeedMps: 3.4
});
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
view	sagittal (side) or posterior (back)
captureFps	"auto" or the recorded FPS, 1–2000
heightMeters	0.5–2.75; default 1.75
surface	ground or treadmill; treadmillSpeedMps null or 0.1–20
discipline	distance or sprint
range	center12 (middle 12 seconds) or full
model	movenet_thunder or blazepose
outputFormat	vertical or person-crop; metricCycleSeconds 2–10

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 Form automation page, analyze runner.mp4 as sagittal at 120 capture FPS with height 1.82 meters, save the three outputs and read the Markdown.”