Mirror-Tools
/
shaka-packager
mirror of https://github.com/shaka-project/shaka-packager.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
shaka-packager/packager/app/test/testdata/encryption-multi-keys/output.mpd

32 lines
2.2 KiB
Plaintext
Raw Permalink Normal View History

Generate two sample entries only if there is clear lead This addresses playready broken with clear lead = 0. clear lead != 0 is still broken with playready on Edge. We think it is likely an Edge bug, which does not support multiple sample entry boxes, thus does not support clear lead. b/37913785 Change-Id: I7adb77a913dccf669153b03b31b4a1e1c98d1cb0
2017-05-09 22:49:01 +00:00
<?xml version="1.0" encoding="UTF-8"?>
<!--Generated with https://github.com/google/shaka-packager version <tag>-<hash>-<test>-->
Put namespace URIs in DASH mpd only if needed Change-Id: I31284b665599a8ee8f0b1aa11b58d6797dbe2884
2018-09-18 19:05:11 +00:00
<MPD xmlns="urn:mpeg:dash:schema:mpd:2011" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:mpeg:dash:schema:mpd:2011 DASH-MPD.xsd" xmlns:cenc="urn:mpeg:cenc:2013" profiles="urn:mpeg:dash:profile:isoff-on-demand:2011" minBufferTime="PT2S" type="static" mediaPresentationDuration="PT2.7360665798187256S">
Generate two sample entries only if there is clear lead This addresses playready broken with clear lead = 0. clear lead != 0 is still broken with playready on Edge. We think it is likely an Edge bug, which does not support multiple sample entry boxes, thus does not support clear lead. b/37913785 Change-Id: I7adb77a913dccf669153b03b31b4a1e1c98d1cb0
2017-05-09 22:49:01 +00:00
<Period id="0">
<AdaptationSet id="0" contentType="video" width="640" height="360" frameRate="30000/1001" subsegmentAlignment="true" par="16:9">
Update Encrypted Tests to Use DiffDir This changes almost all encrypted tests to use DiffDir. The remaining un-updated tests are tests that won't match every time. Change-Id: I858bbaa0beea34887cc3100eb784aa2aecd5a0a5
2018-03-07 19:24:52 +00:00
<ContentProtection value="cenc" schemeIdUri="urn:mpeg:dash:mp4protection:2011" cenc:default_KID="20212223-2425-2627-2829-303132333435"/>
Generate two sample entries only if there is clear lead This addresses playready broken with clear lead = 0. clear lead != 0 is still broken with playready on Edge. We think it is likely an Edge bug, which does not support multiple sample entry boxes, thus does not support clear lead. b/37913785 Change-Id: I7adb77a913dccf669153b03b31b4a1e1c98d1cb0
2017-05-09 22:49:01 +00:00
<ContentProtection schemeIdUri="urn:uuid:1077efec-c0b2-4d02-ace3-3c1e52e2fb4b">
Update Encrypted Tests to Use DiffDir This changes almost all encrypted tests to use DiffDir. The remaining un-updated tests are tests that won't match every time. Change-Id: I858bbaa0beea34887cc3100eb784aa2aecd5a0a5
2018-03-07 19:24:52 +00:00
<cenc:pssh>AAAARHBzc2gBAAAAEHfv7MCyTQKs4zweUuL7SwAAAAIQERITFBUWFxgZICEiIyQlICEiIyQlJicoKTAxMjM0NQAAAAA=</cenc:pssh>
Generate two sample entries only if there is clear lead This addresses playready broken with clear lead = 0. clear lead != 0 is still broken with playready on Edge. We think it is likely an Edge bug, which does not support multiple sample entry boxes, thus does not support clear lead. b/37913785 Change-Id: I7adb77a913dccf669153b03b31b4a1e1c98d1cb0
2017-05-09 22:49:01 +00:00
</ContentProtection>
Fix bitrate for DASH on-demand profile too Removed the logic in MuxerListener to estimate bandwidth from file size and duration, since it is not compliant to the spec. MpdBuilder will estimate bandwidth from segment size and duration if bandwidth is not specified in MediaInfo. Here is the statement from DASH spec (23009-1:2014): Consider a hypothetical constant bitrate channel of bandwidth with the value of this attribute in bits per second (bps). Then, if the Representation is continuously delivered at this bitrate, starting at any SAP that is indicated either by @startwithsap or by any Segment Index box, a client can be assured of having enough data for continuous playout providing playout begins after @minbuffertime * @bandwidth bits have been received (i.e. at time @minbuffertime after the first bit is received). For dependent Representations this value specifies the bandwidth according to the above definition for the aggregation of this Representation and all complementary Representations. Fixes #376. Change-Id: I0fddce39e709d0cded0a4c9ae59adbbcc97ec5ea
2018-04-24 00:20:00 +00:00
<Representation id="0" bandwidth="977743" codecs="avc1.64001e" mimeType="video/mp4" sar="1:1">
Remove Test File Index in packager_test.py Instead of using the test file's index in a list to create the output name, use the original filename and the descriptor. This caused some problems with file name collisions when some tests were using the same name. That was fixed by changing the names. This will go away once they are transitioned to use DiffDir like the other tests. Change-Id: I0a4c480406705ca63fcea61c86c67d4a5f739295
2018-03-02 17:02:38 +00:00
<BaseURL>bear-640x360-video.mp4</BaseURL>
Add support for EditLists in ISO-BMFF - EditLists in input files are parsed and applied to sample timestamps. - An EditList will be inserted in the ISO-BMFF output if - There is an offset between the initial presentation timestamp (pts) and decoding timestamp (dts). Chrome, as of M67, still uses dts in buffered range API [1], which creates various problems when buffered range by pts does not align with buffered range by dts. There is another bug in Chrome that applies EditList to pts only [2]. This means that we can insert an EditList to align pts range and dts range. - MediaSamples have negative timestamps (e.g. for Audio Priming). You may notice the below change on some contents: - Some media duration is reduced by one or two frames. This is because EditList in the input file was ignored in the previous code, so video streams start with a zero dts and a non-zero pts; the smaller of dts and pts was used as the starting timestamp (related to the earlier workaround for Chrome's dts bug), so the calculated duration was actually a bit larger than the actual duration. Now with EditList applied, the initial pts is reduced to zero, so the media duration is also reduced to reflect the actual and correct media duration. It may also result in negative timestamps in TS/HLS Packed Audio, which will be addressed in a follow up CL. Fixes #112. Partially address b/110782437. [1] https://crbug.com/718641, fixed but behind MseBufferByPts. [2] https://crbug.com/354518. Chrome is planning to enable the fix for [1] before addressing this bug, so we are safe. Change-Id: I59317740ad3807ca66fa74b3a18fdf7f32c96aeb
2018-07-03 00:52:25 +00:00
<SegmentBase indexRange="1143-1210" timescale="30000">
<Initialization range="0-1142"/>
Generate two sample entries only if there is clear lead This addresses playready broken with clear lead = 0. clear lead != 0 is still broken with playready on Edge. We think it is likely an Edge bug, which does not support multiple sample entry boxes, thus does not support clear lead. b/37913785 Change-Id: I7adb77a913dccf669153b03b31b4a1e1c98d1cb0
2017-05-09 22:49:01 +00:00
</SegmentBase>
</Representation>
</AdaptationSet>
<AdaptationSet id="1" contentType="audio" subsegmentAlignment="true">
Update Encrypted Tests to Use DiffDir This changes almost all encrypted tests to use DiffDir. The remaining un-updated tests are tests that won't match every time. Change-Id: I858bbaa0beea34887cc3100eb784aa2aecd5a0a5
2018-03-07 19:24:52 +00:00
<ContentProtection value="cenc" schemeIdUri="urn:mpeg:dash:mp4protection:2011" cenc:default_KID="10111213-1415-1617-1819-202122232425"/>
Generate two sample entries only if there is clear lead This addresses playready broken with clear lead = 0. clear lead != 0 is still broken with playready on Edge. We think it is likely an Edge bug, which does not support multiple sample entry boxes, thus does not support clear lead. b/37913785 Change-Id: I7adb77a913dccf669153b03b31b4a1e1c98d1cb0
2017-05-09 22:49:01 +00:00
<ContentProtection schemeIdUri="urn:uuid:1077efec-c0b2-4d02-ace3-3c1e52e2fb4b">
Update Encrypted Tests to Use DiffDir This changes almost all encrypted tests to use DiffDir. The remaining un-updated tests are tests that won't match every time. Change-Id: I858bbaa0beea34887cc3100eb784aa2aecd5a0a5
2018-03-07 19:24:52 +00:00
<cenc:pssh>AAAARHBzc2gBAAAAEHfv7MCyTQKs4zweUuL7SwAAAAIQERITFBUWFxgZICEiIyQlICEiIyQlJicoKTAxMjM0NQAAAAA=</cenc:pssh>
Generate two sample entries only if there is clear lead This addresses playready broken with clear lead = 0. clear lead != 0 is still broken with playready on Edge. We think it is likely an Edge bug, which does not support multiple sample entry boxes, thus does not support clear lead. b/37913785 Change-Id: I7adb77a913dccf669153b03b31b4a1e1c98d1cb0
2017-05-09 22:49:01 +00:00
</ContentProtection>
Add support for EditLists in ISO-BMFF - EditLists in input files are parsed and applied to sample timestamps. - An EditList will be inserted in the ISO-BMFF output if - There is an offset between the initial presentation timestamp (pts) and decoding timestamp (dts). Chrome, as of M67, still uses dts in buffered range API [1], which creates various problems when buffered range by pts does not align with buffered range by dts. There is another bug in Chrome that applies EditList to pts only [2]. This means that we can insert an EditList to align pts range and dts range. - MediaSamples have negative timestamps (e.g. for Audio Priming). You may notice the below change on some contents: - Some media duration is reduced by one or two frames. This is because EditList in the input file was ignored in the previous code, so video streams start with a zero dts and a non-zero pts; the smaller of dts and pts was used as the starting timestamp (related to the earlier workaround for Chrome's dts bug), so the calculated duration was actually a bit larger than the actual duration. Now with EditList applied, the initial pts is reduced to zero, so the media duration is also reduced to reflect the actual and correct media duration. It may also result in negative timestamps in TS/HLS Packed Audio, which will be addressed in a follow up CL. Fixes #112. Partially address b/110782437. [1] https://crbug.com/718641, fixed but behind MseBufferByPts. [2] https://crbug.com/354518. Chrome is planning to enable the fix for [1] before addressing this bug, so we are safe. Change-Id: I59317740ad3807ca66fa74b3a18fdf7f32c96aeb
2018-07-03 00:52:25 +00:00
<Representation id="1" bandwidth="133663" codecs="mp4a.40.2" mimeType="audio/mp4" audioSamplingRate="44100">
Generate two sample entries only if there is clear lead This addresses playready broken with clear lead = 0. clear lead != 0 is still broken with playready on Edge. We think it is likely an Edge bug, which does not support multiple sample entry boxes, thus does not support clear lead. b/37913785 Change-Id: I7adb77a913dccf669153b03b31b4a1e1c98d1cb0
2017-05-09 22:49:01 +00:00
<AudioChannelConfiguration schemeIdUri="urn:mpeg:dash:23003:3:audio_channel_configuration:2011" value="2"/>
Remove Test File Index in packager_test.py Instead of using the test file's index in a list to create the output name, use the original filename and the descriptor. This caused some problems with file name collisions when some tests were using the same name. That was fixed by changing the names. This will go away once they are transitioned to use DiffDir like the other tests. Change-Id: I0a4c480406705ca63fcea61c86c67d4a5f739295
2018-03-02 17:02:38 +00:00
<BaseURL>bear-640x360-audio.mp4</BaseURL>
Add support for EditLists in ISO-BMFF - EditLists in input files are parsed and applied to sample timestamps. - An EditList will be inserted in the ISO-BMFF output if - There is an offset between the initial presentation timestamp (pts) and decoding timestamp (dts). Chrome, as of M67, still uses dts in buffered range API [1], which creates various problems when buffered range by pts does not align with buffered range by dts. There is another bug in Chrome that applies EditList to pts only [2]. This means that we can insert an EditList to align pts range and dts range. - MediaSamples have negative timestamps (e.g. for Audio Priming). You may notice the below change on some contents: - Some media duration is reduced by one or two frames. This is because EditList in the input file was ignored in the previous code, so video streams start with a zero dts and a non-zero pts; the smaller of dts and pts was used as the starting timestamp (related to the earlier workaround for Chrome's dts bug), so the calculated duration was actually a bit larger than the actual duration. Now with EditList applied, the initial pts is reduced to zero, so the media duration is also reduced to reflect the actual and correct media duration. It may also result in negative timestamps in TS/HLS Packed Audio, which will be addressed in a follow up CL. Fixes #112. Partially address b/110782437. [1] https://crbug.com/718641, fixed but behind MseBufferByPts. [2] https://crbug.com/354518. Chrome is planning to enable the fix for [1] before addressing this bug, so we are safe. Change-Id: I59317740ad3807ca66fa74b3a18fdf7f32c96aeb
2018-07-03 00:52:25 +00:00
<SegmentBase indexRange="1019-1086" timescale="44100">
<Initialization range="0-1018"/>
Generate two sample entries only if there is clear lead This addresses playready broken with clear lead = 0. clear lead != 0 is still broken with playready on Edge. We think it is likely an Edge bug, which does not support multiple sample entry boxes, thus does not support clear lead. b/37913785 Change-Id: I7adb77a913dccf669153b03b31b4a1e1c98d1cb0
2017-05-09 22:49:01 +00:00
</SegmentBase>
</Representation>
</AdaptationSet>
</Period>
</MPD>