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/bear-640x360-av-live-static...

50 lines
3.0 KiB
Plaintext
Raw Permalink Normal View History

Share chunkers from the same input except for WVM Updated test files and added end to end tests for AdCues. Change-Id: I28f57c2f0d15f65fa04f599fae446a5c1373bf47
2018-01-10 00:04:40 +00:00
<?xml version="1.0" encoding="UTF-8"?>
<!--Generated with https://github.com/google/shaka-packager version <tag>-<hash>-<test>-->
Do not force earliest_presentation_time to 0 for VOD Instead, the actual earliest presentation time is used except for the first segment if there is an offset between presentation time (pts) and decoding time (dts). Chrome (as of v66) reports dts instead of pts in buffered ranges in MSE API. To avoid breaking Chrome, the earliest_presentation_time of the first segment is set to its dts as Chrome does not like negative values for adjusted dts = dts + Period@start (0 for the first period) - presentationTimeOffset (earliest_presentation_time). Fixes #303. Change-Id: I5ca80e05d5570961400499436f2bcc01f06e69e0
2018-03-27 16:27:17 +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-live:2011" minBufferTime="PT2S" type="static" mediaPresentationDuration="PT2.802799940109253S">
<Period id="0" duration="PT2.0687333333333333S">
Share chunkers from the same input except for WVM Updated test files and added end to end tests for AdCues. Change-Id: I28f57c2f0d15f65fa04f599fae446a5c1373bf47
2018-01-10 00:04:40 +00:00
<AdaptationSet id="0" contentType="video" width="640" height="360" frameRate="30000/1001" segmentAlignment="true" par="16:9">
Use max bitrate in Representation@bandwidth instead of average bitrate According to 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. This suggests that max bitrate should be used instead of average bitrate. Also cleaned up BandwidthEstimator code. Fixes #376. Change-Id: Ibf5896394c5c6bb820849771a2129c59202d2273
2018-04-13 18:48:11 +00:00
<Representation id="0" bandwidth="974122" codecs="avc1.64001e" mimeType="video/mp4" sar="1:1">
Share chunkers from the same input except for WVM Updated test files and added end to end tests for AdCues. Change-Id: I28f57c2f0d15f65fa04f599fae446a5c1373bf47
2018-01-10 00:04:40 +00:00
<SegmentTemplate timescale="30000" initialization="output_video-init.mp4" media="output_video-$Number$.m4s" startNumber="1">
<SegmentTimeline>
Do not force earliest_presentation_time to 0 for VOD Instead, the actual earliest presentation time is used except for the first segment if there is an offset between presentation time (pts) and decoding time (dts). Chrome (as of v66) reports dts instead of pts in buffered ranges in MSE API. To avoid breaking Chrome, the earliest_presentation_time of the first segment is set to its dts as Chrome does not like negative values for adjusted dts = dts + Period@start (0 for the first period) - presentationTimeOffset (earliest_presentation_time). Fixes #303. Change-Id: I5ca80e05d5570961400499436f2bcc01f06e69e0
2018-03-27 16:27:17 +00:00
<S t="0" d="32032"/>
<S t="32032" d="30030"/>
Share chunkers from the same input except for WVM Updated test files and added end to end tests for AdCues. Change-Id: I28f57c2f0d15f65fa04f599fae446a5c1373bf47
2018-01-10 00:04:40 +00:00
</SegmentTimeline>
</SegmentTemplate>
</Representation>
</AdaptationSet>
<AdaptationSet id="1" contentType="audio" segmentAlignment="true">
Use max bitrate in Representation@bandwidth instead of average bitrate According to 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. This suggests that max bitrate should be used instead of average bitrate. Also cleaned up BandwidthEstimator code. Fixes #376. Change-Id: Ibf5896394c5c6bb820849771a2129c59202d2273
2018-04-13 18:48:11 +00:00
<Representation id="1" bandwidth="175884" codecs="mp4a.40.2" mimeType="audio/mp4" audioSamplingRate="44100">
Share chunkers from the same input except for WVM Updated test files and added end to end tests for AdCues. Change-Id: I28f57c2f0d15f65fa04f599fae446a5c1373bf47
2018-01-10 00:04:40 +00:00
<AudioChannelConfiguration schemeIdUri="urn:mpeg:dash:23003:3:audio_channel_configuration:2011" value="2"/>
<SegmentTemplate timescale="44100" initialization="output_audio-init.mp4" media="output_audio-$Number$.m4s" startNumber="1">
<SegmentTimeline>
Integrate CueAlignmentHandler Also changed ChunkingHandler to be one-one handler. Issue: #355 Change-Id: Ie98a96bcc0ddded347699c9f333f604826976d11
2018-03-20 17:12:18 +00:00
<S t="0" d="45056"/>
<S t="45056" d="44032"/>
<S t="89088" d="2048"/>
Share chunkers from the same input except for WVM Updated test files and added end to end tests for AdCues. Change-Id: I28f57c2f0d15f65fa04f599fae446a5c1373bf47
2018-01-10 00:04:40 +00:00
</SegmentTimeline>
</SegmentTemplate>
</Representation>
</AdaptationSet>
</Period>
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
<Period id="1" duration="PT.7340666666666666S">
Integrate CueAlignmentHandler Also changed ChunkingHandler to be one-one handler. Issue: #355 Change-Id: Ie98a96bcc0ddded347699c9f333f604826976d11
2018-03-20 17:12:18 +00:00
<AdaptationSet id="0" contentType="video" width="640" height="360" frameRate="30000/1001" segmentAlignment="true" par="16:9">
<Representation id="0" bandwidth="869044" codecs="avc1.64001e" mimeType="video/mp4" sar="1:1">
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
<SegmentTemplate timescale="30000" presentationTimeOffset="62062" initialization="output_video-init.mp4" media="output_video-$Number$.m4s" startNumber="3">
Share chunkers from the same input except for WVM Updated test files and added end to end tests for AdCues. Change-Id: I28f57c2f0d15f65fa04f599fae446a5c1373bf47
2018-01-10 00:04:40 +00:00
<SegmentTimeline>
Integrate CueAlignmentHandler Also changed ChunkingHandler to be one-one handler. Issue: #355 Change-Id: Ie98a96bcc0ddded347699c9f333f604826976d11
2018-03-20 17:12:18 +00:00
<S t="62062" d="22022"/>
Share chunkers from the same input except for WVM Updated test files and added end to end tests for AdCues. Change-Id: I28f57c2f0d15f65fa04f599fae446a5c1373bf47
2018-01-10 00:04:40 +00:00
</SegmentTimeline>
</SegmentTemplate>
</Representation>
</AdaptationSet>
Integrate CueAlignmentHandler Also changed ChunkingHandler to be one-one handler. Issue: #355 Change-Id: Ie98a96bcc0ddded347699c9f333f604826976d11
2018-03-20 17:12:18 +00:00
<AdaptationSet id="1" contentType="audio" segmentAlignment="true">
<Representation id="1" bandwidth="105634" codecs="mp4a.40.2" mimeType="audio/mp4" audioSamplingRate="44100">
<AudioChannelConfiguration schemeIdUri="urn:mpeg:dash:23003:3:audio_channel_configuration:2011" value="2"/>
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
<SegmentTemplate timescale="44100" presentationTimeOffset="91231" initialization="output_audio-init.mp4" media="output_audio-$Number$.m4s" startNumber="4">
Share chunkers from the same input except for WVM Updated test files and added end to end tests for AdCues. Change-Id: I28f57c2f0d15f65fa04f599fae446a5c1373bf47
2018-01-10 00:04:40 +00:00
<SegmentTimeline>
Integrate CueAlignmentHandler Also changed ChunkingHandler to be one-one handler. Issue: #355 Change-Id: Ie98a96bcc0ddded347699c9f333f604826976d11
2018-03-20 17:12:18 +00:00
<S t="91136" d="30720"/>
Share chunkers from the same input except for WVM Updated test files and added end to end tests for AdCues. Change-Id: I28f57c2f0d15f65fa04f599fae446a5c1373bf47
2018-01-10 00:04:40 +00:00
</SegmentTimeline>
</SegmentTemplate>
</Representation>
</AdaptationSet>
</Period>
</MPD>