One Demonstration, Two Complementary Views
Recent embodied-AI data programs increasingly combine egocentric vision, also called first-person vision, with structured hand-motion signals. Public examples such as NVIDIA EgoScale illustrate the broader direction: scalable robot learning benefits from demonstrations that preserve both what the operator saw and how the operator moved.
A head-mounted egocentric camera can capture objects, task context, contact events, and the visual sequence of an operation. Glove-based hand motion capture can record calibrated hand-pose trajectories and fingertip kinematics that may be difficult to recover reliably from video alone. Neither modality is a complete robot-training dataset by itself, but their combination provides stronger supervision for dexterous manipulation.
What Each Modality Contributes
| Data source | Primary value | Typical limitations |
|---|---|---|
| Egocentric vision | Scene context, objects, task progress, visible contacts, and operator viewpoint | Occlusion, motion blur, depth ambiguity, and limited finger-joint observability |
| Instrumented data glove | Timestamped hand pose, fingertip position and rotation, and hand-kinematics trajectories | Does not independently describe objects, scene state, or robot response |
| Robot telemetry | Commands, joint states, end-effector state, errors, and task outcomes | Does not fully explain human intent or visual context |
For learning pipelines, the important unit is therefore the synchronized episode: ego frames, human hand pose, mapped robot commands, observed robot state, task labels, and outcome events aligned on a common timeline.
Where VetraGlove Pro Fits
VetraGlove Pro is a Qnbot instrumented teleoperation data glove available through dexvivid. Its electromagnetic-field sensing system reconstructs 25-DOF hand pose and provides 6-DOF fingertip pose from five VetraSense sensors. The product specification includes up to 180 Hz output without vibration feedback, with SDK support for Windows, macOS, and Linux.
In a synchronized multimodal data-acquisition workflow, these hand-kinematics signals can be recorded alongside egocentric video and then retargeted to the target dexterous hand. The glove does not replace the camera, robot telemetry, force sensing, or task labels. Its role is to add structured human-hand motion to the episode so that later processing does not depend entirely on vision-based hand-pose estimation.
Build the Dataset Around Synchronization
A practical collection pipeline should define its clock, calibration, coordinate frames, and episode boundaries before large-scale recording begins. At minimum, each episode should preserve:
- ego-camera frames and camera timestamps;
- calibrated hand pose and fingertip 6-DOF data;
- the human-to-robot retargeting output;
- robot commands, joint states, and safety events;
- task instructions, object or scene identifiers, and success labels;
- tracking loss, dropped frames, clock offsets, and invalid segments.
Human and robot hands often differ in degrees of freedom, joint limits, and mechanical coupling. Retargeting should therefore be stored as an explicit transformation, not hidden inside the collection software. Keeping both the original hand signal and the mapped robot command makes the dataset easier to audit, replay, and improve.
From Hardware to a Repeatable Data Service
Scaling collection requires more than supplying devices. Operators need a repeatable protocol, tasks need clear start and end conditions, streams need automated validation, and delivered files need a documented schema. A pilot phase should first verify wearability, camera placement, calibration stability, motion mapping, synchronization accuracy, and export quality.
dexvivid provides project-based robot data collection services using partner hardware. Depending on the project scope, the evaluation can cover egocentric vision, glove-based hand motion capture, teleoperation data, task annotations, acquisition workflow design, sample review, file structure, and delivery requirements. Final modalities, scale, site, licensing, and acceptance criteria are confirmed for each project.
Conclusion
Egocentric vision answers “what was happening in the scene,” while glove-based hand motion capture helps answer “how did the hand perform the action.” When these streams are synchronized with robot telemetry and task outcomes, demonstrations become more useful for imitation learning, policy evaluation, and dexterous manipulation research.
For teams planning this type of pipeline, the right first step is a small, measurable pilot built around the target task and robot—not a large recording campaign without a data contract.
NVIDIA EgoScale is referenced as a public industry example. VetraGlove Pro and dexvivid are not represented as components of, or partners in, that project.
Planning an egocentric-vision and glove-based motion-capture project? Share the target task, robot platform, required data streams, collection location, and desired dataset scale with dexvivid.
Discuss a data collection project