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.
DPX sequence recovery
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
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
Its header, pixel offset, or payload may be damaged.
Files may be missing, renamed, or excluded from transfer.
Packing, endianness, descriptor, or data offset may be wrong.
Header fields or production metadata may be inconsistent.
Protect the source
Original sequence numbers identify gaps and production order.
Frames may differ in element layout or metadata.
Preserve DPX headers before creating derivatives.
Do this now
Record first and last frame, gaps, sizes, hashes, and timestamps.
Keep audio, EDL, color metadata, scan logs, slates, and transfer manifests.
Note dimensions, bit depth, packing, orientation, frame rate, and color pipeline.
Protect failing RAID, SAN, LTO, or shuttle drives before bulk rereads.
NEPFOSYS process
NEPFOSYS compares signatures, offsets, dimensions, packing, and payload length across the sequence.
Readable images and metadata are preserved without renumbering or overwriting sources.
Continuity, sample pixels, orientation, color fields, timestamps, and companion audio are checked.
A clear next step
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 reviewQuestions, answered
Yes, each file is generally a frame, though sequence context helps validate header values.
No. Preserve gaps so restored or re-created frames can be documented accurately.
No. The header fields, data offset, payload length, packing, and pixels still require validation.
DFW local · Nationwide mail-in