dcerouter_112602:/var/www/iOrbiter# svdrpsend -p 2001 help pute
220 dcerouter SVDRP VideoDiskRecorder 1.7.22; Mon May 28 23:21:29 2012; UTF-8
214-PUTE [ file ]
214-    Put data into the EPG list. The data entered has to strictly follow the
214-    format defined in vdr(5) for the 'epg.data' file.  A '.' on a line
214-    by itself terminates the input and starts processing of the data (all
214-    entered data is buffered until the terminating '.' is seen).
214-    If a file name is given, epg data will be read from this file (which
214-    must be accessible under the given name from the machine VDR is running
214-    on). In case of file input, no terminating '.' shall be given.
214 End of HELP info

   EPG DATA
       The  file  epg.data  contains  the  EPG data in an easily parsable format.  The first character of each line
       defines what kind of data this line contains.

       The following tag characters are defined:

       C   <channel id> <channel name>
       E   <event id> <start time> <duration> <table id> <version>
       T   <title>
       S   <short text>
       D   <description>
       G   <genre> <genre>...
       R   <parental rating>
       X   <stream> <type> <language> <descr>
       V   <vps time>
       e
       c

       Lowercase characters mark the end of a sequence that was started by the corresponding  uppercase  character.
       The  outer  frame  consists of a sequence of one or more C...c (Channel) entries. Inside these any number of
       E...e (Event) entries are allowed.  All other tags are optional (although every event should at least have a
       T entry).

       There may be several X tags, depending on the number of tracks (video, audio etc.)  the event provides.

       <channel id>        is the "channel ID", made up from the parameters defined in 'channels.conf'
       <channel name>      is the "name" as in 'channels.conf' (for information only, may be left out)
       <event id>          is a 32 bit unsigned int, uniquely identifying this event
       <start time>        is the time (as a time_t integer) in UTC when this event starts
       <duration>          is the time (in seconds) that this event will take
       <table id>          is a hex number that indicates the table this event is contained in (if this is left empty or 0 this event will not be overwritten or modified by data that comes from the DVB stream)
       <version>           is a hex number that indicates the event's version number inside its table (optional, ignored when reading EPG data)
       <title>             is the title of the event
       <short text>        is the short text of the event (typically the name of the episode etc.)
       <description>       is the description of the event (any '|' characters will be interpreted as newlines)
       <genre>             is a two digit hex code, as defined in  ETSI EN 300 468, table 28 (up to 4 genre codes are supported)
       <parental rating>   is the minimum age of the intended audience
       <stream>            is the stream content (1 = MPEG2 video, 2 = MP2 audio, 3 = subtitles, 4 = AC3 audio, 5 = H.264 video, 6 = HEAAC audio)
       <type>              is the stream type according to ETSI EN 300 468
       <language>          is the three letter language code (optionally two codes, separated by '+')
       <descr>             is the description of this stream component
       <vps time>          is the Video Programming Service time of this event

       This file will be read at program startup in order to restore the results of previous EPG scans.

       Note that the event id that comes from the DVB data stream is actually just 16 bit wide. The internal repre‐
       sentation in VDR allows for 32 bit to be used, so that external tools can generate EPG data that is  guaran‐
       teed not to collide with the ids of existing data.