W3C home > Mailing lists > Public > public-html-media@w3.org > September 2016

[media-source] Clarify expected content of "codecs" parameter in addSourceBuffer/isTypeSupported for streams with multiple tracks of same codec type

From: wolenetz via GitHub <sysbot+gh@w3.org>
Date: Wed, 14 Sep 2016 19:19:31 +0000
To: public-html-media@w3.org
Message-ID: <issues.opened-176995942-1473880768-sysbot+gh@w3.org>
wolenetz has just created a new issue for 
https://github.com/w3c/media-source:

== Clarify expected content of "codecs" parameter in 
addSourceBuffer/isTypeSupported for streams with multiple tracks of 
same codec type ==
Let's say we have a multi-track webm stream containing 1 vp8 track and
 2 vorbis tracks.
Would a fully specified type parameter to 
addSourceBuffer()/isTypeSupported() for this stream be:
'video/webm; codecs="vp8, vorbis"'

or is the following required in a fully-specified type:

'video/webm; codecs="vp8, vorbis, vorbis"'?

Marking as vNext: For MSE v1, this issue is moot (see #137), since 
compliance with that version of the spec doesn't require fully 
specified codecs strings (though at least one implementation does, 
Chrome). Note that DASH manifests produced by at least one muxer 
implementation contain codecs strings containing the latter, 
undeduplicated codecs string, form (see 
https://codereview.chromium.org/2226443002/diff/360001/media/filters/media_source_state.cc#newcode597).

Please view or discuss this issue at 
https://github.com/w3c/media-source/issues/161 using your GitHub 
account
Received on Wednesday, 14 September 2016 19:19:38 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 14 September 2016 19:19:39 UTC