- From: <bugzilla@jessica.w3.org>
- Date: Sun, 20 Jan 2013 16:44:03 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=19676
Cyril Concolato <cyril.concolato@telecom-paristech.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |cyril.concolato@telecom-par
| |istech.fr
--- Comment #8 from Cyril Concolato <cyril.concolato@telecom-paristech.fr> ---
In the same spirit, why is the spec mandating in section 4.5.6 "Coded Frame
Processing" point 1.1 and 1.2 that the Media Source Engine maintains internal
timestamps as double precision floating points, as in:
"Let presentation timestamp be a double precision floating point representation
of the coded frame's presentation timestamp."
An implementation could decide to store the timestamp and run the algorithm
using rationals.
I suggest deleting the part "a double precision floating point representation
of" in those two points.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Sunday, 20 January 2013 16:44:05 UTC