Search Issue Tracker
Active
Votes
0
Found in
2019.4
2020.3
2020.3.9f1
2021.1
2021.2
2022.1
Issue ID
1340568
Regression
No
[macOS] VideoPlayer.clockTime is ~0.5 of a frame's length smaller after setting VideoPlayer.time to a specific value
Reproduction steps:
1. Open the attached project "unity-video-tests" and load Scene "SampleScene"
2. Open "Scripts/Seeking.cs" and comment out "#define AVPLAYER" in line 2
3. Enter Play Mode
4. Click the "Download Video" Button at the top of the Game View
5. Click the "Prepare Video" Button at the top of the Game View
6. Click the "Seek" Button at the top of the Game View
7. Observe the time value in the top left and the clockTime value (named "Time") in the middle bottom of the Game View
Expected result: setting VideoPlayer.time to a specific value results in VideoPlayer.clockTime changing to that value
Actual result: setting VideoPlayer.time to a specific value results in VideoPlayer.clockTime being ~0.5 of a frame's duration smaller than VideoPlayer.time
Reproducible with: 2019.4.29f1, 2020.3.14f1, 2021.1.15f1, 2021.2.0b3, 2022.1.0a1
Could not test with: 2018.4.36f1 (Project's UI breaks)
Notes:
- Reproducible with macOS
- Not reproducible with Windows
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- URP Realtime reflection probes do not update when RenderProbe() is being called once per second
- Addressable terrain shader variants are stripped from the Player
- [iOS] Debug.Log() appears as <private> in Console app
- UI stays in the background when it is disabled in simulator
- A wrong log file is attached when project is launched with a "-logFile" command line argument
Add comment