The shared bottleneck of the world-model race over the past two years: frames keep getting sharper, but interaction stays stuck on discrete commands — press a key, click a waypoint, the model responds one frame at a time. That is "watching", not "entering". And audio has long been missing from most open work: most open-source world models render video with no sound. On August 24, the Echo team at JD (Joy Future Academy, JD) released EchoWM, an attempt to fix both at once: an omnimodal world model that follows continuous 6-DoF navigation trajectories while jointly generating 720p video, environmental sound, music, and speech (arXiv:2608.23189).
A world you walk into, not just look at
EchoWM positions itself as an omnimodal world model: at 720p, video, environmental sound, music, and speech are generated in sync, while the model responds to continuous 6-DoF navigation in both first-person and third-person views. The paper's own phrasing: "responds to continuous navigation while jointly generating 720p video, environmental sound, music and speech".
The interaction design is the interesting part. The paper organizes control around "camera intent": in first-person scenes it specifies how the observer moves; in third-person scenes, camera–character dynamics are learned directly from data, with no view-specific controllers. Discrete commands and continuous poses are both mapped onto a shared metric-scale relative 6-DoF trajectory, and dataset-level calibration keeps motion magnitude consistent across heterogeneous training data.
8-step long video, 4-step causal world model
On the training side, the team built a complementary data engine to jointly learn audio-visual generation and trajectory control, with progressive training followed by autoregressive post-training for long-horizon generation. The open repository lists: 8-step long-video generation, a 4-step causal world model, composable cross-shot memory that preserves character appearance and voice, and stable 60-second rollouts under metric 6-DoF control.
The open-source part is substantial: the GitHub repo jd-opensource/JoyAI-Echo (currently 1.9k stars, 168 forks) ships inference code and full weights — a ~46 GB safetensors main model plus a ~24 GB Gemma-3-12B text encoder. At the default 25 fps, 241 frames, 1280×736 setting, peak VRAM sits around 46–50 GB, so a single 48 GB card or an 80 GB H100/A100 is enough. One day after submission, the paper picked up 64 upvotes on Hugging Face Daily Papers, reaching the front of the August 25 trending list.
Generous release, clear limits
The cold-water points are equally clear. First, the base is Lightricks' LTX2.3 video generator plus a Google Gemma text encoder — EchoWM is a modification and post-training effort built on LTX shoulders, not a from-scratch pretrain. Second, the license restricts use to academic research and non-commercial purposes (inheriting the LTX-2 Community License); commercial use requires contacting Lightricks, so product teams should read the terms first. Third, the current release supports text-to-video and multi-shot long video with paired audio-video memory only — image-to-video (I2V) is not yet supported, and the team says a future version will add it.
Per the repo updates, JoyAI-Echo 1.5 has been announced with code "coming soon", and the TODO list still includes the Echo-SR super-resolution module and a Director Agent. On the community side, a third-party ComfyUI node already exists, supporting per-shot editable prompts and cross-shot memory chaining.
So what
The next round of world-model competition probably won't be about "a sharper frame". It will be about two things: continuous control (can you actually walk in?) and audio completeness (once you're in, is there sound?). EchoWM bundles both into one open release — the license limits commercial use, but it hands the community a reproducible, modifiable omnimodal baseline. For teams working on interactive content, robot-simulation data generation, or game prototyping, these 46 GB of weights are worth a look; the reference implementation and paper are both on GitHub.