[vdr] VPS autotimer stopped prematurely
mailinglists at andreas-mueller.com
Wed Mar 7 17:33:22 CET 2007
Hans-Peter Jansen wrote:
> Hi *,
> my family and me greatly enjoy vdr since years, but I finally got
> around to update the system to a current state (on top of openSUSE
> 10.2) lately. The system is running dedicated for vdr (1.4.5)
> purposes, using two hauppauge ff 2.1 cards.
> Yesterday we decided to watch the new Dittsche programme from Monday
> night, but had to notice, that the recording stopped prematurely:
> Mar 6 00:39:46 ziggy vdr:  channel 1 (Das Erste) event Die
> 06.03.2007 00:35-01:05 (VPS: 06.03 00:35) 'Dittsche' status 2 Mar 6
> vdr:  channel 1 (Das Erste) event Die 06.03.2007 00:35-01:05
> (VPS: 06.03 00:35) 'Dittsche' status 4
> Mar 6 01:00:43 ziggy vdr:  channel 1 (Das Erste) event Die
> 06.03.2007 00:35-01:05 (VPS: 06.03 00:35) 'Dittsche' status 1
> The clock is reliable (adjusted via NTP), thus vdr happened to start
> the recording at 00:39:46, about 48 sec before the broadcast started,
> very nice so far. But what happened at 01:00:43?
This is a problem I also have. The fault is in the broadcaster's system.
I've wrote a number of emails to the support of the ARD, but they seem
to ignore the problem and claim that everything is OK on their side.
Instead, they suspected a problem with my setup, or that the problem is
caused somewhere between the playout center (which is in Potsdam) and
the actual transmitters, or that this problem is only related to the
reception technique used (I use DVB-T, but I've already seen this on
DVB-S and thus it should be the same with DVB-C). They've also
suggested to not use VPS because of this.
For each email I wrote they needed at least two weeks to answer. I gave
up on this (for now) because I have better things to do instead of
writing long mails to tv stations.
It seems to affect at least all stations which belong to the ARD, every
night on 0000 UTC (so 0100 MET for now, in the summer you will notice
it happens on 0200 UTC)
More information about the vdr