Include H265 and H264 in same manifest

[bknill]

I've read somewhere that you can include H265 at highest resolution along with the lower resolution formats and if the device can play the h265 it should prioritize that.

I have the following manifest

<?xml version="1.0" encoding="UTF-8"?>
<MPD xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:mpeg:dash:schema:mpd:2011" xmlns:cenc="urn:mpeg:cenc:2013" xsi:schemaLocation="urn:mpeg:dash:schema:mpd:2011 http://standards.iso.org/ittf/PubliclyAvailableStandards/MPEG-DASH_schema_files/DASH-MPD.xsd" type="static" minBufferTime="PT10S" profiles="urn:mpeg:dash:profile:isoff-main:2011" mediaPresentationDuration="PT54.165S">
  <Period start="PT0S" duration="PT54.165S" id="1">
    <AdaptationSet mimeType="video/mp4" frameRate="60000/1001" segmentAlignment="true" subsegmentAlignment="true" startWithSAP="1" subsegmentStartsWithSAP="1" bitstreamSwitching="false">
      <Representation id="1" width="1920" height="1080" bandwidth="4000000" codecs="avc1.4d402a">
        <BaseURL>cmaf.0.1080.H_264.cmfv</BaseURL>
        <SegmentBase indexRange="760-1135">
          <Initialization range="0-759"/>
        </SegmentBase>
      </Representation>
      <Representation id="2" width="1920" height="1080" bandwidth="4000000" codecs="hev1.1.6.L123.B0">
        <BaseURL>cmaf.0.1080_265.H_265.cmfv</BaseURL>
        <SegmentBase indexRange="708-1083">
          <Initialization range="0-707"/>
        </SegmentBase>
      </Representation>
      <Representation id="3" width="1280" height="720" bandwidth="2000000" codecs="avc1.4d4020">
        <BaseURL>cmaf.0.720.H_264.cmfv</BaseURL>
        <SegmentBase indexRange="760-1135">
          <Initialization range="0-759"/>
        </SegmentBase>
      </Representation>
      <Representation id="4" width="640" height="360" bandwidth="500000" codecs="avc1.4d401f">
        <BaseURL>cmaf.0.360.H_264.cmfv</BaseURL>
        <SegmentBase indexRange="759-1134">
          <Initialization range="0-758"/>
        </SegmentBase>
      </Representation>
      <Representation id="5" width="426" height="240" bandwidth="242000" codecs="avc1.4d401e">
        <BaseURL>cmaf.0.240.H_264.cmfv</BaseURL>
        <SegmentBase indexRange="759-1134">
          <Initialization range="0-758"/>
        </SegmentBase>
      </Representation>
    </AdaptationSet>
    <AdaptationSet mimeType="audio/mp4" lang="eng" segmentAlignment="0">
      <Representation id="6" bandwidth="96000" audioSamplingRate="48000" codecs="mp4a.40.2">
        <BaseURL>cmaf.0.audio.cmfa</BaseURL>
        <SegmentBase indexRange="658-1033">
          <Initialization range="0-657"/>
        </SegmentBase>
      </Representation>
    </AdaptationSet>
  </Period>
</MPD>

However the parsed Manifest when I console.log getBitrateInfoListFor('video') only has one quality level at 4000000

Is this the right way of going around bundling multiple codec types in a manifest?

[dsilhavy]

Different codecs (H.264 and H.265) should be put in different AdaptationSets. Otherwise this can cause problems on the client side when switching between the different Representations with different codecs. For priorization of one AdaptationSet over another one we support the selectionPriority attribute:

specifies the selection priority for the described data structures, i.e. the one described by the containing element. In the absence of other information, higher numbers are the preferred selection over lower numbers.

For example:

<AdaptationSet id="4" contentType="video" maxWidth="768" maxHeight="576" selectionPriority="1" frameRate="12800/512" subsegmentAlignment="true" par="4:3">
 <AdaptationSet id="10" contentType="video" maxWidth="768" maxHeight="576" selectionPriority="2" frameRate="1000000/40000" subsegmentAlignment="true" par="4:3">

There is also the option to use setInitialMediaSettingsFor to change the default track selection mechanism