Single Frame .mov File

Posted to LinkedIn

Not every delivery asset is in motion. Whether a text overlay or a simple background to be layered with other assets.

You might assume that PNG or maybe TIFF with alpha is the automatic answer. Jpeg if no alpha is needed. For some systems, that is ideal. And chances are any media server can support just about any still frame format.

But just because you can do it, and you’re used to doing it, doesn’t mean it’s the best choice.

I’ve been increasingly asked for single-frame Notch LC mov file (or single-frame HAP).

It seemed counterintuitive at first when I heard about it. A single PNG will have a fairly low file size. Why would it make any difference?

For codecs that are built specifically with the GPU in mind (NotchLC, HAP, etc) it can actually make a big difference. Certain media servers and hardware are geared to take advantage of a GPU’s speed and efficiency. As well as reduce usage of RAM, PCI-E bandwidth, and benefit from a parallel workload between CPU & GPU.

CPUs are optimized for serial tasks. GPUs are optimized for parallel tasks. At any given moment a media server needs to perform several tasks in parallel.

With larger resolutions and multiple layers of media stacked on top of each other, composited live in the server, efficiency becomes more and more important.