Hyperion 2.5: how to turn ordinary video into HDR

Hyperion 2.5 guide on Morphic, layered veils of light over a dark ground

Hyperion 2.5 turns ordinary video into HDR: files that pass delivery checks, skies that stop banding, and bright areas that keep their detail instead of going flat white. Here is what it gets you, what to feed it, and when it will not help.

What you get out of it

What changesWhat it looks likeWhy you care
The file passes delivery checksYour export is accepted instead of bouncedMost broadcast and streaming specs refuse the 8-bit files every AI video model produces
Skies and gradients stop bandingA sunset fades smoothly instead of in visible stripesBanding is the single most common thing that makes good footage look cheap
Bright areas keep their detailA blown-out window shows cloud again, not flat whiteDetail that survived the conversion is detail you can grade later
A compositor can use the shotYour AI clip sits in the same scene as live actionWithout it, generated footage can only be cut next to real footage, never combined with it

How it works, in plain terms

An ordinary video file has 256 brightness steps per color, and everything brighter than a certain point simply gets flattened to white. A cloud, a lamp and the sun all end up as the same value. That is why a sunset bands, and why a bright window is a white rectangle.

Hyperion looks at each frame, works out what was probably in those flattened areas, paints the detail back in, and writes the result into a much bigger container with room for it.

The four things Hyperion does to each frame: finds the flattened areas, works out what belonged there, widens the container, then switches the color standard

Only one of those four steps needs a model. Finding the flattened areas, widening the container and switching the color standard are all fixed math. Guessing what belonged inside a blown-out sky is the hard part, and that is the part Hyperion learned by studying real HDR footage.

Worth being straight about: it is a very good guess, not a recovery. The detail was deleted when the file was first made, and nothing can read data that was never written. On a well-shot source that guess looks completely natural. On a badly blown-out one it looks invented.

A bright cloud, a light bulb and the sun all land on the same value in an ordinary video file, while HDR has room for all three

What to send it

The conversion amplifies whatever you give it, so a few minutes here saves a wasted render.

CheckWhat you wantIf it is wrong
Quality of the copyThe original export, not a re-downloadCompression blocks get magnified along with the real detail
ExposureBright areas that fade rather than go flat whiteExpect weaker results in those areas, and lower your expectations
Scan typeProgressive, not interlacedDeinterlace first. Interlaced footage converts badly
Order of workClean up and upscale before convertingDoing it afterwards means processing far bigger files for a worse result

Which file to ask for

Three answers cover almost everything. Ask for ProRes if a person is going to edit or grade it. Ask for EXR if it is going to a visual effects artist. Ask for H.265 if someone is just going to watch it.

The full breakdown, including why the file you work in should not be the file you deliver, is on ProRes vs EXR vs H.265.

When it will not help

  • Very dark or very blown-out footage. There is almost nothing left for the model to work from.
  • Interlaced footage that has not been deinterlaced first.
  • Heavily compressed downloads. Go back to the original file if you can.
  • Shots where the lighting swings around a lot, which can shimmer slightly between frames.

Your HDR export will probably look grey and flat when you open it. That is almost always the player, not the file: most browsers, QuickTime and editing timelines cannot display HDR properly. Check it on an HDR screen in a player that supports it before deciding something went wrong.

FAQs

What does Hyperion 2.5 actually do?

It turns ordinary video into HDR video. It finds the areas that were flattened when the original file was made, works out what detail belonged there, puts it back, and saves the result in a format with far more room for brightness and color. The result is a genuine HDR file, not a brightened copy of the original.

Is this the same as color grading?

No. Grading is a creative choice about how footage should look, made by a person. This is a technical change to what the file can hold. A converted file still needs grading, and it grades better than the original because there is more to work with.

Can it really bring back a blown-out sky?

It can put back something very close to what was there. The original detail was deleted when the file was first saved, so the model is making an informed guess based on real HDR footage it has studied. On well-shot material that guess looks natural. On heavily blown-out material it looks made up.

Are there settings to get right?

No. It runs automatically with no sliders to balance. The only real choice is which file format you want out, and that depends on where the footage is going next.

What kind of footage works best?

Clean, well-exposed, progressive footage straight from the original export. Higher quality in means better results out, because compression damage gets magnified along with everything else. Run any cleanup or upscaling before the conversion, not after.

Why would AI-generated video need this?

Because AI video models all produce the same basic kind of file, and most professional delivery specs will not accept it. Converting is what lets generated footage go into a real edit, a real grade, or a real visual effects shot instead of stopping at a preview.