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/opus-vp9-mp4-with-encryption/output.mpd

32 lines
2.3 KiB
Plaintext
Raw Normal View History

Update end to end test with vpx packaging Change-Id: I70886693b5ad7d4c52170e57901c2437eba69214
2016-01-09 00:18:52 +00:00
<?xml version="1.0" encoding="UTF-8"?>
Update repo url in version string Issue #103 Change-Id: Iec7db3d155c81cf989f1078ed32692f8e037aa65
2016-05-20 21:28:13 +00:00
<!--Generated with https://github.com/google/shaka-packager version <tag>-<hash>-<test>-->
Generate a more accurate time in Period@duration Chrome internally uses time accurate to microseconds, which is implemented per MSE spec (https://www.w3.org/TR/media-source/). Generate Period@duration with better precision to avoid possible buffered range gaps in Chrome (possibly other browsers too), which may lead to other problems like playback stall. b/74238961 Fixes #368. Change-Id: I357a0f62b67f75c7ca044bb99ea4e3c8bbb6fecd
2018-04-02 23:53:29 +00:00
<MPD xmlns="urn:mpeg:dash:schema:mpd:2011" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xlink="http://www.w3.org/1999/xlink" 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.7360000610351562S">
Fix schematron validation problem for live - From DASH spec 2014, MPD@publishTime and Period@id are required for 'dynamic' MPD. - Period@id is always set to "0". - MPD@publishTime is set to the time when the MPD is output. Issue #55 Change-Id: I5e50aa11067176e69a2343fbc82ca42129703e1b
2016-01-11 23:58:02 +00:00
<Period id="0">
Fixed a Opus in Mp4 parsing problem - Also added end to end test in packager_test.py Closes Issue #83 Change-Id: I7a8e695a36e654507b75d558710db1ce8867a916
2016-06-01 23:28:56 +00:00
<AdaptationSet id="0" contentType="audio" subsegmentAlignment="true">
Enable generate_dash_if_iop_compliant_mpd by default This will move ContentProtection element from Representation to AdaptationSet. Shaka Player already supports AdaptationSet switching urn:mpeg:dash:adaptation-set-switching:2016; ExoPlayer does not support it yet. Filed https://github.com/google/ExoPlayer/issues/2431 to track the issue. (ExoPlayer does not like having ContentProtection in Representation anyway) Closes b/34691105 Change-Id: I69d0a4d0e15a912a35c8b2686620419a28e4cc99
2017-02-09 00:47:59 +00:00
<ContentProtection value="cenc" schemeIdUri="urn:mpeg:dash:mp4protection:2011" cenc:default_KID="31323334-3536-3738-3930-313233343536"/>
<ContentProtection schemeIdUri="urn:uuid:1077efec-c0b2-4d02-ace3-3c1e52e2fb4b">
<cenc:pssh>AAAANHBzc2gBAAAAEHfv7MCyTQKs4zweUuL7SwAAAAExMjM0NTY3ODkwMTIzNDU2AAAAAA==</cenc:pssh>
</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="86874" codecs="opus" mimeType="audio/mp4" audioSamplingRate="48000">
Fixed a Opus in Mp4 parsing problem - Also added end to end test in packager_test.py Closes Issue #83 Change-Id: I7a8e695a36e654507b75d558710db1ce8867a916
2016-06-01 23:28:56 +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-320x240-vp9-opus-audio.mp4</BaseURL>
Add support for seek preroll in AAC and other audio codecs Closes #452. Change-Id: I0f648c4fa6c861540b050a5b4e9878987c8383e5
2018-08-21 22:52:09 +00:00
<SegmentBase indexRange="947-1014" timescale="1000000" presentationTimeOffset="37000">
<Initialization range="0-946"/>
Fixed a Opus in Mp4 parsing problem - Also added end to end test in packager_test.py Closes Issue #83 Change-Id: I7a8e695a36e654507b75d558710db1ce8867a916
2016-06-01 23:28:56 +00:00
</SegmentBase>
</Representation>
</AdaptationSet>
<AdaptationSet id="1" contentType="video" width="320" height="240" frameRate="1000000/34000" subsegmentAlignment="true" par="16:9">
Enable generate_dash_if_iop_compliant_mpd by default This will move ContentProtection element from Representation to AdaptationSet. Shaka Player already supports AdaptationSet switching urn:mpeg:dash:adaptation-set-switching:2016; ExoPlayer does not support it yet. Filed https://github.com/google/ExoPlayer/issues/2431 to track the issue. (ExoPlayer does not like having ContentProtection in Representation anyway) Closes b/34691105 Change-Id: I69d0a4d0e15a912a35c8b2686620419a28e4cc99
2017-02-09 00:47:59 +00:00
<ContentProtection value="cenc" schemeIdUri="urn:mpeg:dash:mp4protection:2011" cenc:default_KID="31323334-3536-3738-3930-313233343536"/>
<ContentProtection schemeIdUri="urn:uuid:1077efec-c0b2-4d02-ace3-3c1e52e2fb4b">
<cenc:pssh>AAAANHBzc2gBAAAAEHfv7MCyTQKs4zweUuL7SwAAAAExMjM0NTY3ODkwMTIzNDU2AAAAAA==</cenc:pssh>
</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="1" bandwidth="231745" codecs="vp09.00.10.08.01.02.02.02.00" mimeType="video/mp4" sar="427:320">
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-320x240-vp9-opus-video.mp4</BaseURL>
Remove pto_adjustment flag This flag was introduced to workaround a rounding error in Chrome (probably in other browsers too). Also although this flag avoids the first frame of a Period to be dropped due to rounding error but it could cause the last frame of a Period to be dropped. Now that we use a high precision Period@duration, we do not expect to see rounding errors any more. The player would be a better place for the workaround even if it is still needed. Related issue: #368. Change-Id: I3bd517ecc6d548ff62e0c13394edb49d4bc68e8f
2018-04-09 18:47:29 +00:00
<SegmentBase indexRange="1063-1130" timescale="1000000" presentationTimeOffset="37000">
Support v1 vp9 in iso-bmff - Implemented according to v1.0 spec @ https://www.webmproject.org/vp9/mp4/ - v0 is no longer supported Change-Id: I189c813d788400beda797eea7da943a83dfa7d79
2017-04-24 18:50:49 +00:00
<Initialization range="0-1062"/>
Update end to end test with vpx packaging Change-Id: I70886693b5ad7d4c52170e57901c2437eba69214
2016-01-09 00:18:52 +00:00
</SegmentBase>
</Representation>
</AdaptationSet>
</Period>
</MPD>