Search Issue Tracker
Fixed in 2022.1.X
Votes
1
Found in
2021.2
2021.2.0a1
2021.2.0b17
2022.1
Issue ID
1374819
Regression
Yes
[Video] "WindowsVideoMedia error unhandled Color Standard" warning when importing various video formats
Reproduction steps:
1. Open attached "VideoURP.zip" project
2. In Project window, navigate to and select "Assets/Video/mov.mov"
3. Right-Click -> Reimport the video Asset
4. Observe Console window
Expected result: No warnings
Actual result: "WindowsVideoMedia error unhandled Color Standard: 0 falling back to default this may result in rendering issues" warnings
Reproducible with: 2021.2.0a1, 2021.2.0b17, 2022.1.0a13
Not reproducible with: 2019.4.32f1, 2020.3.21f1, 2021.1.27f1
Reproduces with formats: .m4v, .avi, .mov, .mp4, .wmv
Does not reproduce with formats: .webm
-
Cricket2718
Apr 29, 2023 02:09
AZAIKANG's solution of changing the Mp4 Codec from H264 to VP8 worked for me!
-
DBTX1
Mar 22, 2023 20:14
My friend AZAIKANG is right. I am using 20201.3.20f1 and changing the codec to VP8 fixed the warning and the actual rendering issue.
-
EyeDev44
Mar 09, 2023 09:11
Same in 2021.3.17 LTS
-
justacanuk81
Jan 10, 2023 18:11
I am getting this error in trying to complete the tutorials.
-
duc_unity577
Dec 20, 2022 12:52
We are having this issue in Unity 2021.3.9f1, but the problem seems to come from Unity itself and not the .mp4 file.
Our video has correct color standard:
```
color_range=pc
color_space=bt709
color_transfer=bt709
color_primaries=bt709
```But when we check `Transcode` in the import settings, this warning is printed again.
When we uncheck `Transcode`, the warning is gone but another warning show up about we're not transcoding our video.
-
mylastggeast
Nov 28, 2022 03:44
When is this fix coming to 2021 LTS?
-
cory-trese
Sep 22, 2022 12:55
When is this fix coming to 2021 LTS?
-
AzaiKang
Aug 24, 2022 00:32
Edit to my comment below: I am using Unity 2022.1.9f1 <DX11>
-
AzaiKang
Aug 24, 2022 00:30
I've found a solution using a .mp4 H264 Video File.
1. Open Unity, click the Video Clip and open its Import Settings.
2. While in the Import Settings, you go change its Codec format from Auto into VP8.
3. The "WindowsVideoMedia error unhandled Color Standard: 0 falling back to default this may result in rendering issues" warning is gone after that. Hope it works for everyone. -
wahntin
Jul 22, 2022 09:49
Ignore my last comment: Re-encoding it the way mentioned in the resolution note does not fix the problem for Unity 2021.3.6f1.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Standalone Player crashes with "TDerived GetOrLoad<TDerived>() where TDerived : T" when IL2CPP Code generation is set to "Faster (smaller) Builds"
- IndexOutOfRangeException and InvalidOperationException when logging XML string
- Script missing in "Assets/Settings/Mobile_Renderer/GlobalVolumeFeature" of "com.unity.template.urp-blank" template
- “Font Asset Creator - Error Code [Invalid_File_Structure]…“ error is logged when generating Font Assets from fonts with meta files from previous Editor versions
- Input.mousePosition returns (NaN, NaN, 0.00) when Scene view is opened
Resolution Note (fix version 2022.1):
Fixed in 2022.2.0a1
Every file had an unknown color standard. To remove the warning, you should check how to add the color standard in the file while editing or recording. You can use FFmpeg to add it, but you have to reencode your file, lowering the quality. Use and customize this command for your need.
ffmpeg -i input.mp4 -color_primaries bt709 -color_trc bt709 -colorspace bt709 -color_range pc -vcodec libx264 output.mp4
We reduced redundant warnings, so you should see only one per file.