Skip to content

Commit fce0bdc

Browse files
committed
Clarify Game streaming requirements (section 3.2)
Fixes w3c#103
1 parent b1e964c commit fce0bdc

File tree

1 file changed

+9
-5
lines changed

1 file changed

+9
-5
lines changed

index.html

Lines changed: 9 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -278,19 +278,23 @@ <h4>Game streaming</h4>
278278
<tr>
279279
<td>N15</td>
280280
<td>The application must be able to take steps to ensure a low and consistent
281-
latency for audio, video and data under varying network conditions. This may
282-
include tweaking of transport parameters for both media and data.</td>
281+
latency for audio, video and data under varying network conditions. This may
282+
include tweaking of transport parameters for both media and data.</td>
283283
</tr>
284284
<tr>
285285
<td>N37</td>
286286
<td>It must be possible for the user agent's receive pipeline to process
287-
video at high resolution and framerate (e.g. without copying raw video
288-
frames).</td>
287+
video at high resolution and framerate (e.g. without copying raw video
288+
frames).
289+
To be specific, 120FPS, 165 FPS, 240FPS are all supported by cloud gaming and desirable to bring to browser too.
290+
Higher Resolution support up to 4K and High Dynamic Range(HDR) are also desiable for the support.</td>
289291
</tr>
290292
<tr>
291293
<td>N38</td>
292294
<td>The application must be able to control the jitter buffer and rendering
293-
delay.</td>
295+
delay. To be specific to the Cloud Gaming Application, Maintaing the steady latency within a range
296+
is critical for player adaptation. Good latency ranges are between 30ms - 150ms.
297+
Beyond 170ms is detrimental to user experience. </td>
294298
</tr>
295299
</tbody>
296300
</table>

0 commit comments

Comments
 (0)