Thanks,
It will be very good if HTML5 API specify this. I mean, Say, If we use
<audio> tag , then It must stream only audio part of the file irrespective
of the fact that the src field contains a video file.
PS: sorry for top post
On Tue, May 11, 2010 at 3:53 PM, Chris Double <chris.double at
double.co.nz>wrote:
> On 11/05/10 22:05, narendra sisodiya wrote:
> > 1) Do firefox stream whole video file and play only audio part
> > OR
> > 2) Do firefox stream only audio part of the file and play it.
> >
> > I want to know, is there any bandwidth advantage with <audio/>
tag over
> > <video> tag ?
>
> Whether you use <audio> or <video> it will stream the entire
contents of
> the file (ie. both video and audio tracks). If the file contains
> multiple audio tracks and/or other information that will be streamed and
> ignored by Firefox too.
>
> Chris.
>
>
--
???????????????????????????
? Narendra Sisodiya ( ???????? ???????? )
? Society for Knowledge Commons
? Web : http://narendra.techfandu.org
???????????????????????????
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.xiph.org/pipermail/ogg-dev/attachments/20100511/f9188c06/attachment.htm
On 11 May 2010 04:24, narendra sisodiya <narendra.sisodiya at gmail.com> wrote:> ???? It will be very good if HTML5 API specify this. I mean, Say, If we use > <audio> tag , then It must stream only audio part of the file irrespective > of the fact that the src field contains a video file.I don't think that's a practical option, since the server must manipulate the file to return an audio-only subset of the data for there to be any bandwidth advantage. That's not something that the HTML5 specification, which documents browser behaviour, can describe. Note that it's completely possible to use a server-size module or script to do this, using a query url in the HTML5 media element's src attribute. It's just part of a custom server config rather than the HTML5 API. The Media Fragments Working Group at the W3C is currently working on a standardized syntax for this. See http://www.w3.org/2008/WebVideo/Fragments/WD-media-fragments-spec/ if you're interested. FWIW, -r
FWIW chromium does client side range requests that in theory would request only the audio. But. the ogg demux reads the other tracks and discards them. A use case I've heard is listening to music videos and discard the video... bit of a bandwidth waste. On Tue, May 11, 2010 at 10:17 AM, Ralph Giles <giles at thaumas.net> wrote:> On 11 May 2010 04:24, narendra sisodiya <narendra.sisodiya at gmail.com> > wrote: > > > It will be very good if HTML5 API specify this. I mean, Say, If we > use > > <audio> tag , then It must stream only audio part of the file > irrespective > > of the fact that the src field contains a video file. > > I don't think that's a practical option, since the server must > manipulate the file to return an audio-only subset of the data for > there to be any bandwidth advantage. That's not something that the > HTML5 specification, which documents browser behaviour, can describe. > > Note that it's completely possible to use a server-size module or > script to do this, using a query url in the HTML5 media element's src > attribute. It's just part of a custom server config rather than the > HTML5 API. The Media Fragments Working Group at the W3C is currently > working on a standardized syntax for this. See > http://www.w3.org/2008/WebVideo/Fragments/WD-media-fragments-spec/ if > you're interested. > > FWIW, > -r > _______________________________________________ > ogg-dev mailing list > ogg-dev at xiph.org > http://lists.xiph.org/mailman/listinfo/ogg-dev >-------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.xiph.org/pipermail/ogg-dev/attachments/20100511/759d0e71/attachment.htm