Question Getting WindowsVideoMedia error 0xc00d36b4 on some devices.

Some of our clients have reported that some in-game videos don't play while some do play correctly. So, I took a look at their Player.log and found that there were some errors raised. These are some of them:

WindowsVideoMedia error 0xc00d36b4 while reading archive:/CAB-efe72908991b9f35788263125cf7d6bd/CAB-efe72908991b9f35788263125cf7d6bd.resource
Context: Setting media type for first video stream
Error details: The data specified for the media type is invalid, inconsistent, or not supported by this object.
Track types:
Audio Track, type: 3-ca
Audio Track, type: %10%16
Video Track [1280 x 720], type: H264

WindowsVideoMedia error 0xc00d36b4 while reading archive:/CAB-efe72908991b9f35788263125cf7d6bd/CAB-efe72908991b9f35788263125cf7d6bd.resource
Context: Setting media type for first video stream
Error details: The data specified for the media type is invalid, inconsistent, or not supported by this object.
Track types:
Audio Track, type: %10%16
Video Track [1920 x 1080], type: H264

All video file format is ".mp4". I'm not sure what caused the error, but my guess is the audio track because other files that play correctly were also encoded in H264 codec as well and they do not have an audio track.

The question is:
1. How do I encode the videos to avoid these errors.
2. How do I catch these errors in the code. I try surrounding the part that sets VideoPlayer.clip and the part that calls VideoPlayer.Play() with a try/catch block, but the errors still got through.

I've attached the Player.log files of the clients that reported the issue.
Thanks for the help!

 

getting the same audio errors even in the Unity Editor right after movie asset import when running editor on windows 7
this has started somewhen AFTER Unity 2019.4.8f1 ( which DOES NOT show the problem )
( 2019.4.17f1 and all later version i tested have the problem )

So my guess:

• a videoplayer update that happened AFTER Unity 2019.4.8f1 causes/triggers this error on WINDOWS 7 machines
• Unity Editor AND builds running on W7 seem to be affected
• Build plays video perfectly fine on W10

so your clients might try to run the game on windows 7 and getting those error in the player too

That s quite a serious issue, that slipped through Unity QA here, as W7 is still a supported OS for builds ( and i hope editor too ? )
On top of that tje issue is difficult to catch for game developers using W10 for the editor and to build the games, while players still might run on W7...
Definitely worth a bug report ... will do the same as soon as i find the time...

 

BTW:
using different audio codecs ( which are supported by the windows mediafoundation ) doesnt help, they throw the same error
on top of that, windows mediaplayer itself plays the videos+audio perfectly fine here on Windows 7, so its definitely a Unity bug ...

 

I submitted a bugreport together with a small repro project
I hope this issue will be fixed, as it affects all games build in later unity versions and using some kind of mp4 encoded videos with audio when players run the games on Windows 7

 

@spacefrog Thank you very much for looking into the problem for me. I would have been trying to catch that error without your help.

 

just got a response to my bug report - apparently the issue was already known
Would be great if people would vote on the following url to ensure that it finally get fixed

https://issuetracker.unity3d.com/is...own-when-loading-a-video-with-the-videoplayer

 

This is happening to me too on latest Unity 2019.4.19
However videos works on 2019.4.14
I use windows 7 too


Context: Setting media type for first video stream
Error details: The data specified for the media type is invalid, inconsistent, or not supported by this object.
Track types:
Audio Track, type: %10%16
Video Track [624 x 1000], type: H264

 

Your experience that it's working on 2019.4.14 sounds plausible - according to the issue tracker the problem got introduced with 2019.4.16f1
I cant imagine why this doesnt get higher priority ?
Be sure to give your vote on the issue tracker page to ensure a faster fix ....

 

EDIT:
ahh ... just read the "Fix in Review" line ....
so its just my patience running out, but at least it seems that we get a fix ....
and its planned for LTS versions too...
took some time... but okay ... better late then never

 

I am relieved that it is planned for the LTS version. Still, the wait is on.

 

Just verfied and confirmed that the bug is still existing in 2020.3.0f1 (which is called LTS nevertheless !! )
Additionally it still exists in 2019.4.22f1 and 2021.1.0b11....

 

I am also getting this bug. Any news on this?

 

https://issuetracker.unity3d.com/is...own-when-loading-a-video-with-the-videoplayer
@TruongVu Here is the issue's link. They said the fix is in review for 2021.2, but for other versions, they just planned for the fix. We can only wait.

 

Update: It is now fixed for 2021.2. Still in the plan for 2019.4, 2020.3., 2021.1.

 

To be totally exact it WILL be fixed in the next 2021.2 alpha drop, which will be 2021.2.a13
The current alpha build 2021.2a12 STILL shows the issue ( just verfied it myself here )

Really took a long time to fix this. Even more so when considering that the cause was some W10 specific code that wasnt necessary on W7 anyways

 

Finally it seems that the fix has landed in the most recent alpha build 2021.2.0a13 ( according to the release notes)

Though the fix is still not backported to the most recent LTS builds ( Unity 2019.4.24f1 and 2020.3.4f1 ) and the tech stream 2021.1.3f1

I'm currently downloading and installing the alpha build and report back if it fixes my issue

 

Okay - fix seems to work for me in Unity 2021.2.0a14
There is a new warning being logged in the console
"WindowsVideoMedia error unhandled Color Standard: 0 falling back to default this may result in rendering issues"

But maybe thats something with my encoding ... anyways... hope we ASAP see the fix land in the officially released versions too ...

 

I get this too and I have Unity 2021.2.0a9.1276 running

