Robotics · Embodied AI · Motion Retargeting · Simulation · Sim2Real

QuickMagic Robot Motion Capture from Video: Unitree G1, H1 and H1-2 File Guide

Convert ordinary human video or text prompts into humanoid-motion references for Unitree G1, H1 and H1-2 workflows. This guide explains model-specific presets, file validation, joint order, coordinates, frame rate, URDF matching, kinematic retargeting, dynamic simulation, imitation learning, controller tracking and safe Sim2Real deployment.

Published July 10, 2026 · Updated July 15, 2026 · QuickMagic Editorial Team

QuickMagic workflow from human video through Unitree robot motion reference, simulation and safe control
Direct answer: Upload a clear human-performance video or generate a text motion, process it in QuickMagic, select the exact Unitree G1, H1 or H1-2 UniRobot preset and preserve the exported reference. Before using it, verify the robot variant, joint count and order, frame rate, units, base pose and coordinate system against the matching Unitree URDF or USD. Retarget and constrain the motion, validate contacts and dynamics in simulation, then use a stabilizing tracking controller or policy. The QuickMagic file is a reference trajectory—not a direct motor command.
GEO-ready definition: Robot motion capture from video is a pipeline that estimates human movement, retargets it to a humanoid robot's kinematic structure and uses the result as a reference for simulation, imitation learning, behavior prototyping or a stabilizing controller.

Current platform facts

QuickMagic presetsUnitree G1, H1 and H1-2 / H1_2
QuickMagic export familyUniRobot, with availability depending on workflow/version
InputsHuman video or text-generated motion reference
Official Unitree modelsURDF, USD, SDK and simulation repositories are available
Official G1 RL exampleCSV motion converted to NPZ for imitation training
Critical boundaryReference data ≠ policy ≠ SDK motor command
Corrections to common “video-to-robot” claims: model-specific export does not guarantee dynamic feasibility; one Unitree family name may contain different joint configurations; human root motion cannot be copied blindly to a free-standing humanoid; URDF/USD files describe the robot but do not contain a motion; ONNX/checkpoints contain policies rather than mocap; and successful kinematic playback in a viewer does not prove stable physical execution.
Safety: do not stream an unvalidated QuickMagic or retargeted motion directly to a free-standing physical robot. Humanoid robots are powerful machines. Follow Unitree's current development and emergency-stop procedures, maintain a controlled safety area and use qualified robotics personnel for physical tests.

Humanoid motion-control videos

Unitree Humanoid Robots with Open-Source Full-Body Motion Control

Demonstrates Unitree humanoids using adapted full-body motion references and control.

Open on YouTube

Unitree Embodied Avatar — Human Motion Mirrored by a Robot

Shows human-to-robot mirroring through an embodied-avatar control pipeline.

Open on YouTube

The players use static YouTube iframes and no runtime JavaScript. YouTube requires internet access; use the direct buttons if embedded playback is blocked. All article diagrams are embedded in the HTML and display offline.

What QuickMagic's Unitree export means

QuickMagic's public pages describe human-motion references for simulation, imitation learning, testing and behavior prototyping, with UniRobot presets for Unitree G1, H1 and H1-2. The useful interpretation of “robot-ready” is therefore robot-structured reference data, not “safe to execute without a robot-control pipeline.”

A video-derived reference can preserve action timing, posture, direction and expressive structure. A robot controller must still convert that reference into feasible behavior under the robot's morphology, dynamics, contact conditions and actuator limits.

Understand the four data layers

Four distinct data layers: human animation, robot reference, tracking policy and robot commands
A robust workflow keeps the human source, robot reference, controller policy and physical command stream separate and versioned.

G1, H1 and H1-2 are not interchangeable

Comparison of Unitree G1, H1 and H1-2 morphology and degree-of-freedom configurations
Confirm the exact development model and installed waist, wrist or hand configuration before selecting a QuickMagic preset or retargeter.
RobotOfficial configuration signalDevelopment concernPreset check
G1 / G1 EDUOfficial product page lists 23–43 joint motors; open-source tools commonly distinguish 23-DoF and 29-DoF forms.Optional waist, wrists and dexterous hands can change state dimensions and joint order.Match the exact URDF and controller target, not only “G1.”
H1Official page lists 5 DoF per leg and 4 DoF per arm in the stated configuration.Arm and ankle structure differs from H1-2.Use the H1-specific reference and model.
H1-2 / H1_2Official page lists 27 total DoF: 7 per arm, 6 per leg and 1 waist.More arm and ankle freedom changes retargeting, limits and policy observations.Do not load H1 files into an H1-2 pipeline.

