Merge pull request #111767 from FlorianBorn71/VideoRecordingAndVideoBandwidth

Additions to video recording and video downstream bandwidth

Author: PRMerger6

articles/remote-rendering/reference/network-requirements.md

@@ -23,6 +23,9 @@ The exact network requirements depend on your specific use case, such as the num
 * Having **good Wi-Fi signal strength** is essential. If possible, stay close to your Wi-Fi access point and avoid obstacles between your client device and the access points.
 * Make sure that you always connect to the **nearest Azure data center** for your [region](regions.md). The closer the data center, the lower the network latency, which has a huge effect on hologram stability.
 
+> [!NOTE]
+> The downstream bandwidth is mostly consumed by the video stream, which in turn is split between color- and depth information (both 60 Hz, stereo).
+
 ## Network performance tests
 
 If you want to get an initial understanding of whether the quality of your network connectivity is sufficient to run Azure Remote Rendering, there are existing online tools that you can use. We strongly recommend running these online tools from a reasonably powerful laptop connected to the same Wi-Fi as the device that you are planning to run your Azure Remote Rendering client application on. Results obtained from running the tests on a mobile phone or HoloLens2 are usually less useful, as they have proven to show significant variation on low-powered endpoint devices. The location at which you place the laptop should be roughly at the same place at which you expect to use the device that runs your Azure Remote Rendering client application.
@@ -34,7 +37,7 @@ Pick a server closest to you and run the test. While the server will not be the
    * **Minimum requirement** for Azure Remote Rendering: Approx. 40 Mbps downstream and 5 Mbps upstream.
    * **Recommended** for Azure Remote Rendering: Approx. 100 Mbps downstream and 10 Mbps upstream.
 We recommend running the test multiple times and taking the worst results.
-1. **Use a tool like www.azurespeed.com that measures latency to Azure data centers**. Select the Azure data center supported by Azure Remote Rendering that is closest to you (see [supported regions](regions.md))and run a **latency test**. If there is variation in the numbers you see, give the results some time to stabilize.
+1. **Use a tool like www.azurespeed.com that measures latency to Azure data centers**. Select the Azure data center supported by Azure Remote Rendering that is closest to you (see [supported regions](regions.md)) and run a **latency test**. If there is variation in the numbers you see, give the results some time to stabilize.
    * **Minimum requirement** for Azure Remote Rendering: Latency should consistently be less than 100 ms.
    * **Recommended** for Azure Remote Rendering: Latency should consistently be less than 70 ms.
 

articles/remote-rendering/resources/troubleshoot.md

@@ -33,7 +33,7 @@ There are two reasons why the server might refuse to connect with a **codec not
 
 First make sure to install the **HEVC Video Extensions** as mentioned in the [Software](../overview/system-requirements.md#software) section of the system requirements.
 
-If you still encounter problems, please make sure that your graphics card supports H265 and you have the latest graphics driver installed. See the [Development PC](../overview/system-requirements.md#development-pc) section of the system requirements for vendor specific information.
+If you still encounter problems, make sure that your graphics card supports H265 and you have the latest graphics driver installed. See the [Development PC](../overview/system-requirements.md#development-pc) section of the system requirements for vendor-specific information.
 
 **The codec is installed, but can't be used:**
 
@@ -72,6 +72,14 @@ The video quality can be compromised either by network quality or the missing H2
 * See the steps to [identify network problems](#unstable-holograms).
 * See the [system requirements](../overview/system-requirements.md#development-pc) for installing the latest graphics driver.
 
+## Video recorded with MRC does not reflect the quality of the live experience
+
+A video can be recorded on Hololens through [Mixed Reality Capture (MRC)](https://docs.microsoft.com/windows/mixed-reality/mixed-reality-capture-for-developers). However the resulting video has worse quality than the live experience for two reasons:
+* The video framerate is capped at 30 Hz as opposed to 60 Hz.
+* The video images do not go through the [late stage reprojection](../overview/features/late-stage-reprojection.md) processing step, so the video appears to be choppier.
+
+Both are inherent limitations of the recording technique.
+
 ## Black screen after successful model loading
 
 If you are connected to the rendering runtime and loaded a model successfully, but only see a black screen afterwards, then this can have a few distinct causes.