| Previous | Next |
| NS_E_PDA_CANNOT_TRANSCODE_TO_AUDIO | NS_E_PDA_CANNOT_TRANSCODE_TO_IMAGE |
NS_E_PDA_CANNOT_TRANSCODE_TO_VIDEO
Failure boundary and ownership
NS_E_PDA_CANNOT_TRANSCODE_TO_VIDEO with value 0xC00D123E records finding a video target format and profile accepted by the device. The producing call and its state are more diagnostic than a later aggregate Player failure.
Underlying mechanism
At the checkpoint, before transfer, the Player can compare the source media type with the device’s format capabilities and build a conversion path; Source decoding, target encoding, metadata generation, temporary-cache output and optional encryption are separate phases. The page-specific boundary is finding a video target format and profile accepted by the device.
A source that plays locally can still lack a valid conversion path to the specific format and limits advertised by the connected device. The condition can be reproduced when the device requires a resolution/codec combination the installed encoder cannot produce.
Trace fields worth keeping
| Evidence | Why it matters for cannot transcode to video |
|---|---|
| Producing object and operation | source path and media type, decoder and encoder identifiers, target audio/video/image format, device capability response, output dimensions/bitrate, cache path and free space, EFS state, conversion stage and first codec HRESULT |
| Decisive observation | device video codecs, dimensions/frame-rate limits, source type and encoder availability |
| Generation identity | Record the same disc, device, job or Player operation generation that returned this result; a reconnect or media change creates a different test. |
| Underlying result | Keep the first device, filesystem, COM, codec, DirectShow, IMAPI or BITS result seen before the Player mapped it to this result. |
| Controlled comparison | Repeat the producing call after changing only this condition: select a supported video profile or omit the incompatible item. |
What the comparison proves
| Observation | Interpretation |
|---|---|
| The recorded values match the boundary | The result is consistent with finding a video target format and profile accepted by the device; correct that state before changing unrelated codecs, drivers or playlists. |
| A lower layer failed before this result | Preserve that earlier HRESULT or device result because this result may be only the Player-level mapping. |
| The same call passes after one isolated change | The comparison supports the cannot transcode to video diagnosis rather than a broad installation failure. |
| The code changes after retesting it | The boundary was passed; diagnose the new HRESULT as the next independent stage. |
It scopes the failure to finding a video target format and profile accepted by the device.
Decision path
- Capture
0xC00D123E, it, the exact Player/API operation and the first timestamp at which it appears. - Save device video codecs, dimensions/frame-rate limits, source type and encoder availability; do this before ejecting media, reconnecting a device, canceling a job or rebuilding the Player object.
- correlate the result with source path and media type, decoder and encoder identifiers, target audio/video/image format, device capability response, output dimensions/bitrate, cache path and free space, EFS state, conversion stage and first codec HRESULT.
- Reproduce once with the original source and destination, then apply only this change: select a supported video profile or omit the incompatible item.
- Create a fresh operation generation and verify that the original call advances beyond the cannot transcode to video boundary.
Close alternatives
| Related result | Different diagnostic boundary |
|---|---|
NS_E_PDA_CANNOT_TRANSCODE_TO_AUDIO | finding an audio target format accepted by the device |
NS_E_PDA_CANNOT_TRANSCODE_TO_IMAGE | finding an image target type and dimensions accepted by the device |
NS_E_PDA_FAILED_TO_ENCRYPT_TRANSCODED_FILE | reading or securing converted output when the source/cache file is EFS-encrypted |
Safe correction
Correct this boundary by making sure you select a supported video profile or omit the incompatible item. Then reacquire the interface or media state that produced it and repeat that call.
When verifying it, do not install codec packs or clear every cache before saving the source/target media types and first codec activation error; Change one decoder, encoder or target setting at a time.
Video conversion adds geometry, frame-rate and profile constraints
Preserve the source video subtype and decoded dimensions, then compare them with each device-advertised video profile: codec, profile/level, width, height, frame rate, pixel aspect ratio and bitrate. An audio encoder being available does not satisfy this path. The selected video encoder must produce a complete target combination accepted by the device, often together with a separately compatible audio stream.
Test with one conservative device profile rather than changing codec, resolution and frame rate simultaneously. A failure to instantiate the video encoder differs from a profile that instantiates but rejects dimensions or rate control. Record that boundary so the correction targets encoder availability, scaling or device limits instead of unrelated synchronization settings.
Source material
- Sending a file to a portable device.
- Windows Media Device Manager metadata constants.
- Portable-device capabilities and shell requirements.
- WAVEFORMATEX structure.
- Encrypting File System overview.
Looking for a different code? Search another status or error code.