"WindowsVideoMedia error unhandled Color Standard: 0 falling back to default this may result in rendering issues"

 

Getting the same message with a pretty bog-standard H264 video in 2021.2b7 (don't get it in 2021.1).

"WindowsVideoMedia error unhandled Color Standard: 0 falling back to default this may result in rendering issues"

Seems to still work, but would be great to have even a tiny clue from the editor about what that actually means to get rid of the message.

 

Some of our players also experience this issue.



We're using Unity 2020.3.12f1

 

still have the same issue but I found a work around, select your video in the projects panel
tick transcode
convert your codec to VP8

 

but there is a solution!
still not working on W7... but if you badly need this for now you can extract frames of your video and animation frames like a gif into unity

 

As others have mentioned, I'm also getting this warning in 2021.2.0b15:

WindowsVideoMedia error unhandled Color Standard: 0 falling back to default this may result in rendering issues

This is the only google result for the issue, so would be great to get some more info. Is it a bug, or do I need to change my encoding?

 

Code (JavaScript):

1. WindowsVideoMedia error unhandled Color Standard: 0 falling back to default this may result in rendering issues

It worked for me after i changed the Transcode settings to "Code = VP8" (Auto or x264 gave me the error)

 

Few things about this.

1) In standalone build, it throws a null ref error about once in 100 times. So something is still going on.

2) Can we not set the color profiles in the import settings? Then Unity doesn't have to throw errors or guess.

3) If I set it to VP8 + low bitrate the error disappears...even on 4k mp4 files...so something is going on...

 

As for 1) I will try to get you the exact error msg, it was overwritten in the player log.

2) Good to hear.
3) The thing is it requires the bitrate to be "LOW", I thought the codec VP8 is preventing this msg, then why is bitrate also having influence? I am probably not educated enough in the videos and codecs so kindly do tell in depth

Lastly, if I set it to VP8, will my clients need VP8 codec installed separately to have the video playback in game? Or is everything handled in engine as long as the source video is transcoded?

Thanking you in advance,

 

On checking again, the bitrate seems to have no influence! Thanks for clearing that up!

 

I am trying to import a video file but keep getting this error:

WindowsVideoMedia error 0xc00d36b4 while reading D:/Climber/ClimberGame/Assets/Video/Splash-1.mp4

Context: Setting media type for first video stream
Error details: The data specified for the media type is invalid, inconsistent, or not supported by this object.
Track types:
Audio Track, type: %10%16
Video Track [1920 x 1080], type: H264

Everything plays the video fine. I have tried converting it with Handbrake but nothing seems to help. Windows plays it. YouTube converts it. I just can't import it into Unity. Suggestions?

 

Upgraded and that fixed it.

Now I am getting this warning:

First video frame not zero: 2 (0.066667s). Result may be out of sync. Please make sure tracks all start at 0 in D:/Climber/ClimberGame/Assets/Video/splash.mp4

Should I care? Or ignore it? The video plays fine. I exported it from Adobe Premiere and re-exported it using Handbrake and both files get the same error.

 

It is not a problem. Thanks.

 

Hello, I am an end user (buyer) of two Unity games on Windows 7 , Magia X and Demon Gaze Extra. Both have the same problem described in this topic,the 0xc00d36b4 error : the intro video or any mp4 video simply won't play in-game (it just shows black screen with no sound) even when I could play them outside fine. I've looked up player.log and found the exact same kind of errors demonstrated by OP :

WindowsVideoMedia error 0xc00d36b4 while reading G:/steam/steamapps/common/Magia X/Magia X_Data/StreamingAssets/assets/assetdata_part_1/video/edel/preview_edel.mp4

Context: Setting media type for first video stream
Error details: The data specified for the media type is invalid, inconsistent, or not supported by this object.
Track types:
Video Track [1280 x 720], type: H264

And there would be the same error for every video I tried to play in-game.


Now, it's to my understanding that Unity had long fixed this issue in their engine for devs side on new version of Unity but in my case both developers of these two games show no sign of updating the game nor offering any kind of supports, both can't even be reached. So after much struggle with google on my issues I've finally arrived at this place. I'm hoping that someone would be kind enough to offer solution for this problem for end users like me who apparently can't just update the game engine on their own. Magia X in particular have many mp4 that are played when you are fighting so being unable to play the mp4 detract a lot from game experience.

 

Can you please at least tell what's the component that breaks playing mp4 in Unity on windows 7 but not on windows 8,10 ?

 

What is compiled IL ? Do I, as enduser, have access to them or do I need special tool to do so ?

 

eso soluciona el problema, excelente aporte.

 

Just for future reference, maybe it helps others. I was trying to get rid of the color standard warnings, and noticed that if I used 'Hardware Encoding' in Adobe Media Encoder, it didn't write the color metadata at all (as in 'color_range' etc. was 'unknown'). But if I switched to 'Software Encoding', it started to write the proper metadata.

 

I exported using Davinci Resolve in mp4/H.264 and the video only played once in Editor or in Build, afterwards it threw errors and was stuck on some frame or just black. (In Build, it looped fine until you reloaded the level. Then it was stuck and I had to restart the game)

Transcode with "auto" didn't work but now I used "VP8" as suggested here, which works for me. No errors, plays in Editor, works in build even after switch scenes a few times.

 

I zipped the mp4 file that I used:
https://pecker-game.com/unity/tutorialVideo1_v3.zip

 

Yes, same error code 0xc00d36b4. I submitted a bug report: CASE IN-39768

 

same error, I'm using video mp4 H.264