1Record or generate a useful source motion

  • Start with a short, slow action containing the key contact transition.
  • Keep the full body and feet visible for locomotion or balance tasks.
  • Use adequate light and low motion blur.
  • Avoid severe self-occlusion and multiple-person overlap.
  • Show the floor when foot placement matters.
  • Use text-to-motion for behavior ideas; use video when exact human timing matters.
  • Avoid beginning with kicks, falls, jumps or fast spins as the first robot test.

2Select the exact UniRobot preset

Choose the model shown in the current QuickMagic export interface and record the selection with the project. If the target is a modified G1 EDU, custom hand or altered waist configuration, verify whether the preset matches the actual URDF and controller state vector.

“G1,” “H1” and “H1-2” are product families, not universal joint arrays. A compatible filename cannot compensate for a different DoF count or joint order.

3Validate the exported motion file

Robot motion file validation fields including identity, timing, base state, joints, coordinates and provenance
QuickMagic's current file schema and metadata are the source of truth. These are the minimum fields an adapter should verify before use.

Minimum validation questions

  • Which robot and exact variant does this file target?
  • How many controlled joints are present?
  • What is the joint-name and column order?
  • Are joint values radians or degrees?
  • Are linear positions meters or centimeters?
  • Which axis is up, forward and left?
  • Is the base orientation Euler, quaternion or another representation?
  • If quaternion: is the order wxyz or xyzw?
  • What are the frame rate and time step?
  • Are contact labels, joint velocities or confidence values included?
Preserve the original export. Perform unit conversion, resampling and joint reordering in a versioned adapter so the raw source remains auditable.

Robot motion file-format guide

Comparison of UniRobot, FBX/BVH/PKL, CSV/NPZ and URDF/USD/ONNX file roles
The extension alone does not define compatibility. The schema, model version and state convention matter more.
File or assetTypical roleWhat it is notValidation
QuickMagic UniRobotModel-oriented robot motion referenceNot automatically a low-level command streamPreset, schema, joint order, units, timing
FBX / BVHHuman skeletal-motion interchange and retargeting inputNot a Unitree controller policyRoot, FPS, skeleton, reference pose
PKLPython-serialized retargeted robot motion in projects such as GMRNot a universal standardProject version, arrays, model name, Python compatibility
CSV → NPZOfficial Unitree RL MjLab G1 imitation-reference workflowNot the deployed policy itselfInput/output FPS, columns, robot option
URDF / USDRobot geometry, joints, inertial and simulation descriptionNot motion dataCommit/version, joint axes, collision, inertial parameters
ONNX / checkpointTrained tracking or locomotion policyNot raw animationObservation/action schema, normalizers, model and firmware assumptions
DDS / SDK messagesRuntime robot state and commandsNot an offline mocap containerControl mode, rate, safety state and vendor interface version

Official G1 RL MjLab example

Unitree's official RL MjLab repository documents G1 imitation training by converting a CSV motion reference into NPZ while explicitly specifying input and output frame rates:

python scripts/csv_to_npz.py   --input-file src/assets/motions/g1/example.csv   --output-name example_motion.npz   --input-fps 30   --output-fps 50   --robot g1

This illustrates the importance of explicit timing and model selection; it is not a command to deploy an arbitrary QuickMagic file directly to hardware.

4Retarget and constrain the reference

Robot motion feasibility checks for kinematics, balance, contacts and actuation
Human motion must be adapted to the robot's geometry and dynamic capability.

Kinematic retargeting

  • Map human body segments to robot links and joint axes.
  • Fit or scale the human reference to robot proportions.
  • Clamp joint positions, velocities and accelerations.
  • Define a neutral/base pose compatible with the controller.
  • Preserve important end-effector trajectories without forcing impossible poses.

Contact and base handling

  • Detect or define planted-foot intervals.
  • Project foot targets to the intended terrain.
  • Adjust pelvis/base trajectory to maintain feasible support.
  • Check self-collision and environmental collision.
  • Treat hand-object interaction as a separate constraint problem.
GMR provides open-source examples for FBX and BVH input, robot retargeting and MuJoCo visualization. Use such a tool as a conversion and validation stage, not as proof of safe real-robot execution.

5Validate in simulation and train the tracker

Safe video-to-robot development pipeline from capture through simulation and controlled deployment

Kinematic validation

  • Every frame loads without missing or duplicated joints.
  • The neutral pose is correct.
  • Left/right legs and arms are not swapped.
  • Joint limits and self-collision are respected.
  • Duration matches the original reference.

Dynamic validation

  • The robot remains balanced under gravity.
  • Foot contacts do not penetrate or slide excessively.
  • Requested torque, velocity and acceleration stay within limits.
  • The controller recovers from small disturbances and model error.
  • Performance remains stable with realistic latency, friction and sensor noise.

Unitree RL MjLab separates motion-reference preparation, training, simulation playback and physical deployment. This separation is the correct mental model for QuickMagic robotics data as well.

