How it works · Path D

Getting it to you

A volumetric performance starts out far too big for any internet connection. Getting it into your browser takes a different way of storing it, plus a player that never makes you wait between pieces.

2 interactive demos · about 5 minutes

Size

Terabytes, if you're not careful

A normal video stores one flat picture per frame. A volumetric video stores the whole scene: millions of splats, each with dozens of numbers. Do that 60 times a second and the file size grows very fast.

Two ideas do most of the work to bring it down:

  • Don’t store what didn’t change. When splats keep track of their own lifespan and motion, a single splat can cover many frames instead of being saved again in each one.
  • Store the numbers efficiently. Most values don’t need full precision, and similar values compress well together.

Use the sliders to see how quickly the size drops from impossible to streamable.

Try it
How big is a volumetric video?
Rebuilt every frame60 full scenes per second
893 GB
Splats that lastmove the slider
893 GB
Compressedmove the slider
893 GB
On a typical 25 Mbps connection that final size takes 3 days to arrive, for 30 s of performance. (bars use a log scale: each step is a factor of ten)
A single splat is about 60 numbers. Rebuild millions of them 60 times a second and even a short clip runs to terabytes. Two ideas bring that down to something your connection can handle: let each splat last across many frames instead of storing it again every frame, and store its numbers efficiently. These are general figures for illustration, not our exact ones.
Streaming

Long takes, no breaks

You shouldn’t have to download an entire performance before it starts. So a long take is split into pieces. As soon as the first piece arrives, playback begins, and the next pieces download in the background while you watch.

When one piece ends, the player hands off to the next one without a gap, so the performance plays as one continuous take. You can keep moving the camera right through a handoff and you won’t notice it.

Try it
Seamless pieces
A long performance is split into pieces. While one piece plays, the next one downloads in the background, and the player hands off between them without a gap. On a slow connection, playback simply waits for the next piece. The piece sizes and timings here are just for illustration.
Protection

Built to protect performers

A Mirage performance belongs to the performer, and so does their likeness. It’s delivered in our own protected streaming format and only plays in our own player. There’s no file to download and repost somewhere else.

That matters to the creators we work with, and it’s a big part of why we build every step ourselves, from the capture to the player in your browser.

Check yourself

Two quick questions

Key ideas
  • Stored the simple way, volumetric video can run to terabytes.
  • Splats that last across many frames, plus efficient storage, make it small enough to stream.
  • Long performances stream as pieces that hand off to each other without a gap.
  • Performances stream in a protected format, so they can't simply be downloaded.
1Which idea saves the most space for moving splats?
2Why split a long performance into pieces?
0 of 2 answered