Re: [whatwg] Fetch, MSE, and MIX

Hi Ryan, Thanks for writing this up. I know you already know this, but I wanted to publically declare my support as one of the MSE editors. While I wish we didn't need this, I can understand the concerns of content providers and I think this is a reasonable compromise. Aaron On Thu Feb 19 2015 a

Re: [whatwg] HTML5 video seeking

Hi Ralph, On Mon, Nov 14, 2011 at 3:58 PM, Ralph Giles wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 14/11/11 03:49 PM, Aaron Colwell wrote: > > > Does this mean the user agent must resume playback at the exact > > location specified? >

Re: [whatwg] HTML5 video seeking

ring frame accurate seeking at this point or am I just misinterpreting some part of the spec. Aaron On Tue, Nov 15, 2011 at 1:30 AM, Philip Jägenstedt wrote: > On Tue, 15 Nov 2011 00:49:32 +0100, Aaron Colwell > wrote: > > Hi, >> >> I was looking at the seeking >> al

[whatwg] HTML5 video seeking

Hi, I was looking at the seeking algorithm and had a question about step 10. 10. Wait until the user agent has established whether or not the media data for the new playback position is available, and, if

Re: [whatwg] Proposal for a MediaSource API that allows sending media data to a HTMLMediaElement

Hi Mark, comments inline... On Thu, Aug 11, 2011 at 9:46 AM, Mark Watson wrote: > I think it would be good if the API recognized the fact that the media data > may becoming from several different original files/streams (e.g. different > bitrates) as the player adapts to network or other conditi

Re: [whatwg] File API Streaming Blobs

Comments inline... On Wed, Aug 10, 2011 at 2:05 PM, Charles Pritchard wrote: > On 8/9/2011 9:38 AM, Aaron Colwell wrote: > > FYI I'm working on an experimental extension to Chromium to allow media > data to be streamed into a media element via JavaScript. Here is the draft &g

Re: [whatwg] File API Streaming Blobs

FYI I'm working on an experimental extension to Chromium to allow media data to be streamed into a media element via JavaScript. Here is the draft spec and pending WebKit patch

Re: [whatwg] Proposal for a MediaSource API that allows sending media data to a HTMLMediaElement

On Wed, Jul 13, 2011 at 8:00 PM, Robert O'Callahan wrote: > On Thu, Jul 14, 2011 at 4:35 AM, Aaron Colwell wrote: > >> I am open to suggestions. My intent was that the browser would not attempt >> to cache any data passed into append(). It would just demux the buffers that

Re: [whatwg] Proposal for a MediaSource API that allows sending media data to a HTMLMediaElement

On Tue, Jul 12, 2011 at 5:05 PM, Robert O'Callahan wrote: > On Wed, Jul 13, 2011 at 12:00 PM, Aaron Colwell wrote: > >> On Tue, Jul 12, 2011 at 4:44 PM, Robert O'Callahan >> wrote: >> >>> I had imagined that this API would let the author feed in the sa

Re: [whatwg] Proposal for a MediaSource API that allows sending media data to a HTMLMediaElement

On Tue, Jul 12, 2011 at 4:44 PM, Robert O'Callahan wrote: > On Wed, Jul 13, 2011 at 11:30 AM, Aaron Colwell wrote: > >> I'm doing WebM demuxing and media fetching in JavaScript. When a seek >> occurs, I look at currentTime to see where we are seeking to. I then look at

Re: [whatwg] Proposal for a MediaSource API that allows sending media data to a HTMLMediaElement

On Tue, Jul 12, 2011 at 4:17 PM, Robert O'Callahan wrote: > On Wed, Jul 13, 2011 at 11:14 AM, Aaron Colwell wrote: > >> >> I'm open to that. In fact that is how my current prototype is implemented >> because it was the least painful way to test these ide

Re: [whatwg] Proposal for a MediaSource API that allows sending media data to a HTMLMediaElement

On Tue, Jul 12, 2011 at 3:28 PM, Robert O'Callahan wrote: > On Wed, Jul 13, 2011 at 8:45 AM, Aaron Colwell wrote: > >> I thought about adding an attribute to HTMLMediaElement that provided a >> URL for signalling MediaSource usage. That mechanism would allow you to >>

Re: [whatwg] Proposal for a MediaSource API that allows sending media data to a HTMLMediaElement

Hi Harald, Please point me to specific threads that talk about this. I looked through the public-web...@w3.org archive and didn't see anything about interactive media handling. I did look through the Mozilla/Cisco proposal thread

Re: [whatwg] Proposal for a MediaSource API that allows sending media data to a HTMLMediaElement

On Mon, Jul 11, 2011 at 5:54 PM, Robert O'Callahan wrote: > It seems to me that the spec is written assuming only one media element is > consuming the MediaSource. But nothing stops multiple elements consuming the > same URL simultaneously. Maybe instead of going through a URL you should add > API

[whatwg] Proposal for a MediaSource API that allows sending media data to a HTMLMediaElement

Hi, Based on comments in the File API Streaming Blobs thread and my Extending HTML 5 video for adaptive streaming thread, I decided on taking a s

Re: [whatwg] Extending HTML 5 video for adaptive streaming

Hi Bob, Comments inline On Fri, Jul 1, 2011 at 8:40 AM, Bob Lund wrote: > Hi Aaron, > > Here are some other aspects of script controlled adaptive bit rate that > occur to me, perhaps you have already considered these. > > 1) I guess script will be responsible for maintaining its own playback >

Re: [whatwg] Extending HTML 5 video for adaptive streaming

Hi Adam, On Thu, Jun 30, 2011 at 5:20 PM, Adam Malcontenti-Wilson wrote: > @acolwell: > Is the appendData method one your suggesting or one already > specified/existing? > > I'm suggesting it. It was a quick and dirty way to try out some ideas I had while working on a prototype for Chromium. Now

Re: [whatwg] Extending HTML 5 video for adaptive streaming

Hi Robert, comments inline. On Thu, Jun 30, 2011 at 4:13 PM, Robert O'Callahan wrote: > On Fri, Jul 1, 2011 at 4:59 AM, Aaron Colwell wrote: > >> I've also been looking at the WebRTC MediaStream API and was wondering if >> it >> makes more sense

[whatwg] Extending HTML 5 video for adaptive streaming

Hi, I've been working on an adaptive streaming prototype that uses JavaScript to fetch chunks of media and feeds them to the video tag for decoding. The idea is to let the adaptation algorithm and CDN interactions happen in JavaScript so that they can evolve without the need for browser changes. I

Re: [whatwg] Redirect handling for &

Thanks for your response.. comments inline On Fri, Mar 4, 2011 at 1:30 AM, Philip Jägenstedt wrote: > On Thu, 03 Mar 2011 22:15:58 +0100, Aaron Colwell > wrote: > > Hi, >> >> I was looking at the resource fetch >> algorithm< >> http://www.whatwg.or

[whatwg] Redirect handling for &

Hi, I was looking at the resource fetch algorithmsection and fetching resources sections of the HTML5 spec to determine