Search Issue Tracker

By Design

Votes

0

Found in

2018.2.0b6

Issue ID

1045876

Regression

Yes

[VideoPlayer][Android] Playing video when WaitForFirstFrame is disabled takes video to start 1.5s longer than when it is enabled

Video

-

How to reproduce:
1. Open the attached project
2. Switch platform to Android
3. Build and run Far Plane and Near Plane scenes on Android dveice. Far plane has WaitForFirstFrame disabled, Near Plane has WaitForFirstFrame enabled
4. First scene is Far Plane scene. Click Play button, which will play the video
Result: One can notice that slider which shows time jumps back after around 50ms and video starts playing after ~1.5 seconds
5. Press Next Scene button it will switch to Near Plane scene
6. Click Play button, which will play the video
Result: Video starts playing very fast

Notes: Reproducible with both webm and mp4 videos

Reproducible: 2018.3.0a1, 2018.2.0b6, 2018.1.4f1, 2017.4.4f1, 2017.2.3p1
Not reproducible: 2017.1.3p3

Tested and reproduced on:
Google Pixel 2 XL Adreno 540 OS 8.1.0 1440x2880
Samsung Galaxy S8 Mali-G71 OS 7.0 1440x2960
Xiaomi Mi 4i Adreno (TM) 405 OS 5.0.2 1080x1920
Meizu MX5* PowerVR Rogue G6200 OS 5.0.1 1080x1920

Tested and didn't reproduce on:
Mackbook Pro OSX 10.13.4
iPad Pro 10.5'' iOS 10.3.3

BY DESIGN: Video playback preparation is now fully asynchronous but as a result, time updates start immediately and Android platforms are often incapable of "chasing" this time update. The consequence is that WaitForFirstFrame is now much more important to use. Otherwise, the video player skips ahead (without showing images) until it can catch up with time. In the clip used for the Near Plane scene (H264_SD_144p.mp4), 1.5s corresponds to the location of the first keyframe in the video. This is the expected place where an Android device will be able to skip-ahead at low cost.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.