Search Issue Tracker
Third Party Issue
Votes
1
Found in
2021.3.34f1
2022.3.17f1
2023.2.4f1
2023.3.0b1
6000.0.0b11
Issue ID
UUM-59771
Regression
No
Video freezes and LoopPointReached is called twice after the first loop of Video Clip playback
Reproduction steps:
1. Open the attached “CommonTest“ project
2. Open the “Assets/Scenes/SampleScene.unity“ Scene
3. Enter the Play Mode and wait 10 seconds
4. Observe the Console
Expected result: LoopPointReached error is logged once and the video keeps playing
Actual result: LoopPointReached error is logged twice and the video freezes
Reproducible with: 2021.3.34f1, 2022.3.17f1, 2023.2.4f1, 2023.3.0b1
Reproducible on: Windows 10 (22H2)
Not reproducible on: No other environment tested
Note: Using 2021.3.34f1 and 2023.2.4f1 video didn’t freeze, but 2 errors were still logged
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
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
- Persistent Memory Leak when reloading domain and using Distance-based Ghost Importance
- HDRP project doesn't render in standalone player when using High stripping
Resolution Note:
Microsoft's Media Foundation has a mp4 file source implementation that doesn't support well the distinction between presentation and decode timestamps. When H.264 video content is encoded with so-called B-Frames - present in Main and High profiles - this requires some of the later frames in the stream to be decoded earlier (leading to out-of-order layout in the file). The resulting timestamp offsets and their impact on track duration is incorrectly reported in the API, causing internal issues in end-detection and looping implementation.
We do have some countermeasures to work around these issues, but when they persist, the best approach is to encode with the Baseline H.264 profile, which doesn't use B-Frames. The consequence is that the video will be less compact but also has the advantage of taking less computing resources for decoding.