Video pixelated even when using foveated scaling

fxmdeveloper · June 8, 2021, 3:25pm

Hi,
We’ve been testing CloudXR in AWS service for a while now, and we realized that it wasn’t performing to our expectation, especially on our Quest & Quest2 devices…

These are our experiences of using CloudXR on two different setups:

Using a Wifi connection with around 50Mbps of download speed
- No problem when streaming content into Vive Pro
- Video is very pixelated when running on Quest2 device, even when using the “-f 25” option. Slightly better when using the “-f 50” option when standstill. However, when we start moving or turns around, the results are similar, very pixelated.
Using a Wifi connection with over 200Mbps of download speed

Similar or even worse result when running on Oculus Quest 2 and the result are similar even when we use foveated scaling option. Almost half of the HMD display is black when we turn around quickly.
It also pixelated when run on Oneplus 7 + ARCore.

Here is the QoS log of the second case when running on Quest2.
Streamer Server Log 2021-06-08 02.56.24.txt (639.0 KB)
CloudXR Client Log 2021-06-08 11.13.51.txt (10.1 KB)
CloudXR Client QoS Log 2021-06-08 11.13.51.csv (3.7 KB)
Streamer Client Log 2021-06-08 11.13.51.txt (222.8 KB)

Veronica_NVIDIA · July 21, 2021, 8:32pm

Hi @fxmdeveloper -

Can you please replicate your experience with the latest CloudXR 3.0 release? This release is now available via the CloudXR DevZone.

Thanks!

Veronica

tegradave · July 23, 2021, 6:37pm

Yes, I’d like to see results with 3.0.

From the QOS log, your jitter is EXTREMELY HIGH for most of the run (we’re used to say <200, your values are in multiple thousands, so 10-50x off), and estimated bw drops very low. And this is just a few seconds.

From the server log, we see something like this:
#5(I)[2021-06-08 03:01:02,475]=03:01:02={3124}<NvscStreamingSes> Sent QoS info: stream: 0, client Q-score 67, RTD 51, scores(25, 100, 82)
The score numbers are: (bandwidth, packet loss, latency). There are long spans of low bw scores, indicating a problem potentially with the network.

There was a fix in 3.0 for a specific corner-case which would cause the bandwidth to not go up, which is why we’d like to see this replicated in 3.0. If it still does the same thing, it comes down to the wifi network quality.