A motion-capture day is expensive. Most prototype questions still need a trail of comparable records: same task, labelled condition, stored observations. Research and footwear teams use StrideIQ for accessible video and Fusion plus Motion API when IMU, force or pressure streams should sit on the same session.
Define the task (for example a 20-metre walk in condition A vs B). Capture video through StrideIQ or attach a video source on a Motion Session. If the protocol includes IMU, force or pressure, ingest those as generic sensor sources — not as a claimed branded insole unless that hardware is actually in the protocol. Compare sessions in analysis review or, for machine or policy tests, in MotionBench.
StrideIQ for human video. Arisole Fusion and Motion API for multimodal sessions. MotionBench only when the entity is a robot or other Physical AI system.
Keep condition labels in session metadata so later analysis is not reconstructing which foam was on which day.
Use video snapshots when the force plate is booked, then add instrumented sessions when they exist.
Attach wearable sources when the study already collects them; do not invent a device integration.
Hand designers structured observations instead of a folder of unnamed MP4s.
No. Labs remain the instrumented standard. Arisole is the structured, repeatable layer around and between lab days.
This site does not claim a shipped insole SKU. Pressure and IMU are described as signal classes on Fusion.
Workspace API keys can read analyses and Motion Sessions through the documented /v1 routes.
Loading Arisole. If the interactive app does not start, continue with the public links above.