Re: [vdr] VPS autotimer stopped prematurely
Hans-Peter Jansen wrote: > Hmm, to clarify: the reliability of VPS is impaired starting from > 00:00 CET up to which time? Which times are impared, start and/or end > time? All events are stopped (status 1) on 0100 CET/0200 CEST. So if you have an event that runs from 0030 CET to 0130 CET, it will stop (status 1) on 0100 CET. For the next event, in this case starting at 0130, everything will be okay, so status 4 will be transmitted at the correct time. So for every programme which will end (or might end in the case of a delay) after 0100 CET/0200 CEST, you'll have to take into account that the VPS timer will stop at 0100/0200. > Maybe Klaus could syslog some more detailed infos regarding the > deviation, and possibly check the values semantically, e.g. in this > case, vdr could have checked the original duration, compared with the > broadcasted one, and better had used the longer one.. Could that be a > useful strategy? Does anybody see downsides? No, I don't think this is the right way. This is really something the broadcaster has to fix. Regards, Andreas. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VPS autotimer stopped prematurely
[Resend, since it didn't made it to the list..] Dear Andreas, Am Mittwoch, 7. März 2007 17:33 schrieb Andreas Mueller: > > > > Yesterday we decided to watch the new Dittsche programme from Monday > > night, but had to notice, that the recording stopped prematurely: > > > > 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. I can imagine that this is a quichotesque undertaking.. > It seems to affect at least all stations which belong to the ARD, every > night on UTC (so 0100 MET for now, in the summer you will notice > it happens on 0200 UTC) Hmm, to clarify: the reliability of VPS is impaired starting from 00:00 CET up to which time? Which times are impared, start and/or end time? Maybe Klaus could syslog some more detailed infos regarding the deviation, and possibly check the values semantically, e.g. in this case, vdr could have checked the original duration, compared with the broadcasted one, and better had used the longer one.. Could that be a useful strategy? Does anybody see downsides? Maybe time to get my feet wet with vdr hacking (but my c++ brain is quite rusty..) Thanks for your helpful answer, Andreas. Kind regards, Pete ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VPS autotimer stopped prematurely
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: [3975] channel 1 (Das Erste) event Die > 06.03.2007 00:35-01:05 (VPS: 06.03 00:35) 'Dittsche' status 2 Mar 6 [...] > vdr: [3975] 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: [3975] 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 UTC (so 0100 MET for now, in the summer you will notice it happens on 0200 UTC) Regards, Andreas ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
