DPX sequence recovery

A DPX production can lose individual frames or header fields while the rest of the image sequence remains usable.

Each DPX file normally represents one high-quality image frame with a binary header and pixel data. Storage damage, incomplete transfer, or naming changes can affect continuity, offsets, orientation, bit depth, or only a subset of frames.

Understand the symptom

The DPX header declares image-data offset, dimensions, elements, orientation, bit depth, packing, and frame context.

WHY

What is happening

DPX is a frame-based format with structured binary metadata. A valid magic value alone does not prove that declared offsets, dimensions, packing, or pixel payload are complete.

What you may see

Symptoms that change the recovery path.

01

One frame will not open

Its header, pixel offset, or payload may be damaged.

02

Sequence has skipped numbers

Files may be missing, renamed, or excluded from transfer.

03

Image appears shifted or scrambled

Packing, endianness, descriptor, or data offset may be wrong.

04

Color or orientation is incorrect

Header fields or production metadata may be inconsistent.

Protect the source

Actions that can make the situation worse.

01

Renumbering hides evidence

Original sequence numbers identify gaps and production order.

02

Header cloning can misinterpret data

Frames may differ in element layout or metadata.

03

Converting loses production fields

Preserve DPX headers before creating derivatives.

Do this now

Safe steps before evaluation.

01

Inventory the full sequence

Record first and last frame, gaps, sizes, hashes, and timestamps.

02

Preserve companion assets

Keep audio, EDL, color metadata, scan logs, slates, and transfer manifests.

03

Record expected image properties

Note dimensions, bit depth, packing, orientation, frame rate, and color pipeline.

04

Image source storage

Protect failing RAID, SAN, LTO, or shuttle drives before bulk rereads.

NEPFOSYS process

How a data-first evaluation proceeds.

01

Frame and header analysis

NEPFOSYS compares signatures, offsets, dimensions, packing, and payload length across the sequence.

02

Copy-based frame extraction

Readable images and metadata are preserved without renumbering or overwriting sources.

03

Sequence validation

Continuity, sample pixels, orientation, color fields, timestamps, and companion audio are checked.

A clear next step

Preserve the original device before another repair or recovery attempt.

Start a case with the exact symptoms, incident timeline, prior attempts, encryption details, and the files that matter most. NEPFOSYS will route the case to the appropriate DFW intake or nationwide mail-in path.

Start with a case review

Questions, answered

What customers ask before starting.

Can one DPX frame be recovered independently?

Yes, each file is generally a frame, though sequence context helps validate header values.

Should missing frames be renumbered?

No. Preserve gaps so restored or re-created frames can be documented accurately.

Does a correct SDPX signature prove the image is intact?

No. The header fields, data offset, payload length, packing, and pixels still require validation.

DFW local · Nationwide mail-in

Protect the device. Start with the facts.

Start my recovery case