Welcome to Linux Knowledge Base and Tutorial
"The place where you learn linux"
Mercy Corps

 Create an AccountHome | Submit News | Your Account  

Tutorial Menu
Linux Tutorial Home
Table of Contents

· Introduction to Operating Systems
· Linux Basics
· Working with the System
· Shells and Utilities
· Editing Files
· Basic Administration
· The Operating System
· The X Windowing System
· The Computer Itself
· Networking
· System Monitoring
· Solving Problems
· Security
· Installing and Upgrading
· Linux and Windows

Man Pages
Linux Topics
Test Your Knowledge

Site Menu
Site Map
Copyright Info
Terms of Use
Privacy Info
Masthead / Impressum
Your Account

Private Messages

News Archive
Submit News
User Articles
Web Links


The Web

Who's Online
There are currently, 76 guest(s) and 0 member(s) that are online.

You are an Anonymous user. You can register for free by clicking here




       This  page  describes the formats of the various files vdr
       uses to store configuration data and recordings.


       The file channels.conf contains the channel configuration.
       Each line defines either a group delimiter or a channel.

       A  group  delimiter  is  a line starting with a ':' as the
       very first character, followed by arbitrary text. Example:

       :First group

       Group delimiters may also be used to specify the number of
       the next channel.  To do this, the  character  '@'  and  a
       number must immediately follow the ':', as in

       :@201 First group

       The  given  number  must  be larger than the number of any
       previous channel (otherwise it is silently ignored).

       A group delimiter can also be used to just  set  the  next
       channel's  number,  without an explicit delimiter text, as


       Such a delimiter will not appear in the Channels menu.

       A channel definition is a line with  channel  data,  where
       the fields are separated by ':' characters. Example:


       The  line  number  of  a  channel definition (not counting
       group separators, and based on a possible previous  '@...'
       parameter)  defines  the channel's number in OSD menus and
       the timers.conf file.

       The fields in a  channel  definition  have  the  following
       meaning (from left to right):

       Name   The channel's name (if the name originally contains
              a ':' character it has to be replaced by '|').

              The transponder frequency (as an integer). For DVB-
              S  this value is in MHz. For DVB-C and DVB-T it can
              be given either in MHz, kHz or Hz (the actual value
              given will be multiplied by 1000 until it is larger
              I   Inversion (0, 1)
              M   Modulation (0, 16, 32, 64, 128, 256)
              T   Transmission mode (2, 8)
              V   Vertical polarization
              Y   Hierarchy (0, 1, 2, 4)
              The polarization parameters have no integer numbers
              following them.  This  is  for  compatibility  with
              files from older versions and also to keep the DVB-
              S entries as simple as possible.

              The special value  999  is  used  for  "automatic",
              which means the driver will automatically determine
              the proper value (if possible).

              An example of a parameter field for a DVB-T channel
              might look like this:


       Source The  signal  source  of this channel, as defined in
              the  file  sources.conf.   For  compatibility  with
              files  from  older  versions numeric values will be
              accepted and also written back correctly, but  they
              will  have  no meaning for the DiSEqC settings. You
              should replace the numerical values with the proper
              source identifiers defined in sources.conf.

       Srate  The  symbol  rate  of this channel (DVB-S and DVB-C

       VPID   The video PID (set to '0' for radio  channels,  '1'
              for  encrypted  radio  channels).   If this channel
              uses a separate PCR PID, it follows the VPID, sepa­
              rated by a plus sign, as in ...:164+17:...

       APID   The audio PID (either one number, or two, separated
              by a comma).  If this channel  also  carries  Dolby
              Digital  sound,  the  Dolby  PIDs  follow the audio
              PIDs,   separated   by   a   semicolon,    as    in

       TPID   The teletext PID.

       Conditional access
              An   integer  defining  how  this  channel  can  be
              0       Free To Air
              1...4   explicitly requires the DVB card with the given number
              >=100   requires a specific decryption method defined in ca.conf

       SID    The Service ID of this channel.

       The  components  of  this  string are the Source (S19.2E),
       Frequency (12188, MHz) and SID (12003) as  defined  above.
       The parts that are currently 0 are reserved for future use
       (the last part can be omitted if it is  0,  so  the  above
       example could also be written as S19.2E-0-12188-12003).
       The  channel ID  is  used  in the timers.conf and epg.data
       files to properly identify the channels.

       The file timers.conf contains the timer setup.  Each  line
       contains one timer definition, with individual fields sep­
       arated by ':' characters. Example:

       1:10:-T-----:2058:2150:50:5:Quarks & Co:

       The fields in a timer definition have the following  mean­
       ing (from left to right):

       Status Defines  whether  this  timer  is  inactive  (0) or
              active (1).   The  value  3  is  used  for  instant
              recordings.  Values other than these can be used by
              external programs to mark active timers and  recog­
              nize  if  the  user  has modified them. When a user
              modifes an active timer the status  field  will  be
              explicitly set to '1' (or '0', respectively, if the
              user deactivates the timer).

              Note:  in  order  to  allow  future  extensibility,
              external programs using the status parameter should
              only use the upper 16 bit of this 32 bit  parameter
              and leave the lower 16 bit untouched.

              The  channel  to  record  from.  This is either the
              channel number as shown in the on-screen menus,  or
              a complete channel ID. When reading timers.conf any
              channel numbers will be mapped  to  the  respective
              channel  ids  and  when  the file is written again,
              there will only be channel ids. Channel numbers are
              accepted as input in order to allow easier creation
              of timers when manually editing timers.conf.  Also,
              when  timers  are  listed  via  SVDRP commands, the
              channels are given as numbers.

       Day    The day when this timer shall record.

              If this is a `single-shot' timer, this is  the  day
              of  month  on  which  this timer shall record. This
              must be in the range 1...31.

              In case of a `repeating' timer  this  is  a  string

              The  day  definition  of a `repeating' timer may be
              followed by the date when that timer shall hit  for
              the first time. The format for this is @YYYY-MM-DD,
              so a complete definition could look like this:


              which would implement a timer  that  records  Moday
              thru  Friday, and will hit for the first time on or
              after February 18, 2002.  This  first  day  feature
              can be used to disable a repeating timer for a cou­
              ple of days,  or  for  instance  to  define  a  new
              Mon...Fri timer on wednesday, which actually starts
              "monday next week". The first day date  given  need
              not  be that of a day when the timer would actually

       Start  A four digit integer defining when this timer shall
              start recording.  The format is hhmm, so 1430 would
              mean "half past two" in the afternoon.

       Stop   A four digit integer defining when this timer shall
              stop  recording.  The format is the same as for the
              start time.

              An integer in the range 0...99, defining the prior­
              ity of this timer and of recordings created by this
              timer.  0 represents the lowest value, 99 the high­
              est.   The  priority  is used to decide which timer
              shall be started in case  there  are  two  or  more
              timers  with  the  exact same start time. The first
              timer in the list with the highest priority will be

              This value is also stored with the recording and is
              later used to decide which recording to remove from
              disk in order to free space for a new recording. If
              the disk runs full and a new recording  needs  more
              space, an existing recording with the lowest prior­
              ity (and which has exceeded  its  guaranteed  life­
              time) will be removed.

              If  all available DVB cards are currently occupied,
              a timer with a higher priority will  interrupt  the
              timer  with  the  lowest priority in order to start

              The guaranteed lifetime (in days)  of  a  recording
              programme name).

              The special keywords TITLE and EPISODE, if present,
              will be replaced by the title and episode  informa­
              tion from the EPG data at the time of recording (if
              that data is available). If at the time of  record­
              ing  either  of  these  cannot be determined, TITLE
              will default to the channel name, and EPISODE  will
              default to a blank.

              Arbitrary text that describes the recording made by
              this timer.  Any newline characters in the  summary
              have  to  be  replaced  by '|', and the summary may
              contain ':' characters. If this field is not empty,
              its  contents  will be written into the summary.vdr
              file of the recording.

       The file sources.conf defines the codes to be used in  the
       Source  field  of  channels  in  channels.conf and assigns
       descriptive texts to them.  Example:

       S19.2E  Astra 1

       Anything after (and including) a '#' character is comment.

       The first character of the code must be one of
       S   Satellite
       C   Cable
       T   Terrestrial
       and is followed by further data pertaining to that partic­
       ular source. In case of  Satellite  this  is  the  orbital
       position in degrees, followed by E for east or W for west.

       The file diseqc.conf defines the DiSEqC control  sequences
       to  be  sent  to the DVB-S card in order to access a given
       satellite position and/or band.  Example:

       S19.2E  11700 V  9750  t v W15 [E0 10 38 F0] W15 A W15 t

       Anything after (and including) a '#' character is comment.

       The  first  word  in  a  parameter line must be one of the
       codes defined in the file  sources.conf  and  tells  which
       satellite this line applies to.

       Following  is  the  "switch  frequency" of the LNB (slof),
       which is the transponder frequency up to which this  entry
       shall  be  used; the first entry with an slof greater than
       the actual transponder frequency will be  used.  Typically
       The  rest  of the line holds the actual sequence of DiSEqC
       actions to be taken.  The code letters used here are
       t          22kHz tone off
       T          22kHz tone on
       v          voltage low (13V)
       V          voltage high (18V)
       A          mini A
       B          mini B
       Wnn        wait nn milliseconds (nn may be any positive integer number)
       [xx ...]   hex code sequence (max. 6)
       There can be any number of actions in  a  line,  including
       none  at  all - in which case the entry would be used only
       to set the LOF to use for the given  frequency  range  and

       The  file  ca.conf  defines  the numbers to be used in the
       Conditional access field of channels in channels.conf  and
       assigns descriptive texts to them.  Example:

       101    Premiere World

       Anything after (and including) a '#' character is comment.

       Value lines consist of an integer number,  followed  by  a
       text describing this decryption method (typically the name
       of the pay tv service using this decryption method).

       The special value 0 means Free To Air, which can  be  used
       for  channels  that  don't  require  additional decryption

       The values 1...4 can be used for channels  that  for  some
       reason explicitly need a given DVB card (for backward com­

       The file remote.conf contains the key assignments for  all
       remote  control  units.  Each  line  consists  of  one key
       assignment in the following format:

       name.key  code

       where name is the name of the remote control (for instance
       KBD  for  the  PC keyboard, RCU for the home-built "Remote
       Control Unit", or LIRC for the "Linux Infrared Remote Con­
       trol"),  key  is the name of the key that is defined (like
       Up, Down, Menu etc.), and code is a character string  that
       this  remote  control  delivers  when  the  given  key  is

       -P option when starting VDR. There can be only one @plugin
       per  key  macro,  and  it implicitly adds an Ok key to the
       macro definition (in order to actually select the  plugins
       main menu entry), which counts against the total number of
       keys in the macro. For instance

       User1 @abc Down Down Ok

       would call the main menu function of the "abc" plugin  and
       execute two "Down" key presses, followed by "Ok".
       Note  that  the  color  keys will only execute their macro
       function in "normal viewing" mode (i.e. when no other menu
       or  player  is active). The User1...User9 keys will always
       execute their macro function.  There may be up to 15  keys
       in such a key sequence.

       The  file  commands.conf  contains the definitions of com­
       mands that can be executed from the vdr main menu's  "Com­
       mands"  option.  Each line contains one command definition
       in the following format:

       title : command

       where title is the string that will be  displayed  in  the
       "Commands"  menu, and command is the actual command string
       that will be executed when this option  is  selected.  The
       delimiting  ':'  may  be surrounded by any number of white
       space characters. If title ends with  the  character  '?',
       there  will  be a confirmation prompt before actually exe­
       cuting the command. This can be  used  for  commands  that
       might  have  serious  results (like deleting files etc) to
       make sure they are not executed inadvertently.

       Everything following (and including) a  '#'  character  is
       considered to be comment.

       By default the menu entries in the "Commands" menu will be
       numbered '1'...'9' to make them selectable by pressing the
       corresponding number key. If you want to use your own num­
       bering scheme (maybe to skip certain numbers),  just  pre­
       cede  the titles with the numbers of your choice. vdr will
       suppress its automatic numbering if  the  first  entry  in
       commands.conf  starts with a digit in the range '1'...'9',
       followed by a blank.

       In order to avoid error messages  to  the  console,  every
       command  should  have  stderr redirected to stdout. Every­
       thing the command prints to stdout will be displayed in  a
       result window, with title as its title.


       The file reccmds.conf can be used to define commands  that
       can  be  applied to the currently highlighted recording in
       the "Recordings" menu. The syntax is exactly the  same  as
       described  for  the  file  commands.conf. When executing a
       command, the directory  name  of  the  recording  will  be
       appended  to  the command string, separated by a blank and
       enclosed in single quotes.

       The file svdrphosts.conf contains the IP  numbers  of  all
       hosts  that  are  allowed  to access the SVDRP port.  Each
       line contains one IP number in the format


       where IP-Address is the address of a host or a network  in
       the usual dot separated notation (as in If
       the optional Netmask is given only  the  given  number  of
       bits of IP-Address are taken into account. This allows you
       to grant SVDRP access to all hosts of an  entire  network.
       Netmask can be any integer from 1 to 32. The special value
       of 0 is  only  accepted  if  the  IP-Address  is,
       because  this  will give access to any host (USE THIS WITH

       Everything following (and including) a  '#'  character  is
       considered to be comment.

       Examples:        # always accept localhost # any host on the local net  # a specific host        # any host on any net (USE WITH CARE!)

       The  file  setup.conf  contains  the  basic  configuration
       options for vdr.  Each line contains  one  option  in  the
       format "Name = Value".  See the MANUAL file for a descrip­
       tion of the available options.

       The files 001.vdr...255.vdr are the actual  recorded  MPEG
       data  files.  In  order  to keep the size of an individual
       file below a given limit, a recording is split  into  sev­
       eral files. The contents of these files is Packetized Ele­
       mentary Stream (PES) and contains ES packets with ids 0xE0
       for  video,  0xC0  for  audio  1  and 0xC1 for audio 2 (if
       available).  Dolby Digital data is stored in packets  with
       ids 0xBD.

       plain ASCII file and can contain arbitrary text.

       The  file resume.vdr (if present in a recording directory)
       contains the position within the recording where the  last
       replay session left off.  The data is a four byte (binary)
       integer  value  and  defines  an  offset  into  the   file

       The  file  marks.vdr (if present in a recording directory)
       contains the editing marks  defined  for  this  recording.
       Each  line contains the definition of one mark in the fol­
       lowing format:

       hh:mm:ss.ff comment

       where hh:mm:ss.ff is a frame position within  the  record­
       ing,  given  as  "hours,  minutes,  seconds and (optional)
       frame number".  comment can be any string and may be  used
       to  describe this mark.  If present, comment must be sepa­
       rated from the frame position by at least one blank.

       The lines in this file need not necessarily appear in  the
       correct  temporal  sequence,  they  will  be automatically
       sorted by time index.


       - the comment is currently not used by VDR
       - marks must have a frame number, and that frame  MUST  be
       an  I-frame  (this  means that only marks generated by VDR
       itself can be used, since they will always  be  guaranteed
       to mark I-frames).

       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>
       T   <title>
       S   <subtitle>
       D   <description>

       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

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




       Written by Klaus Schmidinger.


       Report bugs to <vdr-bugs@cadsoft.de>.


       Copyright © 2003 Klaus Schmidinger.

       This is free software; see the source for  copying  condi­
       tions.  There is NO warranty; not even for MERCHANTABILITY

1.2.0                       1 Jun 2003                     vdr(5)

An undefined database error occurred. SELECT distinct pages.pagepath,pages.pageid FROM pages, page2command WHERE pages.pageid = page2command.pageid AND commandid =




Security Code
Security Code
Type Security Code

Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name.

Help if you can!

Amazon Wish List

Did You Know?
You can help in many different ways.


Tell a Friend About Us

Bookmark and Share

Web site powered by PHP-Nuke

Is this information useful? At the very least you can help by spreading the word to your favorite newsgroups, mailing lists and forums.
All logos and trademarks in this site are property of their respective owner. The comments are property of their posters. Articles are the property of their respective owners. Unless otherwise stated in the body of the article, article content (C) 1994-2013 by James Mohr. All rights reserved. The stylized page/paper, as well as the terms "The Linux Tutorial", "The Linux Server Tutorial", "The Linux Knowledge Base and Tutorial" and "The place where you learn Linux" are service marks of James Mohr. All rights reserved.
The Linux Knowledge Base and Tutorial may contain links to sites on the Internet, which are owned and operated by third parties. The Linux Tutorial is not responsible for the content of any such third-party site. By viewing/utilizing this web site, you have agreed to our disclaimer, terms of use and privacy policy. Use of automated download software ("harvesters") such as wget, httrack, etc. causes the site to quickly exceed its bandwidth limitation and are therefore expressly prohibited. For more details on this, take a look here

PHP-Nuke Copyright © 2004 by Francisco Burzi. This is free software, and you may redistribute it under the GPL. PHP-Nuke comes with absolutely no warranty, for details, see the license.
Page Generation: 0.09 Seconds