What does HRESULT 0x00040280 (VFW_S_DVD_NON_ONE_SEQUENTIAL) mean?

 
Previous Next
VFW_S_NOPREVIEWPIN VFW_S_DVD_CHANNEL_CONTENTS_NOT_AVAILABLE

VFW_S_DVD_NON_ONE_SEQUENTIAL

DVD title timing is not one continuous sequential program chain

VFW_S_DVD_NON_ONE_SEQUENTIAL is HRESULT 262784 (0x00040280) from Video for Windows. AllStat describes this result as “The current title was not a sequential set of chapters (PGC), and the returned timing information might not be continuous.” The high-order severity bit is clear, so this is a success result, but it carries more information than plain S_OK.

DVD navigation succeeded, but the current title is not a single sequential PGC, so returned timing may contain discontinuities.

Where the result is encountered

  • This result can appear in DVD Navigator title playback; record the producing interface and method rather than inferring behavior from the symbolic name alone.
  • This result can appear in branching or multi-angle DVD content; record the producing interface and method rather than inferring behavior from the symbolic name alone.
  • It can appear in applications building a timeline from DVD timing information; record the producing interface and method rather than inferring behavior from the symbolic name alone.

The same numeric success value can be mishandled when a wrapper exposes only a Boolean. Keep the original HRESULT until the code-specific outputs and state transition have been evaluated.

Diagnostic sequence

  • capture the raw HRESULT 0x00040280 immediately after the returning method and record whether the caller used SUCCEEDED, FAILED, equality testing, or exception translation.
  • Identify the exact owner of it: interface, method, object instance, provider or filter version, thread or apartment, and operation phase.
  • Validate the decisive contract boundary for it: the caller does not assume monotonically continuous title time across branches, cells, or program-chain transitions.
  • inspect every output parameter, count, status array, returned interface, or side effect that the method documentation associates with this success-with-information result.
  • Compare the observed state before and after it; do not assume that a success severity bit means every optional sub-operation completed.
  • reproduce the smallest request with the same object state and then change only the condition identified by the evidence before repeating the operation.

State boundary that must be proved

The central question for it is whether the caller does not assume monotonically continuous title time across branches, cells, or program-chain transitions. The HRESULT alone confirms neither unrelated work nor the quality of optional outputs.

A reliable interpretation of it names the exact method contract, the object generation, and the outputs that remain valid. This prevents a success-with-information result from being promoted to full success or demoted to a generic error.

Correct handling, retry, and recovery

Use DVD navigation events and chapter/cell information instead of treating title time as a simple linear media clock. Avoid frame-accurate calculations across discontinuities.

Retry it only when the recorded state can change the documented outcome. Repeating the same call is inappropriate for a stable end marker, cancellation, unsupported format, adjusted property, or partial result whose completed side effects have not been reconciled.

Evidence and telemetry to preserve

  • preserve title and PGC identifiers.
  • preserve cell and chapter sequence.
  • preserve current domain and angle.
  • preserve reported time before and after branch points.
  • preserve disc region and navigation events.

Also record vfw_s_dvd_non_one_sequential_operation, vfw_s_dvd_non_one_sequential_object, vfw_s_dvd_non_one_sequential_state_before, vfw_s_dvd_non_one_sequential_state_after, UTC time, process and thread identifiers, and a correlation ID. Keep secrets out of logs while retaining GUIDs, CLSIDs, media subtypes, property IDs, row identities, and hashes needed to distinguish objects.

Difference from nearby HRESULT values

VFW_S_DVD_NOT_ACCURATE concerns seek precision; it concerns the structure of the title timeline itself.

This distinction determines whether the caller should consume partial outputs, stop iteration, wait, reconfigure, notify the user, or perform no error recovery at all.

Developer and administrator guidance

When it crosses process, RPC, scripting, or managed-code boundaries, preserve the unsigned 32-bit value and symbolic name. A signed decimal rendering can obscure that the severity bit indicates success and can lead to incorrect exception or retry behavior.

A support report for it should include decimal 262784, hexadecimal 0x00040280, the AllStat meaning, the owning API, and the first detailed status or output that explains why the method did not return ordinary S_OK.

Practical validation scenario

An interactive DVD branches to alternate scenes. The player receives this status, marks the timeline as discontinuous, and uses navigator events to update position after each branch.

The negative test should preserve the condition that produces it; the recovery test should alter only that condition and verify the final state as well as the HRESULT.

References

Looking for a different code? Search another status or error code.