Hi,
from my log:
Jan 7 23:36:32 mm vdr[3539]: timer 1 (1 2240-0045 'James Bond 007 - Der Hauch des Todes') start Jan 7 23:36:32 mm vdr[3539]: record /vdr/video/James_Bond_007_-_Der_Hauch_des_Todes/2006-01-07.23.30.50.99.rec Jan 8 00:02:22 mm vdr[3539]: replay /vdr/video/James_Bond_007_-_Der_Hauch_des_Todes/2006-01-07.23.30.50.99.rec Jan 8 01:00:43 mm vdr[3544]: channel 1 (Das Erste) event 23:35 'James Bond 007 - Der Hauch des Todes' status 1 Jan 8 01:00:44 mm vdr[3539]: timer 1 (1 2240-0045 'James Bond 007 - Der Hauch des Todes') stop Jan 8 01:41:51 mm vdr[3544]: channel 1 (Das Erste) event 01:40 'Tagesschau' status 4
01:00 is about the time when the programm SHOULD have stopped. It SHOULD have started at 22:40, EPG said so. But it really started at 23:35.
VPS start was correct, but the end went wrong, it stopped about 1 hour too early. Normally it seems the time between status 1 and the next status 4 is quite short, here it was 41 minutes.
Would it be possible to change the messages status 1 etc into something more verbose?
And maybe it would help not to stop a timer before the EPG length of the program has passed, no matter what the status says.
On Sonntag 08 Januar 2006 01:59, Wolfgang Rohdewald wrote:
Jan 7 23:36:32 mm vdr[3539]: timer 1 (1 2240-0045 'James Bond 007 - Der Hauch des Todes') start Jan 7 23:36:32 mm vdr[3539]: record /vdr/video/James_Bond_007_-_Der_Hauch_des_Todes/2006-01-07.23.30.50.99.rec Jan 8 00:02:22 mm vdr[3539]: replay /vdr/video/James_Bond_007_-_Der_Hauch_des_Todes/2006-01-07.23.30.50.99.rec Jan 8 01:00:43 mm vdr[3544]: channel 1 (Das Erste) event 23:35 'James Bond 007 - Der Hauch des Todes' status 1 Jan 8 01:00:44 mm vdr[3539]: timer 1 (1 2240-0045 'James Bond 007 - Der Hauch des Todes') stop Jan 8 01:41:51 mm vdr[3544]: channel 1 (Das Erste) event 01:40 'Tagesschau' status 4
forgot to say this is 1.3.36
Wolfgang Rohdewald wrote:
Hi,
from my log:
Jan 7 23:36:32 mm vdr[3539]: timer 1 (1 2240-0045 'James Bond 007 - Der Hauch des Todes') start Jan 7 23:36:32 mm vdr[3539]: record /vdr/video/James_Bond_007_-_Der_Hauch_des_Todes/2006-01-07.23.30.50.99.rec Jan 8 00:02:22 mm vdr[3539]: replay /vdr/video/James_Bond_007_-_Der_Hauch_des_Todes/2006-01-07.23.30.50.99.rec Jan 8 01:00:43 mm vdr[3544]: channel 1 (Das Erste) event 23:35 'James Bond 007 - Der Hauch des Todes' status 1 Jan 8 01:00:44 mm vdr[3539]: timer 1 (1 2240-0045 'James Bond 007 - Der Hauch des Todes') stop Jan 8 01:41:51 mm vdr[3544]: channel 1 (Das Erste) event 01:40 'Tagesschau' status 4
01:00 is about the time when the programm SHOULD have stopped. It SHOULD have started at 22:40, EPG said so. But it really started at 23:35.
VPS start was correct, but the end went wrong, it stopped about 1 hour too early. Normally it seems the time between status 1 and the next status 4 is quite short, here it was 41 minutes.
Would it be possible to change the messages status 1 etc into something more verbose?
And maybe it would help not to stop a timer before the EPG length of the program has passed, no matter what the status says.
Well, the main problem here seems to be that the ARD hasn't handled the running status correctly. There will always be problems with VPS recordings if the broadcaster doesn't send the correct data. In this case recording until the stop time of the timer might have helped, but it still could have cut off a few minutes.
I suggest contacting the ARD, asking them why they broke the running status, and that they should handle this correctly in the future.
Klaus
On Sonntag 08 Januar 2006 11:02, Klaus Schmidinger wrote:
if the broadcaster doesn't send the correct data. In this case recording until the stop time of the timer might have helped, but it still could have cut off a few minutes.
55 minutes would have been cut off.
Since it happens practically never that a program's transmission is shortened, I still think it might help to always record at least as much as the timer length indicates.
Of course the transmission was faulty, but we still could make vdr more fault tolerant.
Since you do not want to change the log messages, is there documentation about the different runnig statuses anywhere? I really want to understand my log messages.
Wolfgang Rohdewald wrote:
On Sonntag 08 Januar 2006 11:02, Klaus Schmidinger wrote:
if the broadcaster doesn't send the correct data. In this case recording until the stop time of the timer might have helped, but it still could have cut off a few minutes.
55 minutes would have been cut off.
Since it happens practically never that a program's transmission is shortened, I still think it might help to always record at least as much as the timer length indicates.
Well, that still leaves the question whether to use the end time that has been defined in the original timer, or that of the event the timer has been set to (see cTimer::Matches(time_t t, bool Directly)).
Working around messy data is always tricky...
Of course the transmission was faulty, but we still could make vdr more fault tolerant.
Since you do not want to change the log messages, is there documentation about the different runnig statuses anywhere? I really want to understand my log messages.
From epg.h:
int runningStatus; // 0=undefined, 1=not running, 2=starts in a few seconds, 3=pausing, 4=running
Klaus
On Sonntag 08 Januar 2006 14:48, Klaus Schmidinger wrote:
Since it happens practically never that a program's transmission is shortened, I still think it might help to always record at least as much as the timer length indicates.
Well, that still leaves the question whether to use the end time that has been defined in the original timer, or that of the event the timer has been set to (see cTimer::Matches(time_t t, bool Directly)).
I personally would rather trust the original EPG data. But to be on the conservative side, you could use the smaller value.
for 1.3.36, something like this (untested, I don't understand all of this source code):
--- timers.c 2005-09-09 17:22:33.000000000 +0200 +++ timers.c.new 2006-01-08 16:14:01.000000000 +0100 @@ -364,9 +364,10 @@ bool cTimer::Matches(time_t t, bool Dire
if (HasFlags(tfActive)) { if (HasFlags(tfVps) && !Directly && event && event->Vps() && schedule && schedule->PresentSeenWithin(30)) { + time_t orgstopTime = stopTime; startTime = event->StartTime(); stopTime = event->EndTime(); - return event->IsRunning(true); + return (stopTime > t && orgstopTime > t) || event->IsRunning(true); } return startTime <= t && t < stopTime; // must stop *before* stopTime to allow adjacent timers }
Hi Klaus,
Klaus Schmidinger schrieb:
Well, that still leaves the question whether to use the end time that has been defined in the original timer, or that of the event the timer has been set to (see cTimer::Matches(time_t t, bool Directly)).
Working around messy data is always tricky...
I think, the main reason, to use vps-support, is to get the full recording, even if Gottschalk was just before. So recording at least as much as given in the timer entry would help a lot. Perhaps you could set cut marks for start and end of vps-timing, so we wouldn't miss anything, even if the events are not sent correctly, but are enabled to detect it and advise the broadcaster, to change this.
Martin
-
Klaus Schmidinger -
Martin Schoenbeck -
Wolfgang Rohdewald