| Previous | Next |
| NS_E_ATTRIBUTE_NOT_ALLOWED | NS_E_DATA_UNIT_EXTENSION_TOO_LARGE |
NS_E_INVALID_EDL
What NS_E_INVALID_EDL means at its owning API
When this result (0xC00D0BD8) appears, the first blocked transition is the edit decision list contains invalid timing, ordering or source-range information. In practice, the invalid edl media-format check must be reconstructed from the same URL, stream, object instance and call sequence.
A controlled media-format test
- Log
0xC00D0BD8, this result, the exact operation and the first failure time. - Preserve source time range, pass number, preprocessing state, EDL entries in source order and the output mode selected for the stream.
- Perform one isolated test: reduce the EDL to one monotonic source interval and add entries back until the first invalid timing relationship returns.
- Repeat through the same API and protocol path; a different player or local-copy test is useful only as a comparison, not as proof that the invalid edl media-format check is fixed.
What completed, and what did not
Before the invalid edl media-format check, earlier setup may have succeeded, but the edit decision list contains invalid timing, ordering or source-range information was not completed. This is why logs should preserve both the last successful call and this result.
A focused comparison is to reduce the EDL to one monotonic source interval and add entries back until the first invalid timing relationship returns. This isolates the disputed precondition without changing the media identity or unrelated machine settings.
Profile and sample evidence
| Capture | Why it matters |
|---|---|
| Owning call | Record the API method, object identity, thread or callback and timestamp for the invalid edl media-format check. |
| Values to record | source time range, pass number, preprocessing state, EDL entries in source order and the output mode selected for the stream. |
| Object instance | Note when the reader, writer, graph, URL object, streaming session or metadata provider was created; stale state can reproduce it after configuration has changed. |
| Comparison case | Use one known-good resource that exercises the same invalid edl media-format check while changing only the rejected precondition. |
Misleading actions
- changing several profile and codec settings at once, which hides the first incompatible field.
- Record redacted identifiers, lengths, hashes and protocol fields needed to reproduce the invalid edl media-format check.
Nearby results are not interchangeable
Main distinction: It belongs to format, profile or sample processing, not merely to file-name or network resolution.
| Nearby HRESULT | How to compare it |
|---|---|
NS_E_ATTRIBUTE_READ_ONLY | the caller attempted to modify an attribute whose value is owned or computed by the SDK. |
NS_E_ATTRIBUTE_NOT_ALLOWED | the attribute is valid in the SDK but not legal for the selected media type or object. |
NS_E_DATA_UNIT_EXTENSION_TOO_LARGE | per-sample extension data exceeds the size that can be attached to the sample. |
Technical references
- Windows Media Format SDK overview
- Input, stream and output formats
- Profiles
- Windows Media SDK objects
- Microsoft HRESULT registry
Retain the post-fix trace so a later pipeline result is not mistaken for recurrence of this failure.
Looking for a different code? Search another status or error code.