1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
|
; This is the official configuration file example that
; serves as documentation for the config file reader.
;
; As you can see, comments are defined by semicolons.
;
; The format is called INFO format, and defined by boost property_tree:
; http://www.boost.org/doc/libs/1_41_0/doc/html/boost_propertytree/parsers.html#boost_propertytree.parsers.info_parser
; It consists of six mandatory sections, whose relative order in this
; file are of no importance.
; In case of questions or ambiguities, the documentation for the
; command-line configuration interface still mostly applies.
; The general section defines global multiplex parameters.
general {
; the DAB Transmission mode (values 1-4 accepted)
dabmode 2
; the number of ETI frames to generate (set to 0 to get an unlimited number)
nbframes 10
; boolean fileds can accept either false or true as values:
; Enable TCPLog on port 12222
tcplog false
; Write the SCCA field useful for the Factum ETI analyser
writescca false
; Enable timestamp definition necessary for SFN
; This also enables time encoding using the MNSC.
tist false
}
; Some ensemble parameters
ensemble {
id 20479
ecc 1249 ; Extended Country Code (decimal)
label "TuxMux"
}
; Definition of DAB services
services {
; Each service has it's own unique identifier, that is
; only used throughout the configuration file
funk {
label "Funk"
pty 0
language 0
; also supports id
}
luschtig {
label "Luschtig"
; pty, language and id can be omitted, and will take default values
}
}
; The subchannels are defined in the corresponding section.
; supported types are : audio, bridge, data, enhancedpacket,
dabplus, dmb, packet, test
subchannels {
funk {
type audio
inputfile "funk.mp2"
nonblock false
bitrate 128
id 10
}
luschtig {
type audio
inputfile "luschtig.mp2"
nonblock false
bitrate 128
id 3
}
}
; For now, each component links one service to one subchannel
components {
; the component unique identifiers are not used anywhere, but
; are useful to disambiguate different components.
funky {
service funk
subchannel funk
}
luschtigy {
service luschtig
subchannel luschtig
}
}
; A list of outputs, in the format
; unique_id "uri"
outputs {
foobar "fifo:///dev/stdout?type=raw"
}
|
