Search Issue Tracker
By Design
Votes
0
Found in
2018.4
2018.4.32f1
2019.4
2020.2
2021.1
2021.2
Issue ID
1316857
Regression
No
VideoPlayer.StepForward() does not VideoPlayer.OnFrameReady when using a non-transcoded video
Reproduction steps:
1. Download and open the submitted project "VideoPlayer_Bug_Report.zip"
2. Open the Video Scene
3. Enter the Play mode
4. Press Video: Non-Transcoded
5. Press Prepare
6. Press StepForward 3 times
Expected result: VideoPlayer.OnFrameReady is logged for every new frame
Actual result: VideoPlayer.OnFrameReady is only logged on the third StepForward
Reproducible with: 2018.4.32f1, 2019.4.21f1, 2020.2.6f1, 2021.1.0b8, 2021.2.0a6
Notes:
On Unity 2018.4 VideoPlayer.OnFrameReady is called on the second StepForward instead of third
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
The Windows version of the VideoPlayer already emits a message explaining the desynchronization that happens because the video track does not start exactly at 0.