Verifying MPEG-DASH test streams on a remote HTTP server
This example describes how to verify that Dolby Digital Plus bitstreams are correctly multiplexed into the MPEG-DASH format. The multiplexed MPEG-DASH streams for testing are stored on a remote HTTP server.
Procedure
-
Record the URL where the .mpd
file in the table is located.
Input test signals Description - ChID_voices_51_256_ddp.mpd
- ChID_voices_51_256_ddp_A.mp4
- ChID_voices_51_256_ddp_V.mp4
MPEG-DASH On Demand streams multiplexed from one pair of video and audio streams -
Run this command:
mp4validator --input http://192.168.0.1/Dolby_Digital_Plus_Content_Creation_Kit_v1.1/Test_Signals/muxed_streams/DASH/OnDemand/HPL40_25fps/channel_id/51/ChID_voices_51_256_ddp.mpd --output-folder tmp >logfile.txt
-
The verification process generates the files
listed in the table.
Output files Descriptions tmp\AS0_5177248.h264 H.264 file output from MP4Validator, named using the convention AS<AdaptionSetIndex_bitrate>.h264 tmp\AS1_256000.ec3 Dolby Digital Plus file output from MP4Validator, named using the convention AS<AdaptionSetIndex_bitrate>.ec3 tmp\0_1_index.m4s
tmp\1_2_index.m4s
tmp\0_1_segment_XX.m4s
tmp\1_2_segment_XX.m4s
Temporary segmented MP4 files that are downloaded from the HTTP server, named AdaptionSetIndex_RepresentationIndex _segment_SegmentIndex.m4s tmp\local.mpd Associated MPEG-DASH MPD file tmp\tmp.py Temporary Python script used by MP4Validator to automatically download the segmented MP4 files from the HTTP server logfile.txt Log file - Verify the logfile to ensure that no errors are reported by the tool.