Search Issue Tracker
Third Party Issue
Votes
0
Found in
2020.3.45f1
2021.3.18f1
2022.2.6f1
2023.1.0b3
2023.2.0a3
Issue ID
UUM-27915
Regression
No
WindowsVideoMedia error is thrown when importing a WebM file
Reproduction steps:
1. Open the attached project “VideoImportBug“
2. Reimport video file “Assets/Horse_Slow_V3”
3. Observe the Console Window
Expected result: Video file “Slow_Horse_V8” is successfully imported
Actual result: “0xc00d36b4“ error is logged in the Console Window
Reproducible with: 2020.3.45f1, 2021.3.18f1, 2022.2.6f1, 2023.1.0b3, 2023.2.0a3
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
- Polygons are created on the opposite side of the Sprite when the Sprite boundaries are above the edge of the Texture
- Render Graph Viewer Resource list becomes shrunk after using a filter that yields no results
- [Android] [Vulkan] "VK_IMAGE_USAGE_TRANSIENT_ATTACHMENT_BIT" not added on some Android devices in "com.unity3d.player.UnityPlayerActivity/2D Colour Attachement"
- ResolveUsePasses now extracts passes from all subshaders including fallbacks, in contrast to documented behaviour
- [UIBuilder] Changes aren't detected on types implementing IList
Resolution Note:
The Microsoft Media Foundation encoder for H.264, which we are using in our importer, has a limit of 4096x4096. The source webm clip being used has a resolution of 5000x2812. Because it contains transparency, the resulting stored resolution for H.264 ends up being 10000x2812. Using webm directly, or using a lower resolution of this clip are two alternative that would have to be tried.