The UA is able to determine what Byte-Ranges to request when seeking to a point in the video already, I'd imagine the same logic could be applied in this scenario. Sounds like the end_offset in time units might be a problem.<div>
<br></div><div>I know I'd make use of start_offset="50s" end_offset="70s" tags quite a bit with the playlist use case you brought up.<br><br><div class="gmail_quote">On Wed, Jun 30, 2010 at 2:29 PM, Richard Kern <span dir="ltr"><<a href="mailto:kernrj@gmail.com">kernrj@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div>If video were downloaded in sections, there could be a mechanism for telling the browser to wait for a certain number of sections to be downloaded before playback. Also, if we had the option to specify a different URL/file offset for each section, that opens a few possibilities - in Marques's case, scripting could control the url, and bring up an "insufficient funds" or similar frame, seamlessly. The user would also be able to select a different quality of video on the fly, without having the video reload. Another application is a playlist - if I wanted to post a video and "edit" out or splice in certain parts, the modified version could be played seamlessly and use the original files instead of using a newly encoded video.<div>
<br></div><div><video></div><div> <source min_buffer="1" max_buffer="2"></div><div> <section src="URL1"/></div><div> <section src="URL2" start_offset="1000000bytes" end_offset="3000000bytes"></div>
<div> <section src="URL3"/></div><div> </source></div><div></video></div><div><br></div><div>or</div><div><br></div><div>video.setSection(0, URL1);</div><div>video.setSection(1, URL2, 1000000, 3000000);</div>
<div>video.setSection(2, URL3);</div><div><br></div><div>video.setMinBufferedSections(1); //The first section must be completely downloaded before playback begins</div><div>video.setMaxBufferedSections(2); //The download will not be permitted to get more than 2 sections ahead<br>
<br></div><div><br></div><div>In the case of specifying a section with start_offset="5000ms", it may not be trivial for the browser to know how far to seek in order to start playback at that time. It may also be a problem for "end_offset" or in Herman's case "buffer", because the browser would have to partially decode the video stream in order to know how many frames have been downloaded. Buffering from/to a specific time is still possible, but would require metadata correlating video time to file position.</div>
<div><br></div><div>Searching to a random file address may also present a problem if it is not the address of an I-frame. In this case the browser would need to continue seeking until it reaches a point it can decode from.</div>
<div><div></div><div class="h5">
<div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div class="gmail_quote">On Wed, Jun 30, 2010 at 10:10 AM, Nicholas Stephan <span dir="ltr"><<a href="mailto:nicholas.stephan@gmail.com" target="_blank">nicholas.stephan@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I know some internet providers around the world are still charging by bandwidth. I'm sure those customers would appreciate not being sent, and charged for, content they don't even watch. An option to set the buffer size and a toggle to only preloaded the buffer rather than the whole video would go a long way to facilitate that.<div>
<div></div><div><br>
<br>
<br>
<br>
On Jun 30, 2010, at 8:40 AM, Marques Johansson <<a href="mailto:marques@displague.com" target="_blank">marques@displague.com</a>> wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
This attribute fits in with what I was requesting last week.<br>
<br>
My server provides a pay-per-minute video-on-demand service. I don't<br>
want the browser to request more than I am going to send it and in<br>
HTTP I have no way to tell the browser to use "Range: bytes 0-1000",<br>
let alone "Range: 0-" (which my service would refuse to serve). My<br>
service would set the buffer attribute to an acceptable amount of time<br>
that my service would essentially be giving the user for free<br>
(something we already have to do in our Windows Media world).<br>
<br>
Along with this attribute, attributes to set the max fetch size and<br>
the fetch style would serve my purposes very well.<br>
<br>
<video buffer="5000ms" partialrequestsonly maxpartialrequest="10000"><br>
<br>
These are horrible attribute names, but something like this would<br>
avoid needing to change the HTTP spec to get the browser to use<br>
"Range:" in requests and to set the upper bound for ranges.<br>
_______________________________________________<br>
Help mailing list<br>
<a href="mailto:Help@lists.whatwg.org" target="_blank">Help@lists.whatwg.org</a><br>
<a href="http://lists.whatwg.org/listinfo.cgi/help-whatwg.org" target="_blank">http://lists.whatwg.org/listinfo.cgi/help-whatwg.org</a><br>
</blockquote>
_______________________________________________<br>
Help mailing list<br>
<a href="mailto:Help@lists.whatwg.org" target="_blank">Help@lists.whatwg.org</a><br>
<a href="http://lists.whatwg.org/listinfo.cgi/help-whatwg.org" target="_blank">http://lists.whatwg.org/listinfo.cgi/help-whatwg.org</a><br>
</div></div></blockquote></div><br></div></div></div>
<br>_______________________________________________<br>
Help mailing list<br>
<a href="mailto:Help@lists.whatwg.org">Help@lists.whatwg.org</a><br>
<a href="http://lists.whatwg.org/listinfo.cgi/help-whatwg.org" target="_blank">http://lists.whatwg.org/listinfo.cgi/help-whatwg.org</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>Mike Ressler<br>CEO and Founder<br>StatEasy by RessQ Technologies Inc.<br><a href="http://www.stateasysports.com">http://www.stateasysports.com</a><br>412-223-7377<br>
</div>