- From: Philip Jägenstedt <philipj@opera.com>
- Date: Thu, 27 Feb 2014 22:31:23 +0700
- To: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
- Cc: Leeroy <soupress@gmail.com>, Media Fragment <public-media-fragment@w3.org>
On Thu, Feb 27, 2014 at 5:30 PM, Silvia Pfeiffer <silviapfeiffer1@gmail.com> wrote: > On Thu, Feb 27, 2014 at 6:40 PM, Philip Jägenstedt <philipj@opera.com> wrote: >> No, I mean that nothing about looping should be changed, so that if >> the video pauses before the end due to a fragment end time, it just >> won't loop. > > Even with a @loop attribute? Yes. >> Unexpected, sure, but I don't think you'll find an >> implementor eager to do proper looping with fragments because of the >> complexity and edge-casiness of it. > > How is looping when reaching the end different to looping when > reaching the end of a fragment? > It's just a "we've reached this time, so then wind back to the > fragment beginning and play from there again". > What's the extra complexity? To make it loop exactly between the start time and the end time you have to integrate with the media framework, otherwise the looping won't be gapless and it won't loop exactly the same number of samples each time. An implementation that doesn't loop accurately doesn't add anything that you can't do by seeking in JavaScript at the appropriate time. I suspect that implementors will say "just use Web Audio API" if asked to implement accurate looping for <audio src="sound#t=1,2" loop>. Philip
Received on Thursday, 27 February 2014 15:31:50 UTC