1
0
mirror of https://github.com/VDR4Arch/vdr.git synced 2023-10-10 13:36:52 +02:00
vdr/INSTALL

118 lines
5.2 KiB
Plaintext
Raw Normal View History

2000-04-24 10:40:00 +02:00
Installation of the Video Disk Recorder
---------------------------------------
Compiling and running the program:
----------------------------------
Make sure the files from this package are located in a
directory that is "parallel" to the DVB directory of the
driver source for the Siemens DVB-S PCI card (refer to
http://linuxtv.org/dvb/siemens_dvb.html for more information
about that driver). For example, if the DVB driver was
extracted into the directory /home/kls/vdr/DVB, then this
package should be extracted into /home/kls/vdr/VDR.
2000-05-27 16:10:47 +02:00
This program requires the card driver version 0.05 or higher
2000-04-24 10:40:00 +02:00
to work properly.
After extracting the package, change into the VDR directory
and type 'make'. This should produce an executable file
named 'vdr', which can be run after the DVB driver has been
installed.
2000-07-15 12:39:20 +02:00
The 'vdr' program can be controlled via the PC keyboard or
an infrared remote control unit. Define the REMOTE macro to one of the
following values 'make' call to activate the respective control mode:
REMOTE=KBD control via the PC keyboard (default)
REMOTE=RCU control via the "Remote Control Unit" receiver
(see http://www.cadsoft.de/people/kls/vdr/remote.htm)
REMOTE=LIRC control via the "Linux Infrared Remote Control"
(see http://fsinfo.cs.uni-sb.de/~columbus/lirc)
2000-04-24 10:40:00 +02:00
Adding "DEBUG_OSD=1" will use the PC screen (or current window)
to display texts instead of the DVB card's on-screen display
interface. These modes are useful when testing new menus if you
only have a remote connection to the VDR (which, in my case, is
located in the living room and has neither a monitor nor a keyboard).
2000-04-24 16:49:28 +02:00
When running, the 'vdr' program writes status information into the
system log file (/var/log/messages). You may want to watch these
messages (tail -f /var/log/mesages) to see if there are any problems.
2000-07-23 15:01:31 +02:00
The program can be controlled via a network connection to its SVDRP
port ("Simple Video Disk Recorder Protocol"). By default, it listens
on port 2001 (use the --port=PORT option to change this). For details
about the SVDRP syntax see the source file 'svdrp.c'.
2000-07-23 15:36:43 +02:00
If the program shall run as a daemon, use the --daemon option. This
will completely detach it from the terminal and will continue as a
background process.
2000-07-23 15:01:31 +02:00
Use "vdr --help" for a list of available command line options.
2000-04-24 10:40:00 +02:00
The video data directory:
-------------------------
All recordings are written into directories below "/video". Please
make sure this directory exists, and that the user who runs the 'vdr'
program has read and write access to that directory.
If you prefer a different location for your video files, you can change
the value of 'BaseDir' in recording.c.
Note that the file system need not be 64-bit proof, since the 'vdr'
program splits video files into chunks of about 1GB. You should use
a disk with several gigabytes of free space. One GB can store roughly
half an hour of video data.
Configuration files:
--------------------
There are three configuration files that hold information about
channels, remote control keys and timers. These files are currrently
assumed to be located in the directory from which the 'vdr' program
was started (this will become configurable later). The configuration
files can be edited with any text editor, or will be written by the
'vdr' program if any changes are made inside the on-screen menus.
The meaning of the data entries may still vary in future releases,
so for the moment please look at the source code (config.c) to see
the meaning of the various fields.
Learning the remote control keys:
---------------------------------
There is no default 'keys.conf' file, so if you compile the program
2000-07-15 12:39:20 +02:00
with 'REMOTE=RCU' you will have to go through a "teach-in"
2000-04-24 10:40:00 +02:00
session that allows the program to learn your remote control codes.
It will first attempt to determine the basic data transfer mode and
timing of your remote control unit, and then will ask you to press one
key after the other so that it can learn the various key codes. You will
at least need to provide an "Up" and a "Down" key, so that you can switch
channels. The rest of the key definitions is optional, but the more keys
you define, the more you will be able to navigate through the menus and
2000-05-27 16:10:47 +02:00
control recording/replaying. The program uses only a very small number
of keys which have multiple meanings in the various modes (see MANUAL
for a detailed description).
2000-07-15 12:39:20 +02:00
If the program has been built with "REMOTE=KBD", it will use the
2000-04-24 10:40:00 +02:00
key configuration file 'keys-pc.conf', so that you won't loose data
2000-07-15 12:39:20 +02:00
when switching between remote control and keyboard mode.
2000-04-24 10:40:00 +02:00
The default PC key assignments are:
Up, Down, Left, Right Crsr keys in numeric block
2000-05-27 16:10:47 +02:00
Menu 'Home' in numeric block
Ok '5' in numeric block
Back 'End' in numeric block
2000-04-24 10:40:00 +02:00
Red, Green, Yellow, Blue 'F1'..'F4'
2000-05-27 16:10:47 +02:00
0..9 '0'..'9' in top row
2000-04-24 10:40:00 +02:00
2000-07-15 12:39:20 +02:00
If you prefer different key assignments, or if the default doesn't work for
your keyboard, simply delete the file 'keys-pc.conf' and restart 'vdr' to get
into learning mode.
If the program has been compiled with 'REMOTE=LIRC', no 'keys.conf' file
will be used. Instead, the key names as listed in the source file 'config.c'
must be used when setting up LIRC. See http://www2.arnes.si/~mthale1 for
more about LIRC.
2000-04-24 10:40:00 +02:00