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-320x240-vp9-opus-webm-...

24 lines
1.5 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">
[DASH][WebM] Fix subsegmentAlignment not set problem MuxerListener::OnNewSegment was not sent for WebM SingleSegmentSegmenter. Change-Id: Iecae84e7a7c1a8a4d3f577158fa286b9c9959934
2018-01-29 19:04:09 +00:00
<AdaptationSet id="0" contentType="audio" subsegmentAlignment="true">
Integrate CueAlignmentHandler Also changed ChunkingHandler to be one-one handler. Issue: #355 Change-Id: Ie98a96bcc0ddded347699c9f333f604826976d11
2018-03-20 17:12:18 +00:00
<Representation id="0" bandwidth="76531" codecs="opus" mimeType="audio/webm" audioSamplingRate="48000">
Handle preroll and codec_delay when tranmuxing opus Closes Issue #102 Change-Id: I26aa56a63c17c85298311cc17963dd26f26e501e
2016-05-05 22:26:48 +00:00
<AudioChannelConfiguration schemeIdUri="urn:mpeg:dash:23003:3:audio_channel_configuration:2011" value="2"/>
<BaseURL>output_audio.webm</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="323-371" timescale="1000000" presentationTimeOffset="37000">
Handle preroll and codec_delay when tranmuxing opus Closes Issue #102 Change-Id: I26aa56a63c17c85298311cc17963dd26f26e501e
2016-05-05 22:26:48 +00:00
<Initialization range="0-322"/>
</SegmentBase>
</Representation>
</AdaptationSet>
[DASH][WebM] Fix subsegmentAlignment not set problem MuxerListener::OnNewSegment was not sent for WebM SingleSegmentSegmenter. Change-Id: Iecae84e7a7c1a8a4d3f577158fa286b9c9959934
2018-01-29 19:04:09 +00:00
<AdaptationSet id="1" contentType="video" width="320" height="240" frameRate="1000000/34000" subsegmentAlignment="true" par="16:9">
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
<Representation id="1" bandwidth="203360" codecs="vp9" mimeType="video/webm" sar="427:320">
Update end to end test with vpx packaging Change-Id: I70886693b5ad7d4c52170e57901c2437eba69214
2016-01-09 00:18:52 +00:00
<BaseURL>output_video.webm</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="302-350" 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-301"/>
Update end to end test with vpx packaging Change-Id: I70886693b5ad7d4c52170e57901c2437eba69214
2016-01-09 00:18:52 +00:00
</SegmentBase>
</Representation>
</AdaptationSet>
</Period>
</MPD>