RS don't restart recording after 60 seconds

[jirim100]

In RS is set to restart after 60 seconds when no data, but it was not happen. In log file is the following:

 

CS film / CS mini / Horor film 27.6.2015
W:\For The Record\Šest černých dívek aneb Proč zmizel Zajíc otazník; film; ČSR; 1969; nahráno 2015-06-27.ts
Device: USB 2.0 BDA DVB-C Tuner (6)
11:45:03 / 0:00:00 (~ 0,00 MB) Start
11:45:24 / 0:00:21 (~ 0,54 MB) PID 385: MPEG2 Video, 16:9, 720x576, 25 fps
11:45:24 / 0:00:21 (~ 0,54 MB) PID 386: MPEG Audio Stereo, 48 khz, 192 kbps
13:45:00 / 1:59:57 (~ 100,34 MB) Stop
Average Data Rate: 0,014 MB/s
Total Size: 100,3 MB (105208936 Bytes)

 

 

Only first 55 seconds is recorded. Recorded file you can download from here:

http://www.ulozto.net/xhW77mZu/sest-cernych-divek-aneb-proc-zmizel-zajic-otaznik-film-csr-1969-nahrano-2015-06-27-ts?_ga=1.44473572.1756732281.1400416334

 

When no data from the beginning time of recording then restarting recording working ok, but in this case not.

support.zip

Edited June 27, 2015 by jirim100

[Griga]

In RS is set to restart after 60 seconds when no data, but it was not happen. In log file is the following:

 

The svcdebug.log in your support.zip proves that data arrived. Have a look at

 

27.06.15 12:00:00.758 TRecording ($00D5FF10) EPG Callback...

 

($00D5FF10) is the ID of the recording that started at 11:45. The EPG Callback can only happen if EPG data arrives. "no data for 60 secs." means no data at all from the driver for 60s secs. Not a single transport stream packet.

 

Maybe data arrived, but not in a way that can be processed by the recorder. Maybe it was a CI/CAM failure, causing video/audio data not to be decrypted anymore. Cases like this are not covered by the "no data for 60 secs" option.

[jirim100]

 

Cases like this are not covered by the "no data for 60 secs" option.

 

Can you such cases include in this option?? Because for me is more important whether data are finally writen to file. May be this option could be not "no data for 60 seconds arrived from driver" but "no data for 60 seconds written to file".

[Griga]

That won't work either, because there was data written to the file: Service information and EPG data, that is not encrypted. From a certain point on video and audio data is missing. That again suggests a CI/CAM failure.

 

Maybe it would be better to look for a fix, not for a work-around.

[jirim100]

But I don't know how to fix it. Most of the time it works. Only occassionally happen this problem. For me is easier when recording is restarted, then recording again working.

 

When, for example, I buy a new CI / CAM module, I do not have confidence that this problem never arises.

Edited June 29, 2015 by jirim100

[Griga]

I think I found a solution now.

 

The obvious approach is to check for "no unencrypted video / audio data within 60 seconds". However, even that won't work in your case, because most video streams contain special data packets with timing information only (PCR, Program Clock Reference) that are unencrypted. So there is always some unencrypted data arriving, even if your CAM doesn't work.

 

Thus the Recording Service must check for "no unencrypted video/audio packets containing video/audio payload within 60 seconds". The next release will handle it this way. However, I can't test it. That will be up to you.

[jirim100]

Thank you!!

[jirim100]

The next release will handle it this way.

 

When you approximatelly release next version? Last version was released 19 October 2014, this is before 9 months.