Search Issue Tracker

Fixed in Unity 2017.1.0f3

Votes

26

Found in

5.6.0b9

Issue ID

889059

Regression

No

Setting VideoPlayer.frame from code offsets audio

Video

-

-

Priority: 2Necessary for shipping a final release

-

Severity: 3Secondary functionality broken

How to reproduce:
1. Open attached project
2. Enter playmode
3. Click 'Setup'
4. When the video is playing press W to advance 200 frames forward and S to go back 200 frames
5. Notice the video is desynced from audio

Expected result: Audio and video are still synced after setting new videoPlayer.frame
Actual result: Audio gets offset/desynced

Reproduced with: 5.6.0b5, 5.6.0b9, 5.6.0b11, 2017.1.0a3
Note: Video froze instead of changing frame on 5.6.0b1 and b3

Fixed in: 2017.3.0b1
Backported to: 2017.1.1p4, 2017.2.0f2

Comments (6)

  1. E642faf62b932a59095d030de1b33dda?d=mm

    highlyinteractive

    Nov 05, 2018 10:24

    Issue still persists in 2018.2.14f1

  2. 17b24182953467b7a393d662a79abec4?d=mm

    boehmzViacommix

    Mar 15, 2018 01:02

    I am also having the same issue as JOSHMCCREADY. I can tell it is new because if I set a video to pause and go to a specific hard coded time, it will show a different in frame in 2017.3 than 5.6. I am currently unable to upload a bug report for some reason (I keep getting server timeout and the bug reporter freezes). Has anyone been able to submit a bug report for this issue/am I able to upload a bug report in a different way? I have a small sample project that illustrates this problem easily.

  3. Ac7847bdea877295ed503c4ac26546ef?d=mm

    joshmccready

    Mar 01, 2018 00:26

    I'm having an issue that it think is related. Ive been testing the seek function on a frame indexed video and have noticed that both the frame number and frame time become incorrect by one frame after a fixed number of frames. That number of frames stays constant for a given video (was 6005 frames on the video i was looking at) seeking below that number returned the correct frame, seeking above that number returned the frame I wanted +1. by seeking it was impossible to get to frame # 6006. I could however get to this frame if i were to seek to frame 6005 and then call StepForward(). If 6006 were a magic number i could work around this problem but unfortunately this number is different for different videos. Maybe somehow dependent on the bitrate? Something is wrong with how unity is calculating time when it does a seek. Its not fixed in 2017.3.1f1 but am hoping it can be soon.

  4. 7540d4517034d36f5b8d202d3fd87631?d=mm

    Knusper

    Jul 18, 2017 15:56

    I'd like to know why severity is set to "3: workaround is possible". If there is any workaround, where is it?

  5. D514dd6b7bcea73e7368e6cd77c81e74?d=mm

    roumenf

    Jun 21, 2017 11:54

    The same applies to setting VideoPlayer.time. As play, pause and seek are the three major video-player related actions, this issue is urgent and critical.

  6. 7540d4517034d36f5b8d202d3fd87631?d=mm

    Knusper

    Jun 14, 2017 15:27

    This issue persists in 2017.1.0b9. Same behaviour appears when you use "videoPlayer.time" instead of ".frame"

All about bugs

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