On Mon, Aug 17, 2009 at 8:04 PM, Max Romantschuk <span dir="ltr"><<a href="mailto:max@romantschuk.fi">max@romantschuk.fi</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">Silvia Pfeiffer wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Precision is influenced more strongly by the temporal<br>
resolution of the decoding pipeline rather than the polling resolution<br>
for currentTime. I doubt the previous implementations of "start" and<br>
"end" gave you a 3 sample accurate resolution even for wav files.<br>
</blockquote>
<br></div>
I'll chime in here, having done extensive work with audio and video codecs. With current codec implementations getting sample- or frame-accurate resolution is largely a pipe dream. (Outside of the realm of platforms dedicated to content production and playback.) Especially for video there can be several seconds between keyframes, frame-accurate jumps requiring complex buffering tricks.<br>
</blockquote><div> </div></div>Those tricks aren't that hard, at least for Theora; we do them in Firefox.<br clear="all"><br>Rob<br>-- <br>"He was pierced for our transgressions, he was crushed for our iniquities; the punishment that brought us peace was upon him, and by his wounds we are healed. We all, like sheep, have gone astray, each of us has turned to his own way; and the LORD has laid on him the iniquity of us all." [Isaiah 53:5-6]<br>