Yep- big up to everyone who helped us out!
> largely as a thank you to all the folks in the wider what-wg communities
> who came together to get frame-accuracy fixed. Credit go to the open
> standards and open source communities around Webkit, Chrome and Mozilla
> which made it happen: Andrew Sch
Rather than trying to sum up all use cases I think that the media asset
should be fully random accessible and frame accurate to cover any current
and future us ecasse. You should be able to write Javascripts that tell the
asset to go to any point in time.
That way a web developer (or implementers
This is a very interesting observation, I've been thinking what this means
in terms of UI design for scrubbars/players and there's a design limitation
with (traditional) seekbars:
Seekbars tend to have a physical length in pixels, meaning that there's a
physical limitation how precise one can move
I still want the API to support seeks to exact frames.
eg when I build some GUI that allows the user to click on a button that says
"explosion shot 1 at 00:31:02.15" then I want the player to seek to
00:31:02.15 exactly and not to say, 00:31:02.01 simply b/c that's where a
keyframe happens to be.
I'm really happy to see that Chromium has landed a fix for frame-accurate
seeking, making SMPTE timecode compliant operations with HTML5 video
possible.
The fix for Firefox is underway (
https://bugzilla.mozilla.org/show_bug.cgi?id=626273 ) and I have filed bugs
at both Webkit/Safari ( https://bugs
On Wed, Jan 12, 2011 at 10:15 AM, Jeroen Wijering
wrote:
>
> Alternatively, one could look at a step() function instead of a
> seek(pos,exact) function. The step function can be used for frame-accurate
> controls. e.g. step(2) or step(-1). The advantage over a seek(pos,exact)
> function (and the p
wrote:
> On Tue, Jan 11, 2011 at 5:40 PM, Rob Coenen wrote:
> > Hi David- that is b/c in an ideal world I'd want to seek to a time
> expressed
> > as a SMPTE timecode (think web apps that let users step x frames back,
> seek
> > y frames forward etc.).
David I agree- however that's common practice in any video editing tool, in
any digital video camera, etc. It's the defacto industry standard for anyone
working with digital video.
I'm just trying to make readers of this list aware of the fact that HTML5
does a great job in video-play back, but th
f the 4th, and so on.
>
> On Jan 11, 2011, at 18:54 , Rob Coenen wrote:
>
> > just a follow up question in relation to SMPTE / frame accurate playback:
> As
> > far as I can tell there is nothing specified in the HTML5 specs that will
> > allow us to determine the actua
tools in HTML5 that allow to access each
individual frame and do other things than simply playing back the movie in a
linear fashion from beginning to end.
-Rob
On Tue, Jan 11, 2011 at 10:05 PM, Chris Pearce wrote:
> On 12/01/2011 10:58 a.m., Rob Coenen wrote:
>
>> Intresting- I didn&
expose the FPS property as meta-data to the web browser alongside
the 'duration' property?
-Rob
On Tue, Jan 11, 2011 at 9:29 PM, Eric Carlson wrote:
>
> On Jan 11, 2011, at 12:54 PM, Rob Coenen wrote:
>
> Eric, not sure if I understand what you mean. Are you referring to
> digi
Eric, not sure if I understand what you mean. Are you referring to digitally
encoded files where frame #1 has a different duration than frame #2?
On Tue, Jan 11, 2011 at 6:10 PM, Eric Carlson wrote:
>
> On Jan 11, 2011, at 9:54 AM, Rob Coenen wrote:
>
> > just a follow up question
ediaGuide/UsingHTTPLiveStreaming/UsingHTTPLiveStreaming.html
>
> http://devimages.apple.com/iphone/samples/bipbopgear3.html
>
>
> On Mon, Jan 10, 2011 at 11:18 AM, Rob Coenen wrote:
>
>> Thanks for the update.
>> I have been testing with WebKit nightly / 75294 on MacOSX 10.6.6 /
Jan 9, 2011, at 11:14 AM, Rob Coenen wrote:
>
> I have written a simple test using a H264 video with burned-in timecode
> (every frame is visually marked with the actual SMPTE timecode)
> Webkit is unable to seek to the correct timecode using 'currentTime', it's
&g
eckon it
simply seeks to the nearest keyframe?
-Rob
On Fri, Jan 7, 2011 at 5:02 PM, Eric Carlson wrote:
>
> On Jan 7, 2011, at 8:22 AM, Rob Coenen wrote:
>
> >
> > are there any plans on adding frame accuracy and/or SMPTE support to
> HTML5
> > video?
> >
>
Hello list,
are there any plans on adding frame accuracy and/or SMPTE support to HTML5
video?
As far as I know it's currently impossible to play HTML5 video
frame-by-frame, or seek to a SMPTE compliant (frame accurate) time-code.
The nearest seek seems to be precise to roughly 1-second (or neares
16 matches
Mail list logo
