Search Issue Tracker
Fixed
Fixed in 2021.3.30f1, 2022.3.7f1, 2023.1.7f1, 2023.2.0b3, 2023.3.0a1, 7000.0.0a1
Votes
1
Found in
2021.3.14f1
2022.2.0f1
2023.1.0a20
2023.2.0a1
7000.0.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
- A memory leak occurs with massive terrain when camera position changes occur.
- No valid hits are returned when using RaycastCommand
- Camera is not overlooking the main Scene in Scene View in the HDRP Sample Template
- TextShadow properties are not applied when displayed in a custom MenuItem Window
- Memory leak occurs when focused on Player while using Direct3D12
Resolution Note (fix version 2023.3.0a1):
Improve VP8 encoder compression and encoding speed