W3C home > Mailing lists > Public > public-web-and-tv@w3.org > February 2011

HTML5 and frame accuracy

From: Dirk-Willem van Gulik <Dirk-willem.Van.gulik@bbc.co.uk>
Date: Mon, 21 Feb 2011 12:00:45 +0000
Message-Id: <EB570D7E-AA1F-4A08-B751-9B0E6E291D65@bbc.co.uk>
To: public-web-and-tv@w3.org
While not directly pertaining to this community (though is key in the current API discussion here!) - I put up 


largely as a thank you to all the folks in the wider open standards/source communities who came together to get frame-accuracy fixed. 

I know this may found trivial - but for the likes of us - this makes an absolute key difference. It is a serious game changer. With frame accurate time codes you can suddenly (and for the first time!) start considering professional use (well - ideally a lot better than frame-accurate - as audio is needs reliable milliseconds).

Feel free to leave comments if you want us to do another much more detailed post on this elusive 'proxy editing' and 'Edit Decision Lists' - as these concepts are quite core to this industry. And the success in the field of certain APIs, as seen in some of the recent discussions on this list, are related to how much of an impedance (mis) match there is.


Received on Monday, 21 February 2011 12:01:51 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:57:03 UTC