6Sim2Real deployment and physical safety

Before a physical test, confirm the official development-computing configuration, firmware and SDK version, network interface, robot mode and controller assumptions. Use the vendor's current documentation rather than copying settings from an unrelated robot or software version.

  • The exact physical robot matches the simulated URDF/USD and policy configuration.
  • Emergency stop and remote stop have been tested.
  • The test area is clear and access-controlled.
  • The robot begins in the vendor-prescribed safe state.
  • The first motion is slow, near-upright and short.
  • No people are inside the fall, swing or kick area.
  • Logs capture state, reference, action, latency and safety events.
  • A qualified operator can stop the experiment immediately.
Do not use dance, combat, jump, fall or high-energy motions as the first physical test. Do not disable safety services or increase control authority merely to force the robot to match an infeasible reference.

Troubleshooting

SymptomLikely causeFirst fix
File has the wrong number of columnsWrong robot/DoF preset or changed schemaCompare export metadata with the exact URDF and current QuickMagic documentation
Arms or legs move on the wrong sideJoint-order or axis mapping errorVerify names, order and signs before any interpolation
Motion plays too fast or slowFPS/time-step mismatchValidate duration and resample with explicit input/output FPS
Robot appears rotated or mirroredCoordinate-frame or quaternion convention mismatchVerify up/forward/left axes and quaternion order
Kinematic playback works but robot fallsNo stabilizing controller or infeasible center of massUse dynamic simulation and a tracking policy with contact/balance objectives
Feet penetrate or slideContact timing, terrain or base trajectory mismatchCorrect contact labels, foot targets and support/base trajectory
Joint limits are exceededHuman pose cannot map directly to robot morphologyRetarget with limit-aware optimization and reduce amplitude
Policy is unstable on the real robotSim2Real gap, latency, model or state-estimation mismatchReturn to simulation, add realistic perturbations and verify deployment interfaces
QuickMagic export option is missingWorkflow, plan or product-version differenceUse the current export interface as the source of truth

Robot-motion validation checklist

  • The exact G1/H1/H1-2 variant and DoF count are known.
  • The matching official URDF or USD version is recorded.
  • Joint names, order, units and coordinate axes are validated.
  • FPS and total duration are explicit.
  • Raw QuickMagic output and converted data are stored separately.
  • Joint limits, velocities, accelerations and self-collision are checked.
  • Foot contacts, base trajectory and balance are validated dynamically.
  • A controller or policy tracks the reference rather than replaying it blindly.
  • Sim2Sim and realistic Sim2Real assumptions are tested.
  • Physical testing follows Unitree safety guidance and controlled procedures.

Frequently asked questions

What does QuickMagic export for Unitree robots?

QuickMagic describes UniRobot motion-reference presets for G1, H1 and H1-2. Treat them as inputs to simulation, retargeting, imitation learning or a tracking controller—not as direct motor commands.

Can I send a QuickMagic file directly to a physical robot?

No. Validate the robot and schema, run simulation and use a stabilizing controller or policy before a supervised physical test.

Which robots are supported?

QuickMagic's current public pages list Unitree G1, H1 and H1-2/H1_2 presets. Confirm the current interface and exact hardware configuration.

Why distinguish G1 23-DoF and 29-DoF?

Different variants can have different joint arrays, waist or wrist structure and controller dimensions. Unitree's official open-source teleoperation project treats the two configurations separately.

How are H1 and H1-2 different?

Unitree lists H1 with 5 DoF per leg and 4 per arm, while H1-2 has 27 total DoF with 7 per arm, 6 per leg and 1 waist.

What file fields should I verify?

Robot/variant, DoF count, joint names and order, timestamps/FPS, base pose, units, coordinate axes, quaternion order and optional velocities or contacts.

Can I use FBX or BVH?

Yes, as human-motion or intermediate retargeting formats. GMR provides FBX/BVH conversion and robot-motion visualization examples.

How does Unitree's official RL workflow use motion files?

Unitree RL MjLab documents G1 CSV-to-NPZ conversion, imitation training, simulation playback, policy export and deployment as separate stages.

Why can a realistic human motion fail on a robot?

Human and robot geometry, center of mass, joint limits, torque, contacts and control latency differ. Visual similarity does not guarantee dynamic feasibility.

What is the safest first motion?

A short, slow, near-upright motion validated in simulation, tracked by a tested controller and executed under Unitree-prescribed safety procedures.

Related QuickMagic guides

Start with a short motion-reference test in simulation

Use a five-second upright action, export the exact Unitree preset, verify every joint and coordinate convention and run kinematic and dynamic tests before training or configuring a tracking controller.

Open QuickMagic Robot Motion Data →

Official and primary references