On 6/6/2012 1:32 AM, Silvia Pfeiffer wrote:
I believe right now there are two proposals under discussion that are
trying to address the adaptive streaming issues:
https://dvcs.w3.org/hg/audio/raw-file/tip/streams/StreamProcessing.html
and
http://dvcs.w3.org/hg/html-media/raw-file/tip/media-source/media-source.html
I believe both are still somewhat at the experimental level and need
harmonization, but they are both being worked on at the W3C.
The <video><source /></video> format works well for the majority of use
cases, but it falls a little short in expressiveness.
It was not designed for adaptive streaming. I don't think it needs to
be: as Ian pointed out, an adaptive channel with endpoint negotiation
would be ideal.
And we may just end up with a new scheme: my+magic+adaptive+scheme://.
WHATWG has experimented with new URI schemes such as "enc:".
Magnet has become more common-place.
Here's what it looks like:
magnet:?xt=urn:btih:e1eaf0ce97d0a3dfd7da9fac32cffe63fcda7b66&dn=Mozilla+Firefox+13.0&tr=udp%3A%2F%2Ftracker.openbittorrent.com%3A80&tr=udp%3A%2F%2Ftracker.publicbt.com%3A80&tr=udp%3A%2F%2Ftracker.istole.it%3A6969&tr=udp%3A%2F%2Ftracker.ccc.de%3A80
There is a [reasonably] secure hash and 4 reference servers.
The magnet URI technique is going to keep evolving anyway, but I thought
it'd be nice if we took a look at it, to see if there's any further use
in relation to media streaming.
One might for instance, provide additional data, pointing to a set of
http servers and perhaps an alternative as well, pointing to a smaller
file size.
-Charles
On Wed, Jun 6, 2012 at 8:23 AM, Charles Pritchard <[email protected]> wrote:
On Jun 5, 2012, at 2:54 PM, Ian Hickson <[email protected]> wrote:
On Tue, 21 Feb 2012, Rodger Combs wrote:
I propose that <source> add a quality, bitrate, or filesize attribute to
allow the UA to decide between multiple streams by choosing the maximum
quality file that it can download within a reasonable amount of time
If this is for a site like YouTube, I think an adaptive network channel
would be a more effective solution (i.e. one where the download adapts in
real time to changing network conditions, with the endpoints negotiating
with each other regarding what to transmit).
I'd like to see strawman proposals for resource description markup.
Presently, magnet+BitTorrent is the only mature and implemented tech in this
field that I've found with wide support. And it's not even meant for adaptive
streaming.
I know that markup for subtitles happened in this group. I'd like to see an
effort for markup for resources, with the same experimental atmosphere.
The hope being that we can copy and paste some kind of text markup which
describes various endpoints and metadata sufficient for streaming strategies
for media.
