Search Issue Tracker
Won't Fix
Won't Fix in 2023.1.X
Votes
0
Found in
2020.3.44f1
2021.3.17f1
2022.2.3f1
2023.1.0b1
Issue ID
UUM-26004
Regression
No
Error "0xc00d36e6" is thrown when importing a video file encoded with the 58.76.100 encoder
Reproduction steps:
1. Open the attached project “ImportBug“
2. Go to the Assets folder
3. Reimport the video file “problematicFile”
4. Observe the Console Window
Expected result: The video file is successfully imported
Actual result: Error “0xc00d36e6” is thrown in the Console Window
Reproducible with: 2020.3.44f1, 2021.3.17f1, 2022.2.3f1, 2023.1.0b1
Reproducible on: Windows 11
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Microsoft's Media Foundation WMV reader is not properly getting the frame rate from the file, resulting in duration and seek operations to have undefined behaviour. Not all WMV files have this problem so next steps, if this becomes a frequent occurrence, would be to submit a bug to Microsoft's Media team.
Resolution Note (2023.1.X):
Microsoft's Media Foundation WMV reader is not properly getting the frame rate from the file, resulting in duration and seek operations to have undefined behaviour. Not all WMV files have this problem so next steps, if this becomes a frequent occurrence, would be to submit a bug to Microsoft's Media team.