Every signal tells part of the story.

Bring video, wearables and sensors together for a clearer view of movement. Fusion unifies those streams in one Motion Session.

Video

Optical video remains the most accessible human-movement input. Fusion treats video as one source among several so later streams can join the same session.

Wearables

Wearable activity and daily context can join a movement session, giving inertial and activity context beside video.

Sensors

IMU, force and pressure samples can be ingested as sensor sources when your capture setup includes them.

One clearer picture

Multiple sources contribute to the same Motion Session. Downstream evaluation happens in MotionBench for robots, or in human reports in StrideIQ.

Signal classes Fusion can represent

Signal classTypical roleHow it enters Arisole
VideoVisible kinematicsStrideIQ capture or a video Motion Source
WearableActivity and session contextWearable source type on a Motion Session
IMUInertial samplesSensor source, CSV or JSON ingest
ForceContact and loadSensor or telemetry observations
PressureDistributed loadSensor observations when a pressure stream exists
TelemetryMachine motionTelemetry source, including ROS2 via ros-bridge

FAQ

What is Arisole Fusion?

Fusion brings cameras, wearables, IMU, force, pressure and telemetry together on a shared Motion Session.

How does Fusion relate to Motion API?

Motion API exposes sessions, sources and observations. Fusion is the product language for combining those sources.

Loading Arisole. If the interactive app does not start, continue with the public links above.