Fix NS_E_SMPTEMODE_MISMATCH (0XC00D1BAD) Quickly

I know this error is infuriating—you're mid-encode and Windows throws 0XC00D1BAD at you. Let's get you back on track.

The Quick Fix

Open your project in the tool you're using (Expression Encoder, Windows Media Encoder, or a custom app calling the Windows Media Format SDK). Then check the SMPTE timecode mode for each audience. Here's the deal: every audience that references the same source index must use the same timecode mode—either drop-frame or non-drop-frame. Mixing them causes this exact error.

In most encoders, you'll find the SMPTE setting under Output Settings or Audience Properties. Look for a dropdown labeled SMPTE Timecode Mode or Timecode Format. Set all audiences to the same value. If you're using a script or SDK, here's a snippet that forces consistency:

// C# example for Windows Media Format SDK
foreach (IWMStreamConfig stream in profile.StreamConfigs)
{
    if (stream.StreamType == WMT_MEDIATYPE_VIDEO)
    {
        // Force non-drop-frame on all streams
        stream.SetSMPTETimecodeMode(WMT_TIMECODE_MODE_NON_DROP_FRAME);
    }
}

Save, re-import the profile, and re-run the encode. That usually clears it.

Why This Works

The SMPTE timecode mode tells the decoder how to interpret the timecode embedded in the video. Drop-frame timecode skips certain frame numbers to keep time aligned with real-world time; non-drop-frame counts every frame. If one audience expects drop-frame and another expects non-drop-frame for the same video source, the muxer can't produce a consistent output. The error message is literal: the same source index must have the same timecode mode across all audiences. Aligning them removes the contradiction.

Less Common Variations

Sometimes the mismatch isn't obvious. Here are scenarios I've seen trip people up:

1. Source Index Changes After Editing

If you edited the source file (trimmed, re-encoded) and the tool picked up a new timecode mode, old audiences might still reference the old mode. Re-import the source file or reset all audiences to the new mode.

2. Mixed Frame Rates

You might have one audience at 29.97 fps (drop-frame) and another at 30 fps (non-drop-frame). Even if the mode looks the same, the frame rate difference can trigger the error. Set both to the same frame rate and timecode mode.

3. Third-Party Plugins

Some plugins override the timecode mode silently. If the above doesn't work, disable any encoding plugins and try again. The error should disappear if the plugin was the culprit.

Prevention

The easiest way to avoid this is to standardize your SMPTE settings before you add audiences. Decide on a timecode mode (non-drop-frame is generally safer for web delivery) and stick with it across every audience. Also, when you duplicate an audience, the duplicate inherits the timecode mode—so if you change the original later, update the copy too.

Another tip: if you're pulling profiles from different sources, import them all at once and verify the SMPTE settings before encoding. A quick check saves a nasty surprise.

And if you're building custom encoding apps with the SDK, centralize the timecode mode assignment in one function—that way, you never accidentally set different modes.

This error isn't a monster once you know what it's looking for. Match those modes, and you're good to go.