Luminary for Dolby Vision Metadata Management

Detailed Summary

Why Dolby Vision Metadata QC Is a Challenge

When a streamer takes a series international, every new market brings its own rules, legalities, and cultural sensitivities. Shots get removed, scenes get retimed, and content gets reworded. For traditional television, that kind of compliance editing is routine. For prestige Dolby Vision titles delivered as IMF packages with Dolby Atmos, it’s a different game.

You can make all of those edits to the master. But Dolby Vision carries shot-by-shot L1 analysis and trim metadata alongside the picture, and every edit has to keep that metadata in exactly the right place. Get it wrong, and the failures show up downstream: jumping frames, broken tone mapping, and playback problems on the platform.

The core problem is visibility. Looking at an IMF timeline in DaVinci Resolve or another editing tool, you might never know the metadata is wrong, because you can’t see it in detail. Dolby’s Metafier, the command-line tool for working with Dolby Vision XMLs, can manipulate nearly everything: mastering targets, displays, trims, head and tail edits, and padding. But it’s command-line-only, which makes it difficult for most mortals to use.

That gap – between what the metadata requires and what your tools let you see – is why I wrote Luminary.

What Luminary Is – And What It Will Never Do

Luminary is a standalone desktop application for viewing, inspecting, QC’ing, and editing Dolby Vision metadata timelines. Open a Dolby Vision XML with a keyboard shortcut or drag it onto the window, and you get a timeline showing every clip in the sequence, synced to a full set of inspection pages.

One design decision matters more than any feature: Luminary never edits your XML directly. The Dolby spec does not want anyone manipulating these files in a text editor – that is a recipe for data corruption and formatting errors. Every edit Luminary performs runs through Dolby’s official Metafier tool, ensuring the output remains standards-compliant.

Touring the Interface

Click any clip, and the summary page shows the information you need most for that shot. From there, dedicated views take you as deep as you want to go:

Timeline interactivity got particular attention – I hate sluggish, awkward timelines. Keyboard shortcuts zoom in and out, jump to the previous or next shot, and flip between pages. Shift+Z toggles your zoom level, and holding Shift while dragging a region zooms straight into it.

Editing Metadata Without Touching the XML

The Metafier toolbar at the top of Luminary lets you run Metafier commands interactively. In the demo, you’ll see a complete edit pass:

Behind the scenes, all of this is timecode-based rather than frame-number-based. Everything in a Dolby Vision XML revolves around frame numbers, so Luminary does the conversion math in the background – drop frame or non-drop, 23.98, 29.97, 59.94, or 60 – and lets you type timecode like a human.

Syncing Luminary with DaVinci Resolve

Inspecting XMLs is useful for troubleshooting and workflow. But the deeper power lies in synchronizing Luminary with DaVinci Resolve. Here’s the setup, using a Dolby Vision IMF package like the compliance editing workflow described earlier:

Now, click a shot in Luminary, and Resolve’s playhead jumps to it, frame accurate. You can walk the timeline cut point by cut point, verifying each one against detailed metadata while viewing the image through the CMU with tone mapping.

Flip the sync direction from Luminary-to-Resolve to Resolve-to-Luminary, and the Luminary playhead follows wherever you park in Resolve instead. With a dual monitor setup – Resolve on one display, Luminary on the other – you can QC an entire show this way.

A Real-World Failure: The Original vs. Imported Metadata Trap

Here’s the exact class of error that drove me to build this tool. In the demo, a compliance edit removes one shot from the IMF timeline: mark an in and out point (using Luminary to find the precise cut points, since the Resolve timeline was never scene-detected), delete the shot, and re-pull the XML.

The result looks fine at first. Then, tabbing through the cut points: “this cut’s right, this cut’s right – that cut is obviously wrong”. The CMU’s tone mapping confirms it. Every cut after the edit point has slipped.

The cause is a single dropdown. In Resolve’s Dolby Vision palette, each clip selects its metadata source:

One tiny dropdown in the Dolby Vision palette can throw off an entire timeline, because Resolve doesn’t know which timecode, which XML, and which metadata to use unless you specify it. I used to discover this the hard way: encode the whole show, watch it down through tone mapping, and find wrong metadata on shots I never touched. Luminary turns that mystery into a visual check – walk the timeline, verify the cut points, and look exactly where you made your edits.

QC’ing a Remote Resolve Over the Network

Luminary isn’t tied to the Resolve on your own machine – it can reach other Resolve systems over the network. If you run a main hero system plus an assist station for email, scopes, and documents, this is a perfect workflow:

There’s no exporting XMLs, copying them to the NAS, and importing on the other side. Pull, inspect, validate, QC – with the same interactivity as a local session.

Availability, and the New Retrograde Labs Free Tools Library

Luminary is available now at retrograde.tools as a one-month rental or a perpetual license – at the time of publishing, $49 for the rental, $299 perpetual for macOS and Windows, and $499 adding Linux. The app also extracts Dolby Vision metadata directly from encoded J2K MXF files through Metafier – a feature beyond the scope of this demo.

While you’re at the site, look at the rest of the catalog: DCTLs like DyePrint and Flora, Python workflow scripts, and an entire library of free tools. A lot of them will look familiar from Mixing Light over the years – scripts, DCTLs, and Fusion effects I’ve published here. I’ve reorganized all of them, cleaned up their interfaces, fixed long-standing bugs, added documentation, and published them open source on GitHub. If you’ve used my older free tools, the new versions are worth the revisit.

I’m using Luminary day in and day out on my own Dolby Vision work, and it’s under active development. If there’s a feature you need, don’t hesitate to reach out – I’d be happy to try to implement it.