Dreaming the Sound of Contact

Leveraging video and audio generation for zero-shot force-aware manipulation and data generation.

Watch arXivComing Soon CodeComing Soon DatasetComing Soon
Concept overview: three stacked panels showing generated video and audio, a robot contact point with force-direction and audio-magnitude annotations, and real-world execution examples โ€” whiteboard wiping, carrot peeling, lamp button pressing, and box stacking.

Experiments

Video for motion, audio for force.

Pick a task and a run. Each row plays the generated reference video + audio, our force-aware execution on a Franka arm that tracks the audio-derived force profile, and a kinematic-only baseline for comparison. Turn the sound on โ€” the contact audio is the force signal.

6 / 6 ours 0 / 6 base
Run
Generated Video + Audio from Seedance 2.0
Baseline ยท kinematic Same trajectory, no force regulation
2ร—
Ours ยท force-aware Franka arm tracks the audio-derived force profile
2ร—

Abstract

Audio is the force signal video can't see.

Recent advances in video generation enable learning robot manipulation trajectories from generated videos. However, these approaches produce purely kinematic trajectories that lack force information, leading to failure in contact-rich tasks where appropriate contact forces are essential for success. Generated audio carries a complementary and underexplored signal: contact sounds encode force dynamics that video alone cannot capture.

We present a pipeline that jointly leverages generated video and audio to recover both motion trajectories and contact force profiles from a single task description. We execute these force-aware trajectories on a Franka Panda robot using a closed-loop force regulator that tracks the audio-derived force profile during contact. Real-robot experiments across four contact-rich tasks โ€” whiteboard wiping, carrot peeling, box stacking, and button pressing โ€” demonstrate that our force-aware pipeline enables successful manipulation from video generation, where a kinematic-only baseline fails.

We further show that the pipeline can serve as an automated force-aware data-generation engine: a closed-loop policy trained on the generated demonstrations generalizes across object placements and appearances.

Pipeline

Audio as the force signal.

Our vision pipeline localizes the object and gripper (MolmoPoint), segments them (SAM 2), and recovers depth and 3D point tracks (TAPIP3D) to detect contacts and infer force directions. The audio pipeline isolates the contact sound (SAM-Audio) and extracts loudness as a force-magnitude proxy. A 1 kHz impedance controller closes the loop on the audio-derived force profile.

Pipeline diagram: vision branch localizes, segments, and tracks in 3D to estimate force direction; audio branch isolates the contact sound and extracts loudness; the combined force-aware trajectory runs on a Franka Panda with closed-loop force regulation.

Policy Learning

The pipeline is also a data engine.

Beyond single-trajectory execution, we use the pipeline to generate training data: for all four tasks, we randomize the object position, run the full force-aware pipeline, and keep 50 successful rollouts per task as demonstrations, each recording end-effector pose, force profile, and two RGB views. We train a CNN-based Diffusion Policy from the wrist and external RGB images and the end-effector pose, in two variants: one without force input and one that additionally observes the measured 3-D contact force. At test time both command poses through the same fixed-stiffness impedance controller, with no force regulator, on unseen object placements and appearances.

The policy without force input already succeeds in 29/40 trials across the four tasks; adding force input raises this to 34/40, with the largest gains on peeling and pressing. Because the demonstrations are collected under force-aware execution, the recorded poses already encode the contact behavior: comparing all demonstrations with all successful rollouts as mean ± std over in-contact task progress (normalized end-effector path length accumulated during contact) shows both policies maintaining sustained contact and tracking the demonstrations within roughly 2 N on wiping, pressing, and stacking. Peeling is the exception: both policies press harder than the demonstrations, and the force-input policy presses hardest, which removes the skin more reliably.

WipingPeelingStackingPressingTotal
DP w/o force input8/108/108/105/1029/40
DP w/ force input9/1010/108/107/1034/40
Experimental setups for whiteboard wiping, carrot peeling, lamp button pressing, and chocolate box stacking: Franka Panda arms with a RealSense L515 external camera and a wrist-mounted RealSense D455. Contact force over in-contact task progress for all four tasks: data collection (green), policy without force input (red), and policy with force input (blue), shown as mean and standard deviation.