Kieshi
Not sure if this is known but there is an issue with remote control api which I think was introduced in 14.4.
The remote api server uses VideoPlayer.CurrentTimeAsync
to send current video time which has flawed logic. While video is paused the value will fluctuate because CurrentTimeAsync
adds CurrentAppTime - lastCurrentTimeUpdate
to the actual current video time. lastCurrentTimeUpdate
is updated on each frame in Update()
but if the remote api server reads CurrentTimeAsync
between frames the value will not be stable.
Sample values with video paused:
754.977
754.977356
754.981445
754.981934
754.9834
754.9844
754.9772
This also has another issue on some headsets. If the device stops rendering, Update()
will not be called and VideoPlayer.CurrentTimeAsync
will grow infinitely even when paused.