Search Issue Tracker
Won't Fix
Votes
1
Found in
2021.3.32f1
2022.3.13f1
2023.1.19f1
2023.2.0b17
2023.3.0a13
Issue ID
UUM-55489
Regression
No
“VideoClip import error” is thrown when importing a VP8 video
How to reproduce:
1. Create a new project using any template
2. Import the “CubicTransitionVideoVP8” video into the project
3. Observe the Console
Expected result: No errors are thrown
Actual result: “VideoClip import error” is thrown
Reproduced with: 2021.3.32f1, 2022.3.13f1, 2023.1.19f1, 2023.2.0b17, 2023.3.0a13
Reproduced on: Windows 10 (by reporter), Windows 11
Not reproducible on: No other environment tested
Note: Not reproducible with other VP8 encoded videos → Additional information in internal comments
Full error log:
VideoClip import error for Assets/Scenes/CubicTransitionVideoVP8.webm
UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&)
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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Resolution Note:
Hi,
In response to your message about the recently closed bug, I would like to explain a bit without getting into too many technicalities. Solutions to bugs in our system are tackled based on a combination of factors. These include the severity of the issue, the impact it has on our users, and the complexity involved in fixing it. Every issue reported is thoroughly evaluated, with the significant ones getting the topmost priority.
The particular bug you referred to was reviewed and, given it is not causing a high level of disruption for users, it has been categorized as a lower priority at this time.
This decision is not an indefinite one, and it doesn't mean the bug will never be fixed. It's simply a reflection of our current resources and priority plans. We take your feedback seriously and will revisit these issues as we continue to enhance our product.
We appreciate your understanding and thank you once again for helping to improve our services. Please feel free to reach out if you have any other questions or concerns.
Thank you