18386 2012-07-24 16:24:08 +0000 Ad-Insertion support 2016-10-25 09:18:58 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified All All RESOLVED WONTFIX whatwg-resolved P2 enhancement --- 1 duncan.rowden dave.null annevk ian lrosenth mike philipj public-html-admin public-html-wg-issue-tracking robin travil public-html-bugzilla oldest_to_newest 71403 0 duncan.rowden 2012-07-24 16:24:08 +0000 As part of the Media Source Extension work, there's been some discussion on how to support Ad-insertion: http://lists.w3.org/Archives/Public/public-html-media/2012Jul/0038.html As this is a use-case that is not only subject to adaptive-bitrate streams, the suggestion was made to file a bug against HTML spec itself. The requirement is to have a way to frame-accurately define an outpoint for a piece of content and switch to another. In order to save bandwidth it would also be preferable if the UA would not buffer past this outpoint. The subsequent text is not a proposal, just an illustration on how this could be achieved: - A setEndTime call could be defined, which takes a time value as its argument. A UA would then only buffer to the point defined by setEndTime. - A queue call could be defined to allow a subsequent media element to be queued up. This could take in a time-offset argument to allow playback from a defined point in the media. The second piece of media would then automatically start playing (at the chosen offset) when the point defined by setEndTime is reached. 73354 1 ian 2012-09-06 19:27:52 +0000 Is this intended for the WHATWG spec or for the W3C spec? It's assigned to me, but in the W3C spec's component. 73411 2 duncan.rowden 2012-09-07 09:33:39 +0000 I left the default options on when creating this bug, which then must have assigned the bug to you. I was not aware I could submit bugs to WHATWG so was intending the bug for the W3C spec. Could you help me find the correct assignee? (In reply to comment #1) > Is this intended for the WHATWG spec or for the W3C spec? It's assigned to me, > but in the W3C spec's component. 73695 3 philipj 2012-09-12 13:52:08 +0000 It sounds like this would have a lot of overlap with MSE, which already supports ad-insertion, as far as I can tell. 73758 4 duncan.rowden 2012-09-13 10:20:01 +0000 (In reply to comment #3) > It sounds like this would have a lot of overlap with MSE, which already > supports ad-insertion, as far as I can tell. This issue was previously discussed in the MSE group (see Description #c0). The proposal for ad-insertion in MSE only caters for a specific use-case, which requires media to be encoded with ad-insertion in mind. These ads are then inserted at specific segment boundaries. Ad-inserts in the broadcast industry don't typically work this way though, as ads aren't always placed at these specific boundaries. This requirement lead to a discussion within the MSE group that resulted in bringing this bug to the HTML-WG, because MSE was not considered the appropriate place to deal with this bug. 74673 5 erika.doyle 2012-09-27 22:34:07 +0000 Moving this feature request to HTML.next product for further consideration. 81774 6 robin 2013-01-21 16:00:40 +0000 Mass move to "HTML WG" 81881 7 robin 2013-01-21 16:03:19 +0000 Mass move to "HTML WG" 125949 8 travil 2016-04-20 16:33:39 +0000 HTML5.1 Bugzilla Bug Triage: Incubation needed This bug constitutes a request for a new feature of HTML. Our current guidelines, rather than track such requests as bugs or issues, is to create a proposal for the desired behavior, or at least a sketch of what is wanted (much of which is probably contained in this bug), and start the discussion/proposal in the WICG (https://www.w3.org/community/wicg/). As your idea gains interest and momentum, it may be brought back into HTML through the Intent to Migrate process (https://wicg.github.io/admin/intent-to-migrate.html).