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
- ”Last item reached” warning is thrown when no search results are found in UI Toolkit Layout Debugger
- UI Elements overlap in the Shortcuts window when docked and resized to a smaller window size
- UIBuilder DataSourcePath dropdown fails to show properties when binding to abstract classes
- Errors are logged when importing an asset at a path with Firebase
- Entering too big of a number in 2D Renderer Lightmode Tags freezes the Editor
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.