Search Issue Tracker
Not Reproducible
Votes
0
Found in
2020.3.35f1
2021.3.3f1
2022.1.3f1
2022.2.0a13
Issue ID
UUM-3215
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
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
- "HideFlags.HideAndDontSave" flag does not work when the Components are added in OnEnable and Awake methods
- Graph VFX not compiling enterely until they are open on MACOS
- Longer component titles exceed the window's display boundaries
- Overlapping objects do not collide when setting Physics.IgnoreCollision to false
- Crash on RaiseException when deleting animation transitions in a specific Animation Controller
Resolution Note:
This only occurs in a version that reached end of life (2021.3)
Cannot repro with 2022 versions.