Unlikely to work without changes (see end of text) .....
Code:
The VPS-plugin can determine whether a mission begins earlier or lasts longer than the timer is programmed. For this, the channels provide reliable data.
Features:
- Each timer can be enabled VPS
- Evaluation of the Running status of a program (not running, starts in a few seconds, pausing, running)
- Enter the VPS / PDC time possible
- Control-flow time (eg 10 minutes before the actual beginning of the recording captures the plugin to the monitoring of running status)
- Recordings can be completely controlled by the sender information, ie the programmed timer periods are not observed.
The channels provide reliable data? (Running status)
ARD and ZDF to provide for their shipments usually an accurate running status.
Sky delivers (for the Sky-owned channels and some non-transmitters) are often an accurate running status. Unlike ARD / ZDF, the (program) advertising before / after a show but as a "running" is specified.
The private stations adjust their status to not running when a program starts earlier or is coated. The VPS function should therefore not be turned on when recording from the private sector.
Exceptions seem to be TV DMAX and Servus.
What is VPS-time?
ARD and ZDF state in their EPG data, the VPS-time (PDC descriptor).
The VPS time should be the starting time published in magazines. ZDF is the time to on their website and Teletext.
be specified for manual timer programming, the VPS time when you turn the VPS function.
The VPS time can find the plugin, the event ID of the item and can then begin the evaluation of the Running status. When programming via the EPG must not VPS time be specified because, in the case already saved an event ID in the timer.
This looks for the plug after the VPS time, no name for the timer must be specified. The Name and Description fields are filled in by the plugin if a program of the VPS time is found.
What does complete control of broadcasting information?
When this feature is enabled (in the plugin settings and the timer!), Then the plugin can start recording only when the mission is stated as "running", and ends the timer when the Running status to "not running "is set. In that case, the programmed timer periods are therefore not considered for inclusion. The start time of the timer should be programmed but still correct, since this time will be used for this, from when the plug begins to monitor the timer.
The disadvantage of the function is that the program möglicherwise or not taken wrong, when the station is giving incorrect information. This is even on ARD / ZDF irregular times the case.
If the function is not used, then considered the plugin the programmed start and end time and can start recording only if, sooner or run longer, never shorter.
Lead-Time Control
The plugin by default starts 10 minutes before the actual start of recording to monitor the running status.
If no free tuner is there, then tried the plugin on the current transponder / channel for information search. ARD will broadcast e.g. on their transponders and EPG information from ZDF and vice versa. However, it is expected with a slight delay.
For timers that are to be controlled by the sender information on the plugin if necessary in order for the lead time on the included transmitter.
Installation
The plugin is installed like any other.
To use the functions must be changed two files (/ usr/lib/enigma2/python/RecordTimer.py and / usr/lib/enigma2/python/Screens/TimerEntry.py). The files will be patched automatically by the plugin.
Enigma has to be restarted after installation. Maybe even twice.
Originally Posted by goRt
