Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2019.4.X, 2020.3.X
Votes
1
Found in
2018.4
2019.4
2019.4.8f1
2020.1
2020.2
2021.1
Issue ID
1297648
Regression
No
Video starts playing from an arbitrary frame when VideoPlayer.Pause is called before VideoPlayer.Play
Reproduction steps:
1. Download and open the attached project "case_1283295-VideoPlayer_Bug_Report.zip"
2. Open "Video Scene"
3. Enter Play mode
4. Press "Prepare"
5. Press "Pause"
6. Press "Play"
Expected result: The video starts playing from frame 0
Actual result: The video starts playing from an arbitrary frame
Reproducible with: 2018.4.30f1, 2019.4.17f1, 2020.1.17f1, 2020.2.0f1, 2021.1.0a10
Notes:
The issue is only reproducible when internalTime time reference is used.
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note (fix version 2021.1):
When using the internal time reference, the state transition from prepared to paused to playing had a missing internal timestamp initialization, causing the VideoPlayer to jump ahead.
Resolution Note (fix version 2019.4):
Fixed in 2019.4.25f1