Search Issue Tracker
Duplicate
Votes
0
Found in
2018.4
2019.4
2020.2
2021.1
2021.2
2021.2.0a6
Issue ID
1316931
Regression
No
Video Player displays a wrong frame when changing VideoPlayer.frame using a non-transcoded video
Reproduction steps:
1. Download and open the attached project "VideoPlayer_Bug_Report.zip"
2. Open the Video scene
3. Enter Play mode
4. Press Video Non-Transcoded
5. Press Prepare
6. Press Play
7. Press Pause
8. Press Seek to frame 100
Expected result: OnFrameReady is logged for frame 100 and 100 is displayed in the Game view
Actual result: OnFrameReady is logged for frame 99 and 97 is displayed in the Game view
Reproducible with: 2018.4.32f1, 2019.4.21f1, 2020.2.6f1, 2021.1.0b8, 2021.2.0a6
-
Resolution Note:
This results from the H.264 video track having b-frames, which hits a Microsoft H.264 decoder bug. The mitigation is to issue an informational message about why this is happening. Transcoding to H.264 using the base profile instead of the (main profile, like here) fixes the issue. The transcoding can be done either in the Unity video clip importer or outside of Unity.
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
This is a duplicate of issue #1316857