On Mon, 17 Aug 2009, Max Romantschuk wrote:
Silvia Pfeiffer wrote:
Precision is influenced more strongly by the temporal resolution of
the decoding pipeline rather than the polling resolution for
currentTime. I doubt the previous implementations of start and end
gave you a 3 sample
At 0:49 +1200 23/08/09, Robert O'Callahan wrote:
On Mon, Aug 17, 2009 at 8:04 PM, Max Romantschuk
mailto:m...@romantschuk.fim...@romantschuk.fi wrote:
Silvia Pfeiffer wrote:
Precision is influenced more strongly by the temporal
resolution of the decoding pipeline rather than the polling
On Sat, Aug 22, 2009 at 7:37 AM, Silvia Pfeiffer
silviapfeiff...@gmail.comwrote:
Xiph has spent a long time on developing libraries that make seeking
simple for Ogg Theora/Vorbis and Firefox has the advantage of using
these libraries.
In fact we had to write this support ourselves.
Rob
--
On Mon, Aug 17, 2009 at 8:04 PM, Max Romantschuk m...@romantschuk.fi wrote:
Silvia Pfeiffer wrote:
Precision is influenced more strongly by the temporal
resolution of the decoding pipeline rather than the polling resolution
for currentTime. I doubt the previous implementations of start and
On Sat, Aug 22, 2009 at 10:49 PM, Robert O'Callahanrob...@ocallahan.org wrote:
On Mon, Aug 17, 2009 at 8:04 PM, Max Romantschuk m...@romantschuk.fi wrote:
Silvia Pfeiffer wrote:
Precision is influenced more strongly by the temporal
resolution of the decoding pipeline rather than the polling
Silvia Pfeiffer wrote:
Precision is influenced more strongly by the temporal
resolution of the decoding pipeline rather than the polling resolution
for currentTime. I doubt the previous implementations of start and
end gave you a 3 sample accurate resolution even for wav files.
I'll chime in
Hi,
I see no reason why they should not be applicable to data URIs when it
is obvious that the data URI is a media file. This has not yet been
discussed, but would be an obvious use case.
OK. That would be welcome - although there could be syntactic problems
as where to place fragment
Max Romantschuk wrote:
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.)
Dr. Markus Walther wrote:
The much weaker goal I would propose is to support at least one simple
lossless audio format in this regard (I am not qualified to comment on
the video case). Simple means 'simple to generate, simple to decode',
and PCM WAVE meets these requirements, so would be an
On Thu, 13 Aug 2009, Philip Jägenstedt wrote:
We would like to request that addCueRange/removeCueRanges be dropped
from the spec before going into Last Call. We are not satisfied with it
and want to see it replaced with a solution that includes (scriptless)
timed text (a.k.a
On Fri, Aug 14, 2009 at 4:08 AM, Philip Jägenstedtphil...@opera.com wrote:
On Fri, 14 Aug 2009 12:48:59 +0200, Silvia Pfeiffer
silviapfeiff...@gmail.com wrote:
On Fri, Aug 14, 2009 at 7:54 PM, Dr. Markus Waltherwalt...@svox.com
wrote:
Silvia Pfeiffer wrote:
2009/8/14 Dr. Markus Walther
On Sat, 15 Aug 2009 08:47:32 +0200, Jonas Sicking jo...@sicking.cc wrote:
The problem is that you can't use fragment identifiers with data-URIs.
For example
data:text/plain,hello world#frag
Represents a text/plain document with the contents:
hello world#frag
It does not represent the
On Fri, Aug 14, 2009 at 11:58 PM, Anne van Kesterenann...@opera.com wrote:
On Sat, 15 Aug 2009 08:47:32 +0200, Jonas Sicking jo...@sicking.cc wrote:
The problem is that you can't use fragment identifiers with data-URIs.
For example
data:text/plain,hello world#frag
Represents a text/plain
Hi,
The .start/.end properties were dropped in favor of media fragments,
which the Media Fragments Working Group is producing a spec for.
Who decided this? Has this decision been made public on this list?
It will
be something like http://www.example.com/movie.mov#t=12.33,21.16
var
Silvia,
2009/8/13 Dr. Markus Walther walt...@svox.com:
please note that with cue ranges removed, the last HTML 5 method to
perform audio subinterval selection is gone.
Not quite. You can always use the video.currentTime property in a
javascript to directly jump to a time offset in a video.
2009/8/14 Dr. Markus Walther walt...@svox.com:
Hi,
The .start/.end properties were dropped in favor of media fragments,
which the Media Fragments Working Group is producing a spec for.
Who decided this? Has this decision been made public on this list?
It will
be something like
Silvia Pfeiffer wrote:
2009/8/14 Dr. Markus Walther walt...@svox.com:
Hi,
The .start/.end properties were dropped in favor of media fragments,
which the Media Fragments Working Group is producing a spec for.
Who decided this? Has this decision been made public on this list?
It will
be
On Fri, Aug 14, 2009 at 7:54 PM, Dr. Markus Waltherwalt...@svox.com wrote:
Silvia Pfeiffer wrote:
2009/8/14 Dr. Markus Walther walt...@svox.com:
Hi,
The .start/.end properties were dropped in favor of media fragments,
which the Media Fragments Working Group is producing a spec for.
Who
On Fri, 14 Aug 2009 10:28:14 +0200, Dr. Markus Walther walt...@svox.com
wrote:
Hi,
The .start/.end properties were dropped in favor of media fragments,
which the Media Fragments Working Group is producing a spec for.
Who decided this? Has this decision been made public on this list?
It
On Fri, 14 Aug 2009 10:42:50 +0200, Dr. Markus Walther walt...@svox.com
wrote:
Silvia,
2009/8/13 Dr. Markus Walther walt...@svox.com:
please note that with cue ranges removed, the last HTML 5 method to
perform audio subinterval selection is gone.
Not quite. You can always use the
On Fri, 14 Aug 2009 12:48:59 +0200, Silvia Pfeiffer
silviapfeiff...@gmail.com wrote:
On Fri, Aug 14, 2009 at 7:54 PM, Dr. Markus Waltherwalt...@svox.com
wrote:
Silvia Pfeiffer wrote:
2009/8/14 Dr. Markus Walther walt...@svox.com:
Hi,
The .start/.end properties were dropped in favor of
I agree with this assessment.
Please note that at this stage this is my personal opinion, since I
haven't discussed it with other Mozilla developers yet.
Regards,
Silvia.
On Thu, Aug 13, 2009 at 6:31 PM, Philip Jägenstedtphil...@opera.com wrote:
Hi,
We would like to request that
Hi,
please note that with cue ranges removed, the last HTML 5 method to
perform audio subinterval selection is gone.
AFAIK, when dropping support for 'start' and 'end' attributes it was
noted on this list that cue ranges would provide a replacement to
dynamically select, say, a 3-second range
On Thu, 13 Aug 2009 14:34:55 +0200, Dr. Markus Walther walt...@svox.com
wrote:
Hi,
please note that with cue ranges removed, the last HTML 5 method to
perform audio subinterval selection is gone.
AFAIK, when dropping support for 'start' and 'end' attributes it was
noted on this list that
At 10:31 +0200 13/08/09, Philip Jägenstedt wrote:
Hi,
We would like to request that
addCueRange/removeCueRanges be dropped from the
spec before going into Last Call. We are not
satisfied with it and want to see it replaced
with a solution that includes (scriptless) timed
text (a.k.a
On Fri, Aug 14, 2009 at 3:31 AM, David Singersin...@apple.com wrote:
At 10:31 +0200 13/08/09, Philip Jägenstedt wrote:
Hi,
We would like to request that addCueRange/removeCueRanges be dropped from
the spec before going into Last Call. We are not satisfied with it and want
to see it
Hi Markus,
2009/8/13 Dr. Markus Walther walt...@svox.com:
please note that with cue ranges removed, the last HTML 5 method to
perform audio subinterval selection is gone.
Not quite. You can always use the video.currentTime property in a
javascript to directly jump to a time offset in a video.
27 matches
Mail list logo
