2000-04-24 10:40:00 +02:00
|
|
|
Installation of the Video Disk Recorder
|
|
|
|
---------------------------------------
|
|
|
|
|
2015-02-17 15:11:36 +01:00
|
|
|
Version 2.2
|
2003-05-29 12:44:06 +02:00
|
|
|
-----------
|
|
|
|
|
2000-04-24 10:40:00 +02:00
|
|
|
Compiling and running the program:
|
|
|
|
----------------------------------
|
|
|
|
|
2005-09-02 14:54:29 +02:00
|
|
|
VDR requires the Linux-DVB driver header files to compile.
|
|
|
|
As of kernel 2.6 these are part of the official Linux kernel
|
2006-04-15 12:39:35 +02:00
|
|
|
distribution, and so they should be automatically found in
|
|
|
|
/usr/include/linux/dvb. If your DVB driver header files are
|
|
|
|
in a different location, you can rename the file Make.config.template
|
|
|
|
to Make.config and adjust the definition of DVBDIR in that file.
|
|
|
|
|
|
|
|
Refer to http://linuxtv.org for more information about the Linux-DVB driver.
|
2000-04-24 10:40:00 +02:00
|
|
|
|
2009-04-10 10:29:21 +02:00
|
|
|
VDR requires the Linux-DVB driver version that supports the S2API interface.
|
2000-04-24 10:40:00 +02:00
|
|
|
|
2007-06-10 13:02:43 +02:00
|
|
|
You will also need to install the following libraries, as well as their
|
|
|
|
"devel" packages to get the necessary header files for compiling VDR:
|
|
|
|
|
2007-06-17 11:12:46 +02:00
|
|
|
fontconfig
|
2007-06-10 13:02:43 +02:00
|
|
|
freetype2
|
2010-09-19 12:36:07 +02:00
|
|
|
fribidi (see "BiDi support" below)
|
2007-08-11 12:39:06 +02:00
|
|
|
gettext
|
2007-06-10 13:02:43 +02:00
|
|
|
libcap
|
|
|
|
libjpeg
|
|
|
|
|
|
|
|
If the "capability" module is not compiled into your kernel, you may
|
|
|
|
need to do "modprobe capability" before running VDR.
|
|
|
|
|
2000-04-24 10:40:00 +02:00
|
|
|
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.
|
|
|
|
|
2012-10-09 10:43:28 +02:00
|
|
|
If you want to build a 32-bit version of VDR on a 64-bit machine, you can
|
|
|
|
use 'make M32=1' to do so. Note that you also need to have a Make.config file
|
|
|
|
(derived from Make.config.template) to make this work.
|
|
|
|
|
2000-10-03 10:34:48 +02:00
|
|
|
IMPORTANT: See "Configuration files" below for information on how
|
|
|
|
========= to set up the configuration files at the proper location!
|
|
|
|
|
2005-07-31 11:38:40 +02:00
|
|
|
By default the 'vdr' program can be controlled via the PC keyboard.
|
|
|
|
If you want to disable control via the keyboard, you can add NO_KBD=1
|
|
|
|
to the 'make' call, or use the '--no-kbd' option at runtime.
|
|
|
|
|
|
|
|
If you have an infrared remote control unit you can define the REMOTE macro
|
|
|
|
to one of the following values in the 'make' call to make the respective control
|
|
|
|
the default:
|
2000-07-15 12:39:20 +02:00
|
|
|
|
|
|
|
REMOTE=LIRC control via the "Linux Infrared Remote Control"
|
2000-12-28 12:57:16 +01:00
|
|
|
(see http://www.lirc.org)
|
2000-07-15 12:39:20 +02:00
|
|
|
|
2012-02-27 12:30:45 +01:00
|
|
|
Alternatively you can use the '--lirc' option at runtime.
|
|
|
|
This option accepts an optional path to the remote control device,
|
|
|
|
the default of which can be set via the LIRC_DEVICE macro.
|
2000-04-24 10:40:00 +02:00
|
|
|
|
2013-02-08 09:24:55 +01:00
|
|
|
If you want to make your video directory available to other machines that
|
|
|
|
have limitations on directory name lengths and/or allowed characters in
|
|
|
|
directory names, you can call VDR with the command line option '--dirnames'
|
|
|
|
(see man vdr(1) for details).
|
2001-02-18 16:21:05 +01:00
|
|
|
|
2000-04-24 16:49:28 +02:00
|
|
|
When running, the 'vdr' program writes status information into the
|
2007-10-13 13:03:57 +02:00
|
|
|
system log file, which is usually /var/log/messages (or /var/log/user.log,
|
|
|
|
depending on your syslog configuration). You may want to watch these
|
|
|
|
messages (tail -f /var/log/messages) to see if there are any problems.
|
2000-04-24 16:49:28 +02:00
|
|
|
|
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
|
2010-04-02 12:25:50 +02:00
|
|
|
on port 6419 (use the --port=PORT option to change this). For details
|
2000-07-23 15:01:31 +02:00
|
|
|
about the SVDRP syntax see the source file 'svdrp.c'.
|
|
|
|
|
2000-09-17 21:10:57 +02:00
|
|
|
WARNING: DUE TO THE OPEN SVDRP PORT THIS PROGRAM MAY CONSTITUTE A
|
|
|
|
======= POTENTIAL SECURITY HAZARD! IF YOU ARE NOT RUNNING VDR IN
|
|
|
|
A CONTROLLED ENVIRONMENT, YOU MAY WANT TO DISABLE SVDRP
|
|
|
|
BY USING '--port=0'!
|
|
|
|
|
2002-02-02 17:20:54 +01:00
|
|
|
The file 'svdrphosts.conf' can be used to define which hosts are allowed
|
|
|
|
to access the SVDRP port. By default only localhost (127.0.0.1) is granted
|
|
|
|
access. If you want to give other hosts access to your SVDRP port you need to
|
|
|
|
add their IP numbers to 'svdrphosts.conf'.
|
|
|
|
|
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.
|
|
|
|
|
2001-03-31 10:32:58 +02:00
|
|
|
When starting the program through an entry in /etc/inittab, use the --terminal
|
|
|
|
option to set the controlling terminal, as in
|
|
|
|
|
|
|
|
vdr:123:respawn:/usr/local/bin/vdr --terminal=/dev/tty8 -w 60
|
|
|
|
|
2002-04-01 12:25:38 +02:00
|
|
|
See the man page vdr(1) for complete information about all command line options.
|
|
|
|
|
2015-03-12 11:00:54 +01:00
|
|
|
Output devices
|
|
|
|
--------------
|
|
|
|
|
|
|
|
VDR by itself doesn't produce any audio or video output. In order to watch
|
|
|
|
live tv or recordings, you will need to use a plugin that supports the actual
|
|
|
|
hardware in your system, for instance:
|
|
|
|
|
|
|
|
Plugin: Device:
|
|
|
|
|
|
|
|
dvbsddevice Full-Featured SD DVB cards (Fujitsu-Siemens Design)
|
|
|
|
(comes with the VDR source)
|
|
|
|
dvbhddevice Full-featured HD DVB cards (Technotrend TT S2-6400)
|
|
|
|
https://bitbucket.org/powARman/dvbhddevice
|
|
|
|
rpihddevice Raspberry Pi
|
|
|
|
http://projects.vdr-developer.org/git/vdr-plugin-rpihddevice.git
|
|
|
|
|
|
|
|
See http://linuxtv.org/vdrwiki/index.php/Output_devices for more.
|
|
|
|
|
2012-06-03 09:24:21 +02:00
|
|
|
Standard compliance
|
|
|
|
-------------------
|
|
|
|
|
|
|
|
Basically VDR works according to the DVB standard, but there are countries/providers
|
|
|
|
that use other standards, which in some details deviate from the DVB standard.
|
|
|
|
This makes it necessary to handle things differently in some areas, depending on
|
|
|
|
which standard is actually used. If this is the case in your area, you may need
|
|
|
|
to adjust the option "DVB/Standard compliance" in the Setup menu accordingly.
|
|
|
|
|
2001-10-07 11:00:35 +02:00
|
|
|
Locale
|
|
|
|
------
|
|
|
|
|
|
|
|
When presenting the list of recordings, VDR sorts the entries according to
|
|
|
|
the current "locale" settings. This makes sure that special characters (like
|
|
|
|
the German "umlauts") appear at the expected positions. In order to benefit
|
|
|
|
from this you may have to set the locale environment variable, for instance
|
|
|
|
|
|
|
|
export LANG=de_DE
|
|
|
|
|
|
|
|
for a German locale. If you don't want this to result in German error messages
|
|
|
|
in the log file, it is sufficient to just set
|
|
|
|
|
|
|
|
export LC_COLLATE=de_DE
|
|
|
|
|
|
|
|
which only influences the way strings are sorted and leaves error messages
|
|
|
|
in English.
|
|
|
|
|
2007-08-24 13:13:08 +02:00
|
|
|
Note that for VDR's internationalized texts to work, the LANG environment
|
|
|
|
variable must be set to a valid locale!
|
|
|
|
|
2010-09-19 12:36:07 +02:00
|
|
|
BiDi support
|
|
|
|
------------
|
|
|
|
|
|
|
|
Some languages are written right-to-left. In order to display such languages
|
|
|
|
correctly, you need to build VDR with BIDI=1. This will link to the "fribidi"
|
|
|
|
library and implement a function that prepares bidirectional texts to be
|
|
|
|
displayed correctly. Since BiDi support adds some runtime overhead by requiring
|
|
|
|
additional memory allocation and copying, this feature is not compiled in
|
|
|
|
by default, so that users that have no need for this don't get any overhead.
|
|
|
|
|
2015-09-10 13:36:50 +02:00
|
|
|
Workaround for providers not encoding their DVB SI table strings correctly
|
|
|
|
--------------------------------------------------------------------------
|
2008-03-22 11:09:35 +01:00
|
|
|
|
2015-06-01 20:32:09 +02:00
|
|
|
According to "ETSI EN 300 468" the default character set for SI data is
|
2008-03-22 11:09:35 +01:00
|
|
|
ISO6937. But unfortunately some broadcasters actually use ISO-8859-9 or
|
|
|
|
other encodings, but fail to correctly announce that.
|
|
|
|
Users who want to set the default character set to something different can
|
2015-02-10 14:29:27 +01:00
|
|
|
do this by using the command line option --chartab with something
|
2008-03-22 11:09:35 +01:00
|
|
|
like ISO-8859-9.
|
|
|
|
|
2010-01-17 12:45:44 +01:00
|
|
|
Start script with automatic restart in case of hangups:
|
|
|
|
-------------------------------------------------------
|
|
|
|
|
|
|
|
The VDR source directory contains a 'runvdr.template'. Just copy it as 'runvdr'
|
|
|
|
into your /usr/bin or /usr/local/bin directory and adjust it to your particular
|
|
|
|
requirements. (See the comments inside the script for more information.)
|
2001-02-24 16:18:43 +01:00
|
|
|
|
|
|
|
If you run VDR using the 'runvdr' shell script it will use the built-in
|
|
|
|
watchdog timer to restart the program in case something happens that
|
2001-07-21 17:28:58 +02:00
|
|
|
causes a program hangup. If you change the command line options for the
|
|
|
|
call to the VDR program, be sure to NOT use the '-d' option! Otherwise
|
2006-04-21 15:15:18 +02:00
|
|
|
VDR will go into 'daemon' mode and the initial program call will return
|
2006-02-04 15:26:13 +01:00
|
|
|
immediately! 'runvdr' needs to be started as user 'root'. Use the '-u'
|
|
|
|
option to run the actual 'vdr' program under a different user id.
|
2001-02-24 16:18:43 +01:00
|
|
|
|
2005-12-31 13:30:11 +01:00
|
|
|
Setting the system time:
|
|
|
|
------------------------
|
|
|
|
|
|
|
|
If you want VDR to set the system time according to the data received
|
2006-01-13 16:16:32 +01:00
|
|
|
from the transponder, you need to start VDR as user 'root'. For security
|
|
|
|
reasons you should then use the '-u' option to define a lesser privileged
|
|
|
|
user id under which VDR should actually run. It will then only keep the
|
|
|
|
capability to set the system time, and set its user id to the given one.
|
2005-12-31 13:30:11 +01:00
|
|
|
You also need to enable the "EPG/Set system time" option in VDR's
|
|
|
|
Setup menu, and select a transponder from which you want to receive
|
|
|
|
the time in "Use time from transponder". Make sure you select a transponder
|
|
|
|
that has a reliable clock - some transponders are quite off.
|
|
|
|
|
2001-09-01 09:04:37 +02:00
|
|
|
Automatic shutdown:
|
|
|
|
-------------------
|
|
|
|
|
|
|
|
If you define a shutdown command via the '-s' command line option, VDR
|
|
|
|
will call the given command if there is currently no recording or replay
|
|
|
|
active, the user has been inactive for at least MinUserInactivity minutes
|
|
|
|
and the next timer event is at least MinEventTimeout minutes in the future
|
|
|
|
(see the Setup parameters in MANUAL).
|
|
|
|
|
2001-11-03 12:23:45 +01:00
|
|
|
The command given in the '-s' option will be called with five parameters.
|
2007-02-25 10:56:29 +01:00
|
|
|
|
|
|
|
The first one is the time (in UTC) of the next timer event or plugin wakeup
|
|
|
|
time (as a time_t type number), and the second one is the number of
|
|
|
|
seconds from the current time until the next timer event. Your program can
|
|
|
|
choose which one to use for programming some sort of hardware device that
|
|
|
|
makes sure the computer will be restarted in time before the next timer
|
|
|
|
event. Your program must also initiate the actual shutdown procedure of the
|
|
|
|
computer. VDR will not automatically exit after calling the shutdown
|
|
|
|
program, but will rather continue normally until it receives a SIGTERM when
|
|
|
|
the computer is actually shut down. So in case the shutdown fails, or the
|
|
|
|
shutdown program for some reason decides not to perform a shutdown, VDR
|
|
|
|
will stay up and running and will call the shutdown program again after a
|
|
|
|
while. The command will be started in a separate background session, so it
|
|
|
|
can continue to run even after VDR has terminated.
|
|
|
|
|
|
|
|
If there are currently no timers active and there is no plugin wakeup
|
|
|
|
time, both parameters will be '0'. In that case the program shall not set
|
|
|
|
the hardware for automatic restart and only perform the system shutdown.
|
|
|
|
A program that uses the second parameter to set the hardware for restart
|
|
|
|
must therefore also check whether the first parameter is '0'.
|
|
|
|
|
|
|
|
If the wakeup time is given by a timer, the third parameter will be the
|
|
|
|
number of the channel that will be recorded, otherwise it will be 0. The
|
|
|
|
fourth parameter contains the file name of the recording as defined in the
|
|
|
|
timer, the name of the plugin that requested the wakeup time, or an empty
|
|
|
|
string if no wakeup time is present. These can be used by the shutdown
|
|
|
|
program to show that information on some display interface etc.
|
2001-09-30 12:35:09 +02:00
|
|
|
|
2001-11-03 12:23:45 +01:00
|
|
|
The fifth parameter indicates the reason why the shutdown was requested.
|
|
|
|
'0' means this is an automatic shutdown due to some timeout, while '1' means
|
|
|
|
that this is a user requested shutdown (resulting from pressing the "Power"
|
|
|
|
key). The shutdown program may use this information to decide whether or
|
|
|
|
not to actually perform the system shutdown.
|
|
|
|
|
2006-08-05 10:42:23 +02:00
|
|
|
If a timer is currently recording, or a recording would start within the
|
|
|
|
next 30 minutes (default for the "Min. event timeout" setup parameter), and
|
|
|
|
the user insists in shutting down now, the first and second parameter will
|
|
|
|
correspond to a time that is "Min. event timeout" minutes in the future.
|
2001-09-08 13:02:05 +02:00
|
|
|
|
2001-09-01 09:04:37 +02:00
|
|
|
Before the shutdown program is called, the user will be prompted to inform
|
|
|
|
him that the system is about to shut down. If any remote control key is
|
|
|
|
pressed while this prompt is visible, the shutdown will be cancelled (and
|
2007-01-04 13:23:42 +01:00
|
|
|
tried again later). The shutdown prompt will be displayed for 5 minutes, which
|
|
|
|
should be enough time for the user to react.
|
2001-09-01 09:04:37 +02:00
|
|
|
|
|
|
|
A sample shell script to be used with the '-s' option might look like this:
|
|
|
|
|
|
|
|
#!/bin/sh
|
|
|
|
setRTCwakeup $(($1 - 300))
|
|
|
|
sudo halt
|
|
|
|
|
|
|
|
Here 'setRTCwakeup' would be some program that uses the first parameter
|
|
|
|
(which is the absolute time of the next timer event) to set the Real Time
|
|
|
|
Clock so that it wakes up the computer 5 minutes (i.e. 300 seconds) before
|
|
|
|
that event. The 'sudo halt' command then shuts down the computer.
|
|
|
|
You will have to substitute both commands with whatever applies to your
|
|
|
|
particular hard- and software environment.
|
|
|
|
|
2001-09-01 11:44:08 +02:00
|
|
|
If the '-s' option is present, the VDR machine can be turned off by pressing
|
|
|
|
the "Power" key on the remote control.
|
|
|
|
|
2001-09-22 14:23:55 +02:00
|
|
|
Executing commands before and after a recording:
|
|
|
|
------------------------------------------------
|
|
|
|
|
|
|
|
You can use the '-r' option to define a program or script that gets called
|
2001-09-23 14:02:11 +02:00
|
|
|
before and after a recording is performed, and after an editing process
|
2012-09-17 09:03:01 +02:00
|
|
|
has finished or a recording has been deleted.
|
2001-09-22 14:23:55 +02:00
|
|
|
|
2015-04-11 12:12:43 +02:00
|
|
|
The program will be called with two or three (in case of "editing" and "edited")
|
|
|
|
string parameters. The first parameter is one of
|
2001-09-23 14:02:11 +02:00
|
|
|
|
|
|
|
before if this is *before* a recording starts
|
2014-01-01 12:53:40 +01:00
|
|
|
started if this is after a recording has *started*
|
2001-09-23 14:02:11 +02:00
|
|
|
after if this is *after* a recording has finished
|
2015-04-11 12:12:43 +02:00
|
|
|
editing if this is before *editing* a recording
|
2001-09-23 14:02:11 +02:00
|
|
|
edited if this is after a recording has been *edited*
|
2012-09-17 09:03:01 +02:00
|
|
|
deleted if this is after a recording has been *deleted*
|
2001-09-23 14:02:11 +02:00
|
|
|
|
|
|
|
and the second parameter contains the full name of the recording's
|
|
|
|
directory (which may not yet exists at that moment in the "before" case).
|
2015-04-11 12:12:43 +02:00
|
|
|
In the "editing" and "edited" case it will be the name of the edited version
|
|
|
|
(second parameter) and the name of the source version (third parameter).
|
2012-09-17 09:03:01 +02:00
|
|
|
In the "deleted" case the extension of the directory name is ".del"
|
|
|
|
instead of ".rec".
|
2001-09-22 14:23:55 +02:00
|
|
|
|
|
|
|
Within this program you can do anything you would like to do before and/or
|
2001-09-23 14:02:11 +02:00
|
|
|
after a recording or after an editing process. However, the program must return
|
|
|
|
as soon as possible, because otherwise it will block further execution of VDR.
|
|
|
|
Be especially careful to make sure the program returns before the watchdog
|
|
|
|
timeout you may have set up with the '-w' option! If the operation you want to
|
|
|
|
perform will take longer, you will have to run it as a background job.
|
|
|
|
|
|
|
|
An example script for use with the '-r' option could look like this:
|
|
|
|
|
|
|
|
#!/bin/sh
|
|
|
|
case "$1" in
|
|
|
|
before)
|
|
|
|
echo "Before recording $2"
|
|
|
|
;;
|
2014-01-01 12:53:40 +01:00
|
|
|
started)
|
|
|
|
echo "Started recording $2"
|
|
|
|
;;
|
2001-09-23 14:02:11 +02:00
|
|
|
after)
|
|
|
|
echo "After recording $2"
|
|
|
|
;;
|
2015-04-11 12:12:43 +02:00
|
|
|
editing)
|
|
|
|
echo "Editing recording $2"
|
|
|
|
echo "Source recording $3"
|
|
|
|
;;
|
2001-09-23 14:02:11 +02:00
|
|
|
edited)
|
|
|
|
echo "Edited recording $2"
|
2012-06-02 13:57:41 +02:00
|
|
|
echo "Source recording $3"
|
2001-09-23 14:02:11 +02:00
|
|
|
;;
|
2012-09-17 09:03:01 +02:00
|
|
|
deleted)
|
|
|
|
echo "Deleted recording $2"
|
|
|
|
;;
|
2001-09-23 14:02:11 +02:00
|
|
|
*)
|
|
|
|
echo "ERROR: unknown state: $1"
|
|
|
|
;;
|
|
|
|
esac
|
2001-09-22 14:23:55 +02:00
|
|
|
|
2000-07-29 15:21:42 +02:00
|
|
|
Command line options:
|
|
|
|
---------------------
|
|
|
|
|
2000-07-23 15:01:31 +02:00
|
|
|
Use "vdr --help" for a list of available command line options.
|
|
|
|
|
2001-06-24 17:42:19 +02:00
|
|
|
Replaying Dolby Digital audio:
|
|
|
|
------------------------------
|
|
|
|
|
2005-02-16 17:03:32 +01:00
|
|
|
If you have a "full featured" DVB card with SPDIF output you can replay
|
|
|
|
Dolby Digital audio directly through the DVB card.
|
|
|
|
You can also use an external program that reads the DD data
|
2001-06-24 17:42:19 +02:00
|
|
|
from stdin and processes it in a way suitable for your audio hardware.
|
|
|
|
This program must be given to VDR with the '-a' option, as in
|
|
|
|
|
|
|
|
vdr -a ac3play
|
|
|
|
|
2000-04-24 10:40:00 +02:00
|
|
|
The video data directory:
|
|
|
|
-------------------------
|
|
|
|
|
2013-01-06 18:48:29 +01:00
|
|
|
All recordings are written into directories below "/srv/vdr/video". Please
|
2000-04-24 10:40:00 +02:00
|
|
|
make sure this directory exists, and that the user who runs the 'vdr'
|
|
|
|
program has read and write access to that directory.
|
2000-07-29 15:21:42 +02:00
|
|
|
If you prefer a different location for your video files, you can use
|
2000-09-17 14:18:14 +02:00
|
|
|
the '-v' option to change that. Please make sure that the directory
|
|
|
|
name you use with '-v' is a clean and absolute path name (no '..' or
|
|
|
|
multiple slashes).
|
2000-04-24 10:40:00 +02:00
|
|
|
|
|
|
|
Note that the file system need not be 64-bit proof, since the 'vdr'
|
2005-02-08 09:51:53 +01:00
|
|
|
program splits video files into chunks of about 2GB. You should use
|
2000-04-24 10:40:00 +02:00
|
|
|
a disk with several gigabytes of free space. One GB can store roughly
|
2012-02-16 10:23:32 +01:00
|
|
|
half an hour of SD video data, or 10 minutes of HD video.
|
2013-08-23 13:09:27 +02:00
|
|
|
Either use one of today's large terabyte disks (preferably with a backup disk
|
|
|
|
in a RAID-1 array), or use something like "mhddfs" to group several disks
|
|
|
|
into one large volume.
|
2000-07-29 15:21:42 +02:00
|
|
|
|
2013-01-06 18:48:29 +01:00
|
|
|
Note that you should not copy any non-VDR files into the video directory,
|
2006-04-16 10:50:08 +02:00
|
|
|
since this might cause a lot of unnecessary disk access when VDR cleans up those
|
2003-04-27 11:26:33 +02:00
|
|
|
directories and there is a large number of files and/or subdirectories in
|
2009-04-25 14:23:58 +02:00
|
|
|
there. If you have a large disk that you want to use for VDR's video data as
|
|
|
|
well as other stuff, you may want to create a subdirectory for VDR, as in
|
|
|
|
|
2013-03-14 09:20:51 +01:00
|
|
|
/mydisk/video
|
2009-04-25 14:23:58 +02:00
|
|
|
|
|
|
|
and put your other stuff into, say,
|
|
|
|
|
|
|
|
/mydisk/otherstuff
|
2003-04-27 11:26:33 +02:00
|
|
|
|
2006-04-28 12:42:20 +02:00
|
|
|
If your video directory is mounted via a Samba share, and you are experiencing
|
|
|
|
problems with replaying in fast forward mode, you can comment out the line
|
|
|
|
|
|
|
|
#define USE_FADVISE
|
|
|
|
|
|
|
|
in the file tools.c, which may lead to better results.
|
|
|
|
|
2000-04-24 10:40:00 +02:00
|
|
|
Configuration files:
|
|
|
|
--------------------
|
|
|
|
|
2002-04-01 12:25:38 +02:00
|
|
|
There are several configuration files that hold information about
|
|
|
|
channels, remote control keys, timers etc. By default these files are
|
2013-01-06 18:48:29 +01:00
|
|
|
spread around the system according to the FHS ("File system Hierarchy Standard").
|
|
|
|
If you prefer to have VDR built to run locally under the VDR source tree,
|
|
|
|
you can copy the file Make.config.template to Make.config and set the parameter
|
|
|
|
LCLBLD=1. If you also want to have all data files under one single directory,
|
|
|
|
set ONEDIR=1 in Make.config.
|
2003-08-24 11:09:30 +02:00
|
|
|
|
|
|
|
For starters just copy all *.conf files from the VDR directory into your
|
|
|
|
video directory.
|
2000-09-15 15:09:15 +02:00
|
|
|
|
|
|
|
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.
|
2002-04-01 12:25:38 +02:00
|
|
|
Take a look at man page vdr(5) for information about the file formats.
|
2000-04-24 10:40:00 +02:00
|
|
|
|
2000-08-06 14:00:00 +02:00
|
|
|
The files that come with this package contain the author's selections,
|
|
|
|
so please make sure you adapt these to your personal taste. Also make sure
|
|
|
|
that the channels defined in 'channels.conf' are correct before attempting
|
|
|
|
to record anything. Channel parameters may vary and not all of the channels
|
|
|
|
listed in the default 'channels.conf' file have been verified by the author.
|
|
|
|
|
2001-02-03 16:53:01 +01:00
|
|
|
As a starting point you can copy the 'channels.conf' file that comes with the
|
|
|
|
VDR archive into your video directory (or into your config directory,
|
|
|
|
respectively, in case you have redirected it with the -c option).
|
|
|
|
|
2001-08-11 08:44:48 +02:00
|
|
|
Setting up DiSEqC:
|
|
|
|
------------------
|
|
|
|
|
|
|
|
If you are using a DVB-S card with a satellite equipment that needs to be
|
|
|
|
accessed using DiSEqC, you have to go to the "Setup" menu and set the "DiSEqC"
|
2002-11-01 10:43:16 +01:00
|
|
|
parameter to "on". You also need to set up the file 'diseqc.conf' to properly
|
|
|
|
access your DiSEqC equipment (see man vdr(5) for details).
|
2001-08-11 08:44:48 +02:00
|
|
|
|
2011-09-11 14:09:03 +02:00
|
|
|
A special form of DiSEqC is used to connect several receivers to one signal
|
|
|
|
source using only a single cable. This method, known as "Satellite Channel Routing"
|
|
|
|
according to EN50494 (aka "Unicable(TM)", "OLT(TM)", "SatCR", "Single Cable
|
2015-01-26 12:02:14 +01:00
|
|
|
Distribution", "Channel Stacking System" or "Single Cable Interface") or
|
|
|
|
EN50607 (aka "JESS") uses the file "scr.conf" to specify which SCR channels
|
|
|
|
use which user band frequency.
|
2011-09-11 14:09:03 +02:00
|
|
|
|
2011-12-04 12:45:26 +01:00
|
|
|
If DVB-S devices need to be connected to the same satellite cable, but no
|
|
|
|
"Satellite Channel Routing" is available, they can be set to be "bonded" in
|
|
|
|
the Setup/LNB menu. Bonded devices can only be tuned to the same polarization
|
|
|
|
and frequency band, which reduces the number of potentially receivable channels.
|
|
|
|
|
|
|
|
Note that it doesn't make sense to use "Satellite Channel Routing" and
|
|
|
|
"Device Bonding" at the same time with the same devices. If you use either
|
|
|
|
of these methods, it is necessary that your devices are always created in the
|
|
|
|
same sequence when the drivers are loaded. You may need to configure some
|
|
|
|
proper "udev" rules to make sure this happens.
|
2013-02-19 09:48:54 +01:00
|
|
|
If you use "Device Bonding" and you add devices to your setup that don't
|
|
|
|
provide DVB-S and take up a position in which there used to be a bonded DVB-S
|
|
|
|
device, make sure you open, adjust (if necessary) and confirm the Setup/LNB
|
|
|
|
menu to have the device bondings set correctly again.
|
2011-12-04 12:45:26 +01:00
|
|
|
|
2001-11-24 11:42:43 +01:00
|
|
|
Running VDR with DVB-C (cable) or DVB-T (terrestrial):
|
|
|
|
------------------------------------------------------
|
|
|
|
|
|
|
|
VDR automatically recognizes if the DVB card in use is a cable or a
|
|
|
|
terrestrial card. The only thing that needs to be different when using digital
|
|
|
|
cable or terrestrial reception is the 'channels.conf' file. The distribution
|
|
|
|
archive contains a default 'channels.conf.cable' and 'channels.conf.terr',
|
|
|
|
respectively, which users of such cards can rename or copy to 'channels.conf'
|
|
|
|
in order to receive digital cable or terrestrial channels. The format of these
|
2002-11-01 10:43:16 +01:00
|
|
|
files is mostly the same as for satellite channels, however, some fields have
|
|
|
|
different or extended meanings (see man vdr(5) for details).
|
2001-11-24 11:42:43 +01:00
|
|
|
|
|
|
|
You can even use a mixture of DVB-S, DVB-C and DVB-T cards in the same system.
|
|
|
|
All you need to do is to put all the channel definitions into one big
|
2002-11-01 10:43:16 +01:00
|
|
|
'channels.conf' file. VDR will automatically know which channels can be
|
|
|
|
received with which card(s) by evaluating the 'source' parameter.
|
2001-02-24 11:55:10 +01:00
|
|
|
|
2000-04-24 10:40:00 +02:00
|
|
|
Learning the remote control keys:
|
|
|
|
---------------------------------
|
|
|
|
|
2002-09-29 13:40:45 +02:00
|
|
|
There is no default 'remote.conf' file, so 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-04-24 10:40:00 +02:00
|
|
|
|
2002-09-29 13:40:45 +02:00
|
|
|
The recommended PC key assignments are:
|
2000-04-24 10:40:00 +02:00
|
|
|
|
2013-10-12 12:56:31 +02:00
|
|
|
Up, Down, Left, Right Cursor keys
|
|
|
|
Menu 'Home'
|
2002-04-01 12:24:35 +02:00
|
|
|
Ok 'Enter'
|
2013-10-12 12:56:31 +02:00
|
|
|
Back 'Backspace'
|
2000-04-24 10:40:00 +02:00
|
|
|
Red, Green, Yellow, Blue 'F1'..'F4'
|
2013-10-12 12:56:31 +02:00
|
|
|
0..9 '0'..'9'
|
|
|
|
Volume+/- 'PgUp', 'PgDn'
|
|
|
|
Mute 'F10'
|
|
|
|
|
|
|
|
If you want to change your key assignments later, simply delete the file
|
|
|
|
'remote.conf' and restart 'vdr' to get into learning mode.
|
2000-07-15 12:39:20 +02:00
|
|
|
|
2002-12-15 15:36:02 +01:00
|
|
|
Generating source code documentation:
|
|
|
|
-------------------------------------
|
|
|
|
|
|
|
|
You can do a 'make srcdoc' to generate source code documentation using the
|
2003-09-09 19:03:29 +02:00
|
|
|
Doxygen tool. To do so you need the Doxygen package from http://www.doxygen.org
|
2002-12-15 15:36:02 +01:00
|
|
|
and the Graphviz package from http://www.research.att.com/sw/tools/graphviz.
|
|
|
|
After installing these two packages you can do 'make srcdoc' and then use your
|
|
|
|
HTML browser to read srcdoc/html/index.html.
|