videos prematurely going to next video..

MainFragger

I will be watching a video, and it will suddenly go to the next video for no reason. Also, even if I pause a video, after a few seconds, it will proceed to the next video. I have tried exiting and coming back into the app,, rebooting my headset, but that has not resolved it.

Lucy

MainFragger
Hi, do you play videos in AirScreen channel? Please share with us(contact@skybox.xyz) your log files to troubleshoot. If you're using Quest 1 or Quest 2, you need to connect your Quest to PC through a cable, zip and send us the log files in Quest 2\Android\data\xyz.skybox.player.ovr\files\Log.

Mickael

I got same similar issue (i think what i will describe is the root cause of Lucy's bug)
When you play a 5s video file, no matter what you do:

pause immediately,
use mark A/ B
check loop on unique file

After 5s skybox jump to next files.
It seems the timer of skybox (== video length) never stops no matter what feature we use.
it's pretty annoying,

Lucy

Mickael Ted Hi, please tell us(contact@skybox.xyz) your Oculus registered email. We'd like to add you to our Quest beta channel and offer you a fix version. You can test whether the problem is resolved in the beta channel.

Ted

I have similar experience occasionally. And they always came with laggy WiFi connection here.

Ted

Once I have this situation, I disconnected and reconnected the WiFi connection. This trick always works. But I haven't found any WiFi channel confliction when the network was laggy. Actually I can't say what happened.
BTW, 2.4G can cause laggy then cause this issue in my scenario. So I alwayin use 5G WiFi for video streaming. I presumed that SKYBOX should have detected interrupted streaming and try playing next video file. Maybe it's just the way of SKYBOX and has it's perks.

Lucy

Ted Hi, network packet loss may cause the app skipping to the next video randomly. We addressed this issue in the beta channel. You can tell us your Oculus register email and try out the beta version.

MainFragger

HI, sorry I fell away from this discussion. I can at least confirm that I haven't had this issue for a while. So some previous update seems to have resolved the issue.