Config files

Content Config Files

There is one config file for each VoD content resource. It can be used with multiple manifests, and should include all the representations that should be accessible (as a comma-separated list).

All representations for the same ContentType must have the same track_timescale in the init segments. This timescale should be in the config file, and is extracted automatically by the dashanalyzer.py tool.

The config-file testpic_2s.cfg for all the MPDs with testcontent in testpic_2s must include all the representations used in different MPDs in order for the segments to be properly processed.

A new version, 1.1, was introduced to support SegmentTimeline by having a side file (.dat file) with the segment durations of all segments. Such a file can be generated by the VoD analyzer.

[General]
version = 1.1

[Setup]
default_tsbd_secs = 300
segment_duration_s = 2
nr_segments_in_loop = 1800
first_segment_in_loop = 1

[video]
representations = V300
timescale = 90000
total_duration = 324000000
dat_file = testpic_2s_video.dat

[audio]
representations = A48
timescale = 48000
total_duration = 172800000
dat_file = testpic_2s_audio.dat

[subtitles]
representations = S1,sub_eng,sub_swe,sub_eng_cap,S1_one_region,S1_two_regions,sub_ttml_qbb,sub_nor
timescale = 1000

Version 1.0 of the config file had less parameters. This is enough to support the $Number$-based template.

[General]
version = 1.0

[Setup]
default_tsbd_secs = 300
segment_duration_s = 2
first_segment_in_loop = 1
nr_segments_in_loop = 1800

[audio]
representations = A48
timescale = 48000

[video]
representations = V300
timescale = 90000

[subtitles]
representations = S1,sub_eng,sub_swe,sub_eng_cap,S1_one_region,S1_two_regions
timescale = 1000