summaryrefslogtreecommitdiff
path: root/MANUAL
diff options
context:
space:
mode:
authorKlaus Schmidinger <kls (at) cadsoft (dot) de>2004-02-29 18:00:00 +0100
committerKlaus Schmidinger <kls (at) cadsoft (dot) de>2004-02-29 18:00:00 +0100
commit5a4eb3f1041b8a53826cebe570f9d201f3d35826 (patch)
tree4444f7bec812600713430e7f0570dfdd0bf9136e /MANUAL
parent3fc29659759abb10154b78f9e3568407e523e1fc (diff)
downloadvdr-patch-lnbsharing-5a4eb3f1041b8a53826cebe570f9d201f3d35826.tar.gz
vdr-patch-lnbsharing-5a4eb3f1041b8a53826cebe570f9d201f3d35826.tar.bz2
Version 1.3.5vdr-1.3.5
- Fixed reading the EPG preferred language parameter from 'setup.conf'. - Fixed switching to a visible programme in case the current channel has neither a video nor an audio PID. - Fixed editing channels (SID now range checked) and creating new channels (NID, TID and RID are now set to 0). - Fixed transponder handling to make it work with satellites that provide two transponders on the same frequency, with different polarization, like Hispasat at S30.0W (thanks to Thomas Bergwinkl for pointing this out). See man vdr(5) for details about the enhanced channel ID format. - Since there appears to be no general solution for the UPT error yet, a recording now initiates an "emergency exit" if the number of UPT errors during one recording exceeds 10 (suggested by Gregoire Favre). Since the UPT error doesn't happen on my system, this has not been explicitly tested. The "preliminary fix" for the UPT error in VDR/dvbdevice.c has been disabled by default, since it makes channel switching unpleasently slow. If you want to have that workaround back, you can uncomment the line //#define WAIT_FOR_LOCK_AFTER_TUNING 1 in VDR/dvbdevice.c. - Adapted the 'sky' plugin to use the actual channel IDs, and to fetch EPG data from www.bleb.org. - Limited automatic retuning to devices that actually provide the transponder (necessary for the 'sky' plugin). - Fixed handling receivers in the 'sky' plugin, so that a recording on the same channel won't interrupt an ongoing Transfer Mode. - Added subtable ID and TSDT handling to 'libsi' (thanks to Marcel Wiesweg). - Fixed some Russian OSD texts (thanks to Vyacheslav Dikonov). - Added the 'running status' to the EPG events. This is necessary for implementing the VPS function for recording. - Removed the obsolete 'present' and 'following' handling from the EPG data. - The EPG data is now always kept sorted chronologically in the internal data structures. This also means that any EPG data retrieved through the SVRDP command LSTE is guaranteed to be sorted by start time. - Now using the 'running status' in the channel display, so that a programme that has an end time that is before the current time, but is still running, will still be shown in the display (provided the broadcasters handle the 'running status' flag correctly). This also applies to programmes that have a start time that is in the future, but are already running. - Implemented an "EPG linger time", which can be set to have older EPG information still displayed in the "Schedule" menu (thanks to Jaakko Hyvätti). - Added PDCDescriptor handling to 'libsi'. - Implemented handling the VPS timestamps (aka "Programme Identification Label") for full VPS support for timers (provided the tv stations actually broadcast this information). The VPS time is displayed in the event info page if it exists and is different than the event's start time. - Extended the SVDRP command LSTE to allow limiting the listed data to a given channel, the present or following events, or events at a given time (thanks to Thomas Heiligenmann). - Fixed a typo in libsi/si.h (thanks to Stéphane Esté-Gracias). - Timers can now be set to use the VPS information to control recording a programme. The new setup options "Recording/Use VPS" and "Recording/VPS margin", as well as the "VPS" option in the individual timers, can be used to control this feature (see MANUAL for details). Note that this feature will certainly need a lot of testing before it can be called "safe"! - The "Schedule" and "What's on now/next?" menus now have an additional column which displays information on whether there is a timer defined for an event, whether an event has a VPS time that's different than its start time, and whether an event is currently running (see MANUAL under "The "Schedule" Menu" for details).
Diffstat (limited to 'MANUAL')
-rw-r--r--MANUAL32
1 files changed, 32 insertions, 0 deletions
diff --git a/MANUAL b/MANUAL
index 80977a9..c4d4391 100644
--- a/MANUAL
+++ b/MANUAL
@@ -138,6 +138,16 @@ Version 1.2
The "Blue" button can be pressed to switch to the channel with the selected
programme.
+ The following markers in these menus give additional information about the
+ status of the events:
+
+ t there is a timer defined for this event which covers only part of the event
+ T there is a timer defined for this event which covers the entire event
+ V this event has a VPS time that's different than its start time
+ * this event is currently running (the validity of this marker depends on
+ whether there is currently a DVB card receiving the transponder this channel
+ is on).
+
* Selecting a Channel
There are four ways to select a channel:
@@ -351,6 +361,14 @@ Version 1.2
would have a Day setting of "M-W----".
Start: The start time of the timer in hh:mm as 24 hour ("military") time.
Stop: The stop time of the timer.
+ VPS: Defines whether the timer shall use VPS (if available). If this
+ option is set to 'yes', the start time must exactly match the
+ programme's VPS time, otherwise nothing will be recorded. If VPS
+ is used, the stop time has no real meaning. However, it must be
+ different than the start time, and should correspond to the actual
+ stop time of the programme, just in case there is no real VPS data
+ available at the time of recording, so VDR has to fall back to
+ normal timer recording.
Priority: The Priority (0..99) 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
@@ -462,6 +480,9 @@ Version 1.2
be fixed accordingly. Restart VDR if you want to make sure
all data is fixed.
+ EPG linger time = 0 The time (in minutes) within which old EPG information
+ shall still be displayed in the "Schedule" menu.
+
Set system time = no Defines whether the system time will be set according to
the time received from the DVB data stream.
Note that this works only if VDR is running under a user
@@ -582,6 +603,17 @@ Version 1.2
no = don't use the 'Episode name'
yes = use it (and create subdirectories)
+ Use VPS = 0 Defines whether a timer that is created from an EPG entry
+ (by pressing the "Record" (red) button in the "Schedules"
+ or "What's on now/next?" menu) will automatically use VPS
+ if the event it is created for has a VPS time.
+
+ VPS margin = 120 Defines how many seconds before a VPS controlled timer is
+ scheduled to start, VDR will make sure that one of the DVB
+ devices is tuned to the transponder that timer shall record
+ from. This is necessary for the "Running Status" information
+ that is broadcast in the EPG data to be seen by VDR.
+
Mark instant recording = yes
Defines whether an "instant recording" (started by
pressing the "Red" button in the "VDR" menu) will be