Video glitches on Quest 2 after updating to Oculus OS v53

[Gurwar]

Problem description:

When playing 8k 360 video inside the quest, there are noticable glitches and artifacts within the video stream. The glitches also occur with 5K video but not as much.

Device (which devices are you having the issue with - model, OS version number):

Quest 2

Media (tell us about your videos - number of videos, resolution, codec, frame-rate, example URLs):

Multiple Videos, 8K/5K Resolution,

System Information:

AVPro Video: v2.6.6 (plugin v2.6.3f1-ultra) Target Platform: Android Unity: v2021.3.16f1 WindowsEditor OS: Desktop - B550M DS3H AC (Gigabyte Technology Co., Ltd.) - Windows 11 (10.0.22621) 64bit - English CPU: AMD Ryzen 5 5600X 6-Core Processor - 12 threads - 32691KB GPU: NVIDIA GeForce RTX 3080 - NVIDIA - Direct3D 11.0 [level 11.1] - 10067KB - 16384

[RealMoonSt]

I've update to PTC v57, and unfortunately there is no improvement in the issue. Also I tested the fix that Headjack had implemented on their software, and unfortunately that did not eliminate the artifact issue for me on their app build, only reduced it.

The only true elimination of the issue I have found so far is the DeoVR app and whatever Unity/AVPro/Exoplayer implementation they have done which inadvertently fixes the issue.

Given that this has been going on for close to 5-6 months now (estimated to have first started in March), and there is currently the equivalent of a forum riot going on in the official Meta thread over this issue, and Meta is not addressing it for some strange reason... I was wondering if Renderheads should take a position on the fact that the AVPro Video software is currently not an acceptable and implementable solution for Quest 2/Pro for high-quailty VR Immersive video, given the now prolonged timescales?

I do appreciate that we are all in this together, and I will continue to push for a solution from Meta while I look for other overall solutions for my business.

[Ste-RH]

Regarding previous versions of AVPro Video. If you send over your Unity pdf invoice to unitysupport@renderheads.com we will happily provide any pervious version asset packages you have a license for and desire.

[RealMoonSt]

Thanks @Ste-RH , currently DeoVR have said they use AVPro 2.7.3 , so that's the one we'd like to try in non-trial mode and I'll send over an email for that as you suggest, cheers

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[RealMoonSt]

Just to keep this thread from going properly stale, I have not been able to determine any benefit from using the same AV Pro plugins and Unity versions as the DeoVR media player app, which continues to be unaffected by the pixel artifact issue. Unfortunately the issue remains and Meta have not provided a fix on v57.

Also I have been testing our same h.265 vr180 file with other VR media player apps on Quest 2, such as Pigasus VR and Skybox VR, and in both cases our file playback with no issues. I do not know if Pigasus uses AVPro or Exoplayer, but I believe Skybox has their own implementation. Also the Meta TV player on Quest 2 is unaffected with the same file. However I have encountered the problem still with the latest Headjack, despite an update they put out claiming it was fixed, who also use AVPro. Therefore the issue seems most common (for VR Video playback) with the AVPro Video Plugin... with the one exception being DeoVR who have done something unknown to circumvent it.

Despite engaging with Meta on the forums, the headjack team and the developers of Virtual Desktop (which is also still affected) nobody has been able to identify a root cause... and therefore identifying what change DeoVR have implemented is very difficult. Also there is no indication from the Oculus Debug Overlay tool what DeoVR might be doing differently other than their app is using twice as much memory during playback as our AVPro Video built app (VSS/RSS/PSS/USS etc).

[Chris-RH]

I've been following the threads on Meta. It seems that users are also seeing this in Prime Video, Youtube, various games, and even in the home screen, so it doesn't seem specific to Exoplayer/AVPro Video. It appears to be related to the headset GPU being pushed too hard. I'm not sure that there is anything further we can do about it. Just keep poking at meta on their forum to fix it, please :)