[linux-dvb] Re: some libdvbcfg wishes, preset format

[Andrew de Quincey]

Hi, here is an updated description of the multiplexes.conf format - comments please...

/**
 * The dvbcfg_multiplex file consists of multiple sections, each describing a
 * particular multiplex or a service belonging to a multiplex. Its format is as
 * follows:
 * [dvbmultiplexes]
 * version=0.1
 * date=<unixdate>
 *
 * [m]
 * gmid = <GMID of this multiplex>
 * d = <delivery specific parameters>
 *
 * [s]
 * usid= <USID of this service>
 * name= <name of this service>
 * sname= <short name of this service>
 * pname= <provider name of this service>
 * flags= <service specific flags>
 * ca= <list of ca systems supported by this multiplex>
 * zap= <list of pids and their types for accelerated channel locking>
 * pmt= <list of pids and their types used as a supplement/replacement to the standard PMT SI tables>
 *
 * There may only be one [dvbmultiplex] section, and it must be the first section within the file.
 *
 * There can be multiple [m] and [s] sections in any one file. A [s] belongs
 * to the most recent preceding [m] section.
 *
 * All keys within the sections are mandatory, except for the following:
 * flags, sname, pname, ca, zap, pmt.
 *
 * GMID and USID are described in dvbcfg_common.h.
 *
 * The <delivery specific parameters> vary depending on the source_type of the multiplex. They are as follows:
 * DVBS: <frequency> <inversion> <polarization> <symbol_rate> <fec_inner>
 * DVBC: <frequency> <inversion> <symbol_rate> <fec_inner> <modulation>
 * DVBT: <frequency> <inversion> <bandwidth> <code_rate_HP> <code_rate_LP> <constellation> <tranmission_mode> <guard_interval> <hierarchy_information>
 * ATSC: <frequency> <inversion> <modulation>
 *
 * All numerical values are in the units used in the "struct dvb_frontend_parameters".
 * For other parameters, the numerical value as defined in the enumerations in frontend.h is used.
 *
 * Currently only the flag "nopmt" is defined for the <service specific flags>. If this is present, the
 * PMT should be ignored completely, and the pmt entries used instead.
 *
 * The <list of ca systems supported by this multiplex> is only used for encrypted services to identify the
 * type of CAM/subscription card the user must have in order to successfully decrypt a service. This is just
 * a list of numbers seperated by whitespace.
 *
 * Both zap and pmt have the same format: <pid>:<type>. <type> may either be one of the standard
 * PMT stream types as defined in ISO13818-1, table 2-29, or it may be one of the special values "_ac3", "_dts",
 * "_tt", or "_pcr".
 *
 * zap is to provide accelerated channel zapping. It gives a pre-extracted list of PIDs
 * (usually just audio, video, and pcr) so that a channel can be zapped to without having to wait for the
 * PAT or PMT tables. They should be verified against the PAT/PMT when it is received, in case they
 * have changed in the meantime. Use of these is optional.
 *
 * pmt gives a list of extra PID/type pairs for PIDS that are for some reason missing from the PMT
 * table for a channel. If the "nopmt" flag is also set, these entries will be used instead of a PMT.
 * If not, they will be used in addition to the PMT (however the pmt entries should override any clashing
 * entries in the PMT).
 *
 * This file format can also be used for "seed" transponders - if this is the case, the file should consist
 * only of [m] sections.
 *
 * Comments begin with '#' - any characters after this will be ignored
 * to the end of the line.
 *
 * Example:
 * [dvbmultiplexes]
 * version=0.1
 * date=5798475834
 *
 * [m]
 * gmid=S5E:0x0001:0x002:0x000
 * d= 12345 0 H 27500000 9
 *
 * [s]
 * usid=0x0001:0x000
 * name=service 1
 * zap=0x55:_ac3 0x56:0x78 0x57:_pcr 0x59:0x01
 * pmt=0x100:_dts 0x101:_tt 0x102:0x76
 *
 * [s]
 * usid=0x0002:0x000
 * name=service 2
 * zap=0x55:_ac3 0x56:0x78 0x57:_pcr 0x59:0x01
 * pmt=0x100:_dts 0x101:_tt 0x102:0x76
 *
 * [m]
 * gmid=Cde-de-Berlin:0x0001:0x002:0x000
 * d = 12345 0 27500000 9 4
 */