7253 2009-08-10 20:00:07 +0000 <video>: Provide a way to let the browser know what's coming next, for gapless playback 2017-07-21 10:31:08 +0000 1 1 1 Unclassified WHATWG HTML unspecified All All RESOLVED WONTFIX http://whatwg.org/specs/web-apps/current-work/#the-audio-element P3 enhancement Needs Impl Interest 10711 1 contributor ian annevk hober0 ian mike philipj public-html-admin public-html-wg-issue-tracking robin silviapfeiffer1 slave.loren contributor oldest_to_newest 26360 0 contributor 2009-08-10 20:00:07 +0000 Section: http://whatwg.org/specs/web-apps/current-work/#audio Comment: Media elements should provide a "next" property to gaplessly play back another media object after it has finished. This woud allow proper playback of gapless albums and an in-browser implementation of HTTP Adaptive Bitrate Streaming. Posted from: 209.251.142.125 26955 1 ian 2009-09-09 09:07:20 +0000 Agreed, but let's wait til we have good implementation experience on the current API before adding more. Deferring to a future version. 26957 2 ian 2009-09-09 09:08:19 +0000 *** Bug 7254 has been marked as a duplicate of this bug. *** 33194 3 mjs 2010-03-14 14:48:55 +0000 This bug predates the HTML Working Group Decision Policy. If you are satisfied with the resolution of this bug, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html This bug is now being moved to VERIFIED. Please respond within two weeks. If this bug is not closed, reopened or escalated within two weeks, it may be marked as NoReply and will no longer be considered a pending comment. 82026 4 public-rdfa-wg 2013-01-24 06:38:19 +0000 This bug was cloned to create HTML WG bug 19057. 84596 5 ian 2013-03-19 00:14:49 +0000 Are any browser vendors interested in doing something like this? 85042 6 silviapfeiffer1 2013-03-27 01:02:24 +0000 For the last 3 years at FOMS we have had discussions of gapless playback. Here are some notes from those meetings: * http://www.foms-workshop.org/foms2012/pmwiki.php/Main/CollabBrowserDevs ("smooth playback" in the "Asset loading control" section) * http://www.openmediadevelopers.org/pmwiki.php/Main/OVC2011GaplessPlayback You will note that in 2011 the discussion about gapless playback included also a discussion about playlists. They are intertwined issues. 112820 7 philipj 2014-10-08 12:06:05 +0000 This would require coordinating the backends of two media elements, which is a bit like MediaController. No one has put in the engineering effort to implement MediaController correctly yet, so I'm a bit skeptical of this. Note that if the containers and codecs of two audio files are the same, you should be able to use Media Source Extensions to play them gaplessly. It should also be possible using the Web Audio API, although possibly only if both files are fully loaded and decoded in advance. Splitting into chunks would help, and make it kind of like the MSE case. 112997 8 silviapfeiffer1 2014-10-12 11:37:12 +0000 I think people are doing it now by preloading the next media resource in a hidden media element. I can live with that for now. 113043 9 philipj 2014-10-13 20:52:08 +0000 That doesn't get you gapless playback, but I can live with that too :) 128739 10 annevk 2017-07-21 10:31:08 +0000 Please file a new issue at https://github.com/whatwg/html/issues/new if there's still interest.