[Bug 17000] New: Define a capability detection mechanism

https://www.w3.org/Bugs/Public/show_bug.cgi?id=17000

           Summary: Define a capability detection mechanism
           Product: HTML WG
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Media Source Extensions
        AssignedTo: adrianba@microsoft.com
        ReportedBy: acolwell@chromium.org
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org


Different user-agents may have certain limitations on the number of SourceIDs,
number of tracks, and overlap semantics they support. We need a mechanism for
Web Applications to be able to detect these limitations so they can adjust
their behavior and select appropriate content.

Here is an initial list of possible limitations user-agents might have:
-Unable to change sample rate or number of audio channels during playback.
-Certain decoder config parameter changes may not be allowed or prevent
seamless splices. (ie Vorbis codebook changes)
-Adding/removing SourceID's during playback may not be supported.
-Limited # of simultaneous audio & video tracks. This may limit # of SourceID's
as well.
-Supporting instantaneous splices @ overlap point vs waiting until the next
random access point.

This is an incomplete list, but outlines some of the implementation choices
we've  had to consider in the Chromium implementation.

Our initial suggestion is to create MIME parameter(s) similar to codecs and
reuse the current canPlayType() infrastructure to determine what a UA supports.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Tuesday, 8 May 2012 20:10:45 UTC