Successive timers fail

[QBox User]

Successive recordings failed. Both were on same channel and used same device. (A second device was available.)

Program 1 recorded OK, 20 minutes duration with -2 minute start time, +10 minute stop and "Nothing" post-record

Program 2 started OK, 55 minutes duration with -2 minute start time +10 minute stop and "Standby" post-record, but recording stopped after 7 minutes (while P1 was still recording), with no Standby.

 

Program 1 log file:

BBC TWO Scot 29/09/2011
D:\TV Recordings\DVBViewer\Recording Service\2011-09-29_23-58-02_BBC TWO Scot_Dame Shirley Bassey at the....ts
Device: IT9135 BDA Filter (1)
23:58:02 / 00:00:00 (~ 0.00 MB) Start
00:30:01 / 00:31:58 (~ 812.22 MB) Stop

 

Program 2 log file:

BBC TWO Scot 30/09/2011
D:\TV Recordings\DVBViewer\Recording Service\2011-09-30_00-18-00_BBC TWO Scot_Imagine... Dame Shirley Bassey....ts
Device: IT9135 BDA Filter (1)
00:18:00 / 00:00:00 (~ 0.00 MB) Start
00:25:00 / 00:07:00 (~ 176.95 MB) Stop

 

P2.txt contains the programme details for P1. The two .txt files are identical except for "Size" and the following lines:

 

P1: Created=29.09.2011 23:58:02

P2: Created=30.09.2011 00:18:00

 

P1: TimerID={9839FC78-1924-45E0-8498-C27829240726}

P2: TimerID={33FAD04F-FE9B-48B0-BD5F-40A07785475E}

 

Both timers were set from the RS "Channel EPG" web-page. To verify the P2 timings, here is the epgdebug.log for the channel during this period:

29.09.11 23:58:02.987 BBC TWO Scot     running - 29/09/2011 22:30:00 - Today at Conference - 63300 - PDC:0
29.09.11 23:58:03.963 BBC TWO Scot     not running - 29/09/2011 23:00:00 - Dame Shirley Bassey at the... - 64134 - PDC:0
30.09.11 00:00:23.964 BBC TWO Scot     running - 29/09/2011 23:00:00 - Dame Shirley Bassey at the... - 64134 - PDC:0
30.09.11 00:00:24.960 BBC TWO Scot     not running - 29/09/2011 23:20:00 - Imagine... Dame Shirley Bassey... - 64135 - PDC:0
30.09.11 00:18:00.992 BBC TWO Scot     not running - 29/09/2011 23:20:00 - Imagine... Dame Shirley Bassey... - 64135 - PDC:0
30.09.11 00:18:00.992 BBC TWO Scot     not running - 29/09/2011 23:20:00 - Imagine... Dame Shirley Bassey... - 64135 - PDC:0
30.09.11 00:18:01.968 BBC TWO Scot     running - 29/09/2011 23:00:00 - Dame Shirley Bassey at the... - 64134 - PDC:0
30.09.11 00:18:01.968 BBC TWO Scot     running - 29/09/2011 23:00:00 - Dame Shirley Bassey at the... - 64134 - PDC:0
30.09.11 00:19:48.020 BBC TWO Scot     running - 29/09/2011 23:20:00 - Imagine... Dame Shirley Bassey... - 64135 - PDC:0
30.09.11 00:19:48.020 BBC TWO Scot     running - 29/09/2011 23:20:00 - Imagine... Dame Shirley Bassey... - 64135 - PDC:0
30.09.11 00:19:48.975 BBC TWO Scot     not running - 30/09/2011 00:15:00 - BBC News - 61252 - PDC:0
30.09.11 00:19:48.975 BBC TWO Scot     not running - 30/09/2011 00:15:00 - BBC News - 61252 - PDC:0

 

Finally, the svcdebug.log shows a single recording for the period.

 

29.09.11 23:58:01.987 Opendevice       bvUnknown
29.09.11 23:58:01.988 TRecording Allocate IT9135 BDA Filter (1)
29.09.11 23:58:01.988 StartRecording   IT9135 BDA Filter (1)
29.09.11 23:58:02.897 StartRecording:  BBC TWO Scot
29.09.11 23:58:02.991 AddReference     TRecording: 2
29.09.11 23:59:57.487 AddReference     webserver: 3
30.09.11 00:00:23.860 TUCCommandClient DelPid: 0	260	5400	5401	5403	3845	3846	3847	3848
30.09.11 00:00:25.180 TUCCommandClient DelPid: 3842	2321	2322	2323	2329
30.09.11 00:00:25.181 TUCCommandClient Release TBS QBOX DVB-S2 Tuner (3)
30.09.11 00:00:25.181 TUCCommandClient Destroy TBS QBOX DVB-S2 Tuner (3)
30.09.11 00:00:25.215 TUCCommandClient Destroyed TBS QBOX DVB-S2 Tuner (3)
30.09.11 00:00:25.215 TUCCommandClient hamDeleted TBS QBOX DVB-S2 Tuner (3)
30.09.11 00:00:25.216 Releasereference CmdClientDisconnect: 2

 

I have not yet upgraded from 1.9.1, but can see nothing in 1.9.2 Changes that might affect this. I don't think UK DVB-T uses PDC.

 

Does the user need to trim timebuffer end/start times to zero for successive recordings?

 

 

Disclaimer: QBoxUser wishes to point out that the above recording attempts should not infer any membership of the Shirley Bassey fan club as they could have been made on the request of a relative.

Recording Service.zip

[Webturtle]

Hello QBox User,

 

I have made many successive recordings without any of your problems (German TV). My timebuffers before and after recordings are 10 minutes. I think you don't have to trim the timebuffers to zero.

 

 

With many greetings

 

Webturtle

[QBox User]

Thanks for replying. Most of mine have been OK as well, but I have had a couple of previous failures. This is the first that provides some evidence of error within the program. A couple of attempts today have gone OK, with no errors, so it's not the recording overlap that's to blame. I have set another pair of recordings over midnight to see if the date change could have an effect.

 

Might be helpful if a developer could say where the details come from for the *.txt file - is it always directly from svctimers.xml, or can the data be modified by another process? I'm puzzled how the P2 file could have got the P1 information.

[QBox User]

P2 should have stopped at 00:25 UTC

It actually stopped at 00:25 Local - exactly 1 hour too soon.

Maybe a clue?

 

In a previous issue I reported -

http://www.DVBViewer.tv/forum/topic/46801-runaway-recording/page__p__344646__fromsearch__1#entry344646

- the stop time was changed from 00:40 to 22:40 - 2 hours early (actually 22 hours too late). In that case, the original programme duration exceeded one hour. As above, the txt file contained the wrong program details, and it was the second of two successive recordings on the same channel.

 

If it was a time conversion error, users in a different zone might not see the same issue, but it should be reproducible (at least until UK changes to UTC+0 this month), so I'll keep trying.

[Webturtle]

Hello QBox User,

 

I think the information in the Info.txt comes from the EPG-Date of the recorded program.

 

I had an Info.txt with the name a.txt from the movie "A" an the information of the movie "B". The reason was, that there had be a change in the program planning.

 

 

With many greetings

 

Webturtle

[QBox User]

Further occurrences

a. Short test timer over midnight did not record at all. This was the first of two successive recordings, rather than the second as above. Since there was no log or txt files, I have no details.

 

b. Weekly timer over midnight next Saturday/Sunday caused a clash with timer late on Sunday. On a closer look, the first timer had 20 hours added to its previous setting (00:20 > 20:20). I've been taking snapshots of the timers file. This is the affected timer:

<Timer Type="1" ID="{5C70F6D9-D96C-49D1-97C2-EE48A52AD74B}" Enabled="-1" Priority="50" Date="08.10.2011" Start="22:14:00" Dur="126" Days="-----T-" Action="0">

<Timer Type="1" ID="{5C70F6D9-D96C-49D1-97C2-EE48A52AD74B}" Enabled="-1" Priority="50" Date="15.10.2011" Start="22:14:00" Dur="1326" Days="-----T-" Action="0">

I had edited this timer recently, but only to change the date from 8th to 15th, as the programme wasn't shown this week-end. The error could have occurred when the change was saved - presumably, the times would have been recalculated.

This is quite similar to what happened in my earlier "runaway recording".

 

I'm a bit puzzled no one else is seeing this, and wondering what could be different in my system or settings. For now, I have changed the time zone from automatic to manual, but left it at +60 minutes.