Unexpected error 0xc00d36b4 The data specified for the media type is invalid, inconsistent, or not supported by this object in Windows 10

Question

We have a video creation module  based on the Microsoft "Tutorial: Using the Sink Writer to Encode Video" at https://msdn.microsoft.com/en-us/library/windows/desktop/ff819477(v=vs.85).aspx.

This code worked great with MFVideoFormat_H264 on Windows 7, 8 and 8.1 to generate MP4 files but we get the following error on Windows 10 when invoking:

hr = pSinkWriter->SetInputMediaType(streamIndex, pMediaTypeIn, NULL);

although the Windows 10 machines have a valid H264 coded installed.

Is it a known limitation?

How to workaround.

Answer 1

Hi Eddy,

I get the same error, when I try to call IMFSinkWriter::SetInputMediaType() on Windows 10.

Same code works just fine on my Windows 8.1 system.

I've also check my system, it have valid H264 Encoders

--> Microsoft H264 Encoder MFT (version 10.0.14342.1000)

--> Intel Quick Sync Video H264 Encoder MFT (version 7.15.12.16)

Have you found any solution for this issue?

Thanks

Hendrik

Answer 2

0xC00D36B4 MF_E_INVALIDMEDIATYPE tells that you are trying to write a feed that requires conversion, and there is no suitable codec available. That is, the problem is with your media type which is not accepted by H.264 codec. You should have posted your video media type details here.

---

http://alax.info/blog/tag/directshow

Answer 3

Hi Roman ,

Thanks for the reply.

My input media type is YUY2.

I've checked that the H264 codec support YUY2 and NV12 as input.

I've done below experiment

Input Media type YUY2  -->  IMFSinkWriter Target media type MFVideoFormat_WMV3  (Works)

Input Media type YUY2  -->  IMFSinkWriter Target media type MFVideoFormat_H264 (Failed,IMFSinkWriter::SetInputMediaType() return 0xC00D36B4) 

Thanks,

Hendrik

 

Answer 4

Media type is not just subtype, you have to provide other attributes to make it well formed.

This tutorial updated to use YUY2 -> H264 works well in Windows 10.

---

http://alax.info/blog/tag/directshow

Answer 5

I fixed my problem by changing the average bit rate value from a funky formula that I used to use the Kush Gauge (see http://www.paromitapoddar.com/VideoCompression/kush.html). With this done, things went ok.

Eddy