Search Issue Tracker
Fixed in 2021.3.30f1
Fixed in 2021.3.X, 2022.3.X, 2023.1.X, 2023.2.X, 2023.3.X, 7000.0.0a1, future release
Votes
1
Found in
2021.3.14f1
2022.2.0f1
2023.1.0a20
2023.2.0a1
Issue ID
UUM-20744
Regression
Yes
The Video Import Size is too big when using VP8 Codec
Reproduction steps:
- Open the attached project “VP8Bug“
- Select the video file “Assets/video_vp8“
- In the Inspector window navigate to the preview pane
- Click on the video name and select the option “Source Info”
- Compare the Original Size to the Imported Size
Expected results: The Original Size is bigger than the Imported Size
Actual results: The Imported Size is thrice as big as the Original Size
Reproducible with: 2021.2.0a21, 2021.2.19f1, 2021.3.14f1, 2022.1.23f1, 2022.2.0f1, 2023.1.0a20
Not reproducible with: 2020.3.42f1, 2021.2.0a20
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
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Active Targets section text in Graph Inspector is truncated despite available space
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
- Shader Graph Node information is briefly displayed in Graph Inspector when clicking on Category in the Blackboard
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
Resolution Note (fix version 2023.3):
Improve VP8 encoder compression and encoding speed