W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2017

New 120Hz iPad with Variable Refresh Rate: Standardizing in HTML

From: Mark Rejhon <mark@blurbusters.com>
Date: Tue, 6 Jun 2017 17:30:19 -0400
Message-ID: <CANDAP16=E3wFgTSkh+5x2LYC=tMavE3NTSLM9HiTDrvWpCXvrg@mail.gmail.com>
To: Mark Rejhon <mark@blurbusters.com>
Cc: "public-webapps@w3.org" <public-webapps@w3.org>
Yesterday, Apple announced 120Hz and variable refresh rate support on
iPads, permitting true 24fps @ 24Hz as well as 48fps @ 48Hz for smooth
video playback.

As a result, the priority of adding variable refresh rate support to HTML
5.2 has dramatically jumped upwards in priority. Even the WebKit people are
beginning to ask me questions.

I have completely rewritten the description of Issue #375 at W3C:
https://github.com/w3c/html/issues/375

I have a proposal written in these two new comments:
PHASE 1: https://github.com/w3c/html/issues/375#issuecomment-306591154
PHASE 2: https://github.com/w3c/html/issues/375#issuecomment-306603305
I would like your comments before writing this into the HTML 5.2 standard;

Sincerely,
Mark Rejhon
Invited Expert, Variable Refresh Rates / 120Hz+


On Sat, Apr 29, 2017 at 4:34 PM, Mark Rejhon <mark@blurbusters.com> wrote:

> Thank you!
>
> As a display researcher with already a peer-reviewed conference paper and
> prior industry-standard writing experience --
>
> I'll be focussing on the sphere of display update rate standardizations
> (canvas, WebGL, etc)
>
> -- upcoming variable refresh rate displays (e.g. VESA Adaptive-Sync, HDMI
> 2.1 VRR, G-SYNC, FreeSync)
> -- compatibility with high-refresh rate displays used in the now
> billion-dollar eSports gaming industry (144Hz, 240Hz, etc)
> -- ultra low latency issues (e.g. browser compositing and desktop manager
> compositing in the same refresh cycle)
> -- VSYNC API's such as VSYNC OFF (1000fps+) for specialized low-latency
> applications.
>
> (As an aside -- it is noteworthy more than 80% of eSports competition
> players use VSYNC OFF operation for low latency purposes in the
> Olympics-race-tight milliseconds times they care about. It's already
> implemented in some browsers: Chrome already supports this as a command
> line option, but is not exposed as a JavaScript-controllable feature yet).
>
> Current outstanding github issues include github
> github.com/w3c/html/issues/375 (1 commit pending) and
> github.com/w3c/html/issues/785
>
> Cheers,
> Mark Rejhon
> Blur Busters/TestUFO
>
>
> On Sat, Apr 29, 2017 at 1:19 PM, <chaals@yandex-team.ru> wrote:
>
>> Welcome both of you - thank you for the contributions you have already
>> made, and I look forward to your continued participation.
>>
>> cheers
>>
>> 29.04.2017, 12:20, "Léonie Watson" <tink@tink.uk>:
>> > Welcome to Mark Rejhon and David MacDonald, who have joined WebPlat as
>> > Invited Experts (IE).
>> >
>> > Léonie
>> > --
>> > @LeonieWatson tink.uk Carpe diem
>>
>> --
>> Charles McCathie Nevile - standards - Yandex
>> chaals@yandex-team.ru - - - Find more at http://yandex.com
>>
>>
>
Received on Tuesday, 6 June 2017 21:31:14 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:27:42 UTC