Zero duration/size recordings

Grumpy_Geoff · Post by **Grumpy_Geoff** » Tue Nov 10, 2015 13:02

I've observed some zero length recordings occurring.
The T4 has decided to record some program timers twice - 2 * "activating state 1", however it never then progressed to:
"activating state 2", nor
"start recording"

This has happened twice recently, once yesterday and once this morning, I now believe it occurred the other day, I had originally put that occurrence down to me phaffing around with the T4.

Yesterday, the "Camp Lakebottom" zero length recording was a boot up to standby recording. This mornings "Rabbids Invasion" zero length recording was from the running state.

Only the one program being recorded on each occasion.

The next recording after "Camp Lakebottom" was fine (also a boot up to standby recording).
Next recording after today's "Rabbids Invasion" is set for this afernoon. The prior recording was fine (T4 came out of deep standby for that).

AutoTimers in use. FTA EPG.

Sorry, I don't yet know how to reproduce this issue.

Does this sound like another occurrence of - viewtopic.php?f=50&t=9225

Drivers: 2015-11-06
Firmware: 2015-11-06 17:33 (beta)

Cheers
Geoff

MrQuade · Post by **MrQuade** » Tue Nov 10, 2015 14:36

Grumpy_Geoff wrote: Does this sound like another occurrence of - viewtopic.php?f=50&t=9225

Probably not, but it is easy to check. Just set two manual timers to fire simultaneously on Tuners A and B and put the T4 into standby, then wait for them to fire. If it is the old bug then one of the recordings will be zero length.

Grumpy_Geoff · Post by **Grumpy_Geoff** » Tue Nov 10, 2015 15:43

MrQuade wrote:... Just set two manual timers to fire simultaneously on Tuners A and B and put the T4 into standby, then wait for them to fire. If it is the old bug then one of the recordings will be zero length.

You're right - both recorded as expected. Tuners A & B used for recordings, tuner C used for last watched service prior to standby.
You did mean from standby right, not deep standby?

The zero-length timer from last Friday that I initially discounted as this issue, appears to be the same issue - 2 lots of "state 1" entries, no "state 2" (recording) entry, eventually followed by a "state 3" (stop) at timer end.

One further observation from this morning - after I'd posted, I went to shutdown the T4 to deep standby, I was warned a recording was in progress or about to commence. Not believing the prompt, I exited and took a look at the timers and recordings folders - nada.
The InfoBar just had a 'REC' indicator for tuner A (no service) - it was as if tuner A had locked up. and I'm guessing this was the tuner used for the recording.
The same may have occurred yesterday, given it was the only timer at the time.

Cheers
Geoff

MrQuade · Post by **MrQuade** » Tue Nov 10, 2015 16:08

Grumpy_Geoff wrote: You're right - both recorded as expected. Tuners A & B used for recordings, tuner C used for last watched service prior to standby.
You did mean from standby right, not deep standby?

Yep, normal standby.
To trigger that old bug, all you needed to do was call both A and B tuner in the same instant.

So it would also work if you were currently live viewing with Tuner C (and A and B were idle), or if you were watching a recording with no active timers running.

Grumpy_Geoff · Post by **Grumpy_Geoff** » Tue Nov 10, 2015 19:12

MrQuade wrote:Yep, normal standby.
To trigger that old bug, all you needed to do was call both A and B tuner in the same instant.

Yeah, 'tis what I did.

MrQuade wrote:So it would also work if you were currently live viewing with Tuner C (and A and B were idle), or if you were watching a recording with no active timers running.

Tuners A & B were in use for recording in standby, I think tuner C only came into play when I took the box out of standby to see if the two recordings had any content.

Should I be suspicious of the new DVB tuner drivers? - viewtopic.php?f=56&t=9751&start=20#p130597
Just enquiring

EDITED:
Forget that last point, as the last example above occurred 6/11 11:29 AWST, which is prior to that update I believe.

Cheers
Geoff

Grumpy_Geoff · Post by **Grumpy_Geoff** » Sun Nov 15, 2015 12:35

Another occurrence of the zero-duration timer occurred this morning.
No "activating state 2" nor "start recording".

This was the 2nd timer of the morning, T4 was already in running state.
"REC" status indicator was showing in InfoBar (but no program name) and on front panel

Code: Select all

<timer begin="1447545300" end="1447548300" serviceref="1:0:1:402:450:3203:EEEE0000:0:0:0:" repeated="0" rename_repeat="1" name="Teen Titans Go!" description="Yearbook Madness/Hose Water" afterevent="auto" eit="35149" location="/media/hdd/movie/Aaron&apos;s/" tags="" disabled="0" justplay="0" always_zap="0" descramble="1" record_ecm="0" isAutoTimer="1">
<log code="500" time="1446942221">[AutoTimer] Try to add new timer based on AutoTimer Teen Titans Go!.</log>
<log code="5" time="1447545280">activating state 1</log>
<log code="5" time="1447545280">activating state 1</log>
<log code="0" time="1447545280">Found enough free space to record</log>
<log code="0" time="1447545280">Filename calculated as: &apos;/media/hdd/movie/Aaron&apos;s/20151115 0755 - GO! - Teen Titans Go!&apos;</log>
<log code="6" time="1447545280">prepare ok, waiting for begin</log>
<log code="0" time="1447545280">Found enough free space to record</log>
<log code="0" time="1447545280">Filename calculated as: &apos;/media/hdd/movie/Aaron&apos;s/20151115 0755 - GO! - Teen Titans Go!_001&apos;</log>
<log code="6" time="1447545280">prepare ok, waiting for begin</log>
<log code="5" time="1447548300">activating state 3</log>
<log code="12" time="1447548300">stop recording</log>
</timer>

Grumpy_Geoff · Post by **Grumpy_Geoff** » Thu Nov 19, 2015 19:46

Another occurrence of the zero-duration timer occurred this afternoon.
No "activating state 2" nor "start recording".

T4 had been in deep standby, therefore booted for this timer.

Interesting. looking at the timers.xml file, I've observed that the timer's 'begin' time is 1447917600 (19/11 15:20:00 AWST), yet the timer log shows that it did not prepare until 7 seconds after that time (1447917607 - 19/11 15:20:07 AWST), thus it is waiting for a start time that is in the past!
This is not the same for the previous example I've shown (prepare was 20 seconds prior to supposed start)..

Code: Select all

<timer begin="1447917600" end="1447919988" serviceref="1:0:1:2E4:261:3201:EEEE0000:0:0:0:" repeated="0" rename_repeat="1" name="Dennis The Menace And Gnasher" description="Dennis and co bust out of detention./ Gnasher tunnels his way under the school to surprise Walter./ Dennis and his parents are &apos;invited&apos; to Walter&apos;s house./ Dennis & co concoct a super plant food to speed up their" afterevent="auto" eit="28669" location="/media/hdd/movie/Aaron&apos;s/" tags="" disabled="0" justplay="0" always_zap="0" descramble="1" record_ecm="0" isAutoTimer="1">
<log code="500" time="1447314550">[AutoTimer] Try to add new timer based on AutoTimer Dennis & Gnasher.</log>
<log code="15" time="1447400948">record time changed, start prepare is now: Thu Nov 19 15:20:07 2015</log>
<log code="5" time="1447917607">activating state 1</log>
<log code="5" time="1447917607">activating state 1</log>
<log code="0" time="1447917607">Found enough free space to record</log>
<log code="0" time="1447917607">Filename calculated as: &apos;/media/hdd/movie/Aaron&apos;s/20151119 1520 - ABC3 - Dennis The Menace And Gnasher&apos;</log>
<log code="0" time="1447917607">Found enough free space to record</log>
<log code="0" time="1447917607">Filename calculated as: &apos;/media/hdd/movie/Aaron&apos;s/20151119 1520 - ABC3 - Dennis The Menace And Gnasher&apos;</log>
<log code="6" time="1447917607">prepare ok, waiting for begin</log>
<log code="6" time="1447917607">prepare ok, waiting for begin</log>
<log code="15" time="1447919384">record time changed, start prepare is now: Thu Nov 19 15:19:40 2015</log>
<log code="5" time="1447919988">activating state 3</log>
<log code="12" time="1447919988">stop recording</log>
</timer>

Is anyone else seeing this?

Cheers
Geoff

Grumpy_Geoff · Post by **Grumpy_Geoff** » Sat Nov 21, 2015 13:24

Another occurrence of the zero-duration timer occurred yesterday 'arvo.
Again, two entries for "activating state 1" - no "activating state 2" / "start recording".

Timer prepared at 15:57:37, 20 seconds prior to supposed start, but never started to record at 15:57:57

Code: Select all

<timer begin="1448006277" end="1448007888" serviceref="1:0:1:2E4:261:3201:EEEE0000:0:0:0:" repeated="0" rename_repeat="1" name="Numb Chucks" description="Using their imaginary &apos;kung-fu-bility&apos;, Dilweed and Fungus have now devoted their lives to doing good deeds and protecting the quiet woodland town of Ding-a-Ling Springs and its citizens using their imaginary &apos;kung fu&apos; skills" afterevent="auto" eit="28731" location="/media/hdd/movie/Aaron&apos;s/" tags="" disabled="0" justplay="0" always_zap="0" descramble="1" record_ecm="0" isAutoTimer="1">
<log code="500" time="1447400953">[AutoTimer] Try to add new timer based on AutoTimer Numb Chucks.</log>
<log code="15" time="1447660068">record time changed, start prepare is now: Fri Nov 20 15:57:37 2015</log>
<log code="5" time="1448006257">activating state 1</log>
<log code="5" time="1448006257">activating state 1</log>
<log code="0" time="1448006257">Found enough free space to record</log>
<log code="0" time="1448006257">Filename calculated as: &apos;/media/hdd/movie/Aaron&apos;s/20151120 1557 - ABC3 - Numb Chucks&apos;</log>
<log code="6" time="1448006257">prepare ok, waiting for begin</log>
<log code="0" time="1448006257">Found enough free space to record</log>
<log code="0" time="1448006257">Filename calculated as: &apos;/media/hdd/movie/Aaron&apos;s/20151120 1557 - ABC3 - Numb Chucks_001&apos;</log>
<log code="6" time="1448006257">prepare ok, waiting for begin</log>
<log code="5" time="1448007888">activating state 3</log>
<log code="12" time="1448007888">stop recording</log>
</timer>

Timers starting before (15:20) and after (16:53) the failed (15:57) timer recorded successfully - all were for the same service:

Numb Chucks
20.11.2015 15:57 - 20.11.2015 16:24
ABC3
Using their imaginary 'kung-fu-bility', Dilweed and Fungus have {snipped}
finished

Dennis The Menace And Gnasher
20.11.2015 15:20 - 20.11.2015 16:00
ABC3
Dennis ends up permanently attached to Walter./ Dennis & Gnasher make {snipped}
finished

Camp Lakebottom
20.11.2015 16:43 - 20.11.2015 17:14
ABC3
During a heat wave, McGee and the gang bring back a glacier and find a tiny {snipped}
finished

It's strange that I'm the only one experiencing this!

Cheers,
Geoff

Grumpy_Geoff · Post by **Grumpy_Geoff** » Tue Nov 24, 2015 15:05

Another occurrence of the zero-duration timer occurred Monday 'arvo.
Again, two entries for "activating state 1" - no "activating state 2" / "start recording".

Timer prepared at 16:42:13, 20 seconds prior to supposed start, but never started to record at 16:42:33.

Boot from deep standby @ 16:38.
The two timers before this recorded successfully and all three timers were on same service -

Code: Select all

<timer begin="1448268153" end="1448270081" serviceref="1:0:1:2E4:261:3201:EEEE0000:0:0:0:" repeated="0" rename_repeat="1" name="Camp Lakebottom" description="McGee is thrilled when he wins a mounted horse head, until the horse head&apos;s evil body starts stealing the Bottom Dwellers noggins in a rodeo rampage." afterevent="auto" eit="28895" location="/media/hdd/movie/Aaron&apos;s/" tags="" disabled="0" justplay="0" always_zap="0" descramble="1" record_ecm="0" isAutoTimer="1">
<log code="500" time="1447660059">[AutoTimer] Try to add new timer based on AutoTimer Camp Lakebottom.</log>
<log code="15" time="1447746587">record time changed, start prepare is now: Mon Nov 23 16:42:13 2015</log>
<log code="5" time="1448268133">activating state 1</log>
<log code="5" time="1448268133">activating state 1</log>
<log code="0" time="1448268133">Found enough free space to record</log>
<log code="0" time="1448268133">Filename calculated as: &apos;/media/hdd/movie/Aaron&apos;s/20151123 1642 - ABC3 - Camp Lakebottom&apos;</log>
<log code="0" time="1448268133">Found enough free space to record</log>
<log code="6" time="1448268133">prepare ok, waiting for begin</log>
<log code="0" time="1448268133">Filename calculated as: &apos;/media/hdd/movie/Aaron&apos;s/20151123 1642 - ABC3 - Camp Lakebottom&apos;</log>
<log code="6" time="1448268133">prepare ok, waiting for begin</log>
<log code="5" time="1448270081">activating state 3</log>
<log code="12" time="1448270081">stop recording</log>
</timer>

Dennis The Menace And Gnasher
23.11.2015 15:20 - 23.11.2015 15:59
ABC3
A tiger escapes from Beanotown zoo./ Dennis & Gnasher attempt to make {snipped}
finished

Numb Chucks
23.11.2015 15:57 - 23.11.2015 16:24
ABC3
Using their imaginary 'kung-fu-bility', Dilweed and Fungus have {snipped}
finished

Camp Lakebottom
23.11.2015 16:42 - 23.11.2015 17:14
ABC3
McGee is thrilled when he wins a mounted horse head, until the horse head's {snipped}
finished

Front panel and InfoBar indicated a recording was in progress - but this wasn't true (no timers active, and nothing being written to disk).

Any suggestions as to debugging steps?

simoncasey · Post by **simoncasey** » Tue Nov 24, 2015 15:27

Is it only just those same shows that are having the problem?

Grumpy_Geoff · Post by **Grumpy_Geoff** » Tue Nov 24, 2015 16:06

Hi simoncasey,

Thanks for the reply,
Out of the 7 failures to date, only one has been for the same program.

Grumpy_Geoff · Post by **Grumpy_Geoff** » Sun Nov 29, 2015 10:48

Here we go again

Two more failed timer recordings.
Again, two entries each for "activating state 1" - no entries for "activating state 2" / "start recording", as the recordings never get to start.

One other (overlapping) recording at the time. T4 was in use at the same time playing from a network share.
When I'd finished watching from the share, I then switched the media listing back to /media/hdd/movie and noticed the 'Duration 0:00' entries.

Interesting that X-Files "S1 E2" @ 20:25 recorded successfully, but has two timers.

Fargo and The X-Files "S1 E3" failed to record anything (only *.eit, *.ts.meta, and a zero-byte *.ts - no *.ts.ap, *.ts.cuts, *.ts.sc).

Code: Select all

<timer begin="1448717100" end="1448725500" serviceref="1:0:1:325:320:3202:EEEE0000:0:0:0:" repeated="0" rename_repeat="1" name="Fargo" description="Set in 1987, a pregnant Minnesota police chief investigates a string of roadside homicides after a struggling car salesman hires two criminals to kidnap his wife. Stars William H. Macy. #SBSMovie" afterevent="deepstandby" eit="14987" tags="Fargo" disabled="0" justplay="0" always_zap="0" descramble="1" record_ecm="0" isAutoTimer="1">
<log code="500" time="1448094485">[AutoTimer] Try to add new timer based on AutoTimer Fargo.</log>
<log code="5" time="1448717080">activating state 1</log>
<log code="0" time="1448717080">Found enough free space to record</log>
<log code="5" time="1448717080">activating state 1</log>
<log code="0" time="1448717080">Filename calculated as: &apos;/media/hdd/movie/20151128 2125 - SBS HD - Fargo&apos;</log>
<log code="6" time="1448717080">prepare ok, waiting for begin</log>
<log code="0" time="1448717080">Found enough free space to record</log>
<log code="0" time="1448717080">Filename calculated as: &apos;/media/hdd/movie/20151128 2125 - SBS HD - Fargo_001&apos;</log>
<log code="6" time="1448717080">prepare ok, waiting for begin</log>
<log code="5" time="1448725500">activating state 3</log>
<log code="12" time="1448725500">stop recording</log>
</timer>

<timer begin="1448717100" end="1448722500" serviceref="1:0:1:681:607:1014:EEEE0000:0:0:0:" repeated="0" rename_repeat="1" name="The X-Files" description="S1 E3: Squeeze. The Essential X-Files Collection has been personally curated by writer Chris Carter to include episodes that are not only fan favourites, but are also a crucial guide to the essence of" afterevent="auto" eit="24273" tags="The_X-Files" disabled="0" justplay="0" always_zap="0" descramble="1" record_ecm="0" isAutoTimer="0">
<log code="5" time="1448717080">activating state 1</log>
<log code="5" time="1448717080">activating state 1</log>
<log code="0" time="1448717080">Found enough free space to record</log>
<log code="0" time="1448717080">Found enough free space to record</log>
<log code="0" time="1448717080">Filename calculated as: &apos;/media/hdd/movie/20151128 2125 - ONE - The X-Files&apos;</log>
<log code="6" time="1448717080">prepare ok, waiting for begin</log>
<log code="0" time="1448717080">Filename calculated as: &apos;/media/hdd/movie/20151128 2125 - ONE - The X-Files_001&apos;</log>
<log code="6" time="1448717080">prepare ok, waiting for begin</log>
<log code="5" time="1448722500">activating state 3</log>
<log code="12" time="1448722500">stop recording</log>
</timer>

<timer begin="1448713500" end="1448718900" serviceref="1:0:1:681:607:1014:EEEE0000:0:0:0:" repeated="0" rename_repeat="1" name="The X-Files" description="S1 E2: Deep Throat. The Essential X-Files Collection has been personally curated by writer Chris Carter to include episodes that are not only fan favourites, but are also a crucial guide to the essenc" afterevent="auto" eit="24272" tags="The_X-Files" disabled="0" justplay="0" always_zap="0" descramble="1" record_ecm="0" isAutoTimer="0">
<log code="5" time="1448713480">activating state 1</log>
<log code="0" time="1448713480">Found enough free space to record</log>
<log code="0" time="1448713480">Filename calculated as: &apos;/media/hdd/movie/20151128 2025 - ONE - The X-Files&apos;</log>
<log code="6" time="1448713480">prepare ok, waiting for begin</log>
<log code="5" time="1448713500">activating state 2</log>
<log code="11" time="1448713500">start recording</log>
<log code="5" time="1448718900">activating state 3</log>
<log code="12" time="1448718900">stop recording</log>
<log code="5" time="1448718900">activating state 3</log>
<log code="12" time="1448718900">stop recording</log>
</timer>

<timer begin="1448713500" end="1448718900" serviceref="1:0:1:681:607:1014:EEEE0000:0:0:0:" repeated="0" rename_repeat="1" name="The X-Files" description="S1 E2: Deep Throat. The Essential X-Files Collection has been personally curated by writer Chris Carter to include episodes that are not only fan favourites, but are also a crucial guide to the essenc" afterevent="auto" eit="24272" tags="The_X-Files" disabled="0" justplay="0" always_zap="0" descramble="1" record_ecm="0" isAutoTimer="0">
<log code="5" time="1448713480">activating state 1</log>
<log code="0" time="1448713480">Found enough free space to record</log>
<log code="0" time="1448713480">Filename calculated as: &apos;/media/hdd/movie/20151128 2025 - ONE - The X-Files&apos;</log>
<log code="6" time="1448713480">prepare ok, waiting for begin</log>
<log code="5" time="1448713500">activating state 2</log>
<log code="11" time="1448713500">start recording</log>
<log code="5" time="1448718900">activating state 3</log>
<log code="12" time="1448718900">stop recording</log>
<log code="5" time="1448718900">activating state 3</log>
<log code="12" time="1448718900">stop recording</log>
</timer>

Any debugging/logging ideas?

Edited to add - I noticed tuners A and B were in use, which makes sense (ONE and SBS HD).

Cheers
Geoff

IanSav · Post by **IanSav** » Sun Nov 29, 2015 11:30

Hi Geoff,

Could you please provide a file listing of the contents of /etc/enigma2 on the unit giving you all the grief.

Regards,
Ian.

prl · Post by **prl** » Sun Nov 29, 2015 12:06

I find this strange:

Code: Select all

<log code="5" time="1448717080">activating state 1</log>
<log code="0" time="1448717080">Found enough free space to record</log>
<log code="5" time="1448717080">activating state 1</log>
<log code="0" time="1448717080">Filename calculated as: &apos;/media/hdd/movie/20151128 2125 - SBS HD - Fargo&apos;</log>
<log code="6" time="1448717080">prepare ok, waiting for begin</log>
<log code="0" time="1448717080">Found enough free space to record</log>
<log code="0" time="1448717080">Filename calculated as: &apos;/media/hdd/movie/20151128 2125 - SBS HD - Fargo_001&apos;</log>
<log code="6" time="1448717080">prepare ok, waiting for begin</log>
<log code="5" time="1448725500">activating state 3</log>

That's taken from the Fargo recording, but the X-File S1 E3 log is the same.

Do two recordings for each of those timers show up in the Movie Player, with one of them empty, and the other a proper recording?

Code: Select all

Interesting that X-Files "S1 E2" @ 20:25 recorded successfully, but has two timers.

Did it actually have two timers?

The Fargo timer seems to be coming from an AutoTimer, but the X-Files recordings seem to be from one-off manual timers. Is that correct?

Grumpy_Geoff · Post by **Grumpy_Geoff** » Sun Nov 29, 2015 17:11

IanSav wrote:Hi Geoff,

Could you please provide a file listing of the contents of /etc/enigma2 on the unit giving you all the grief.

Regards,
Ian.

Hi Ian.

Listing as requested -

Code: Select all

beyonwiz 4.4 beyonwizt4


beyonwizt4 login: root
root@beyonwizt4:~#
root@beyonwizt4:~# pwd
/home/root
root@beyonwizt4:~# cd /etc/enigma2
root@beyonwizt4:/etc/enigma2# ls -al
drwxr-xr-x    2 root     root          2232 Nov 29 12:11 .
drwxr-xr-x   36 root     root          7144 Nov 29 10:49 ..
-rw-r--r--    1 root     root            42 Sep 22 20:29 GRUMPY-I5-STUDY.cache
-rw-r--r--    1 root     root           373 Nov 17 16:37 automounts.xml
-rw-r--r--    1 root     root         13190 Nov 29 09:36 autotimer.xml
-rw-r--r--    1 root     root             0 Nov 29 09:36 blacklist
-rw-r--r--    1 root     root           211 Sep 22 19:10 bouquets.radio
-rw-r--r--    1 root     root           485 Nov 20 11:39 bouquets.tv
-rw-r--r--    1 root     root        947410 Nov 29 09:36 epg.dat
-rw-r--r--    1 root     root           195 Nov  7 12:48 epgrefresh.xml
-rw-r--r--    1 root     root          3187 Nov 29 09:36 lamedb
-rw-r--r--    1 root     root          1443 Nov 26 09:26 lcndb
-rw-r--r--    1 root     root           161 Nov  5 19:57 movietags
-rw-r--r--    1 root     root           220 Nov 17 16:36 networkbrowser.cache
-rw-r--r--    1 root     root             0 Oct 19 11:17 playlist.e2pls
-rw-r--r--    1 root     root           787 Nov 29 09:36 pm_timers.xml
-rw-r--r--    1 root     root          3052 Nov 29 10:50 profile
-rw-r--r--    1 root     root          5221 Nov 29 09:36 resumepoints.pkl
-rw-r--r--    1 root     root          2604 Nov  5 19:58 seriesplugin_patterns.json
-rw-r--r--    1 root     root          5318 Nov 29 09:36 settings
-rw-r--r--    1 root     root        180611 Nov 29 12:11 timers.xml
-rw-r--r--    1 root     root          1687 Nov 26 09:26 userbouquet.LastScanned.tv
-rw-r--r--    1 root     root           293 Nov 26 12:09 userbouquet.epgrefresh__tv_.tv
-rw-r--r--    1 root     root            26 Sep 22 19:09 userbouquet.favourites.radio
-rw-r--r--    1 root     root           924 Nov 26 10:35 userbouquet.favourites.tv
-rw-r--r--    1 root     root           250 Nov 26 10:29 userbouquet.hd_channels__tv_.tv
-rw-r--r--    1 root     root          6609 Nov 26 09:26 userbouquet.terrestrial_lcn.radio
-rw-r--r--    1 root     root          7034 Nov 26 09:26 userbouquet.terrestrial_lcn.tv
-rw-r--r--    1 root     root             0 Nov 29 09:36 whitelist
root@beyonwizt4:/etc/enigma2#

Cheers,
Geoff

Grumpy_Geoff · Post by **Grumpy_Geoff** » Sun Nov 29, 2015 17:24

prl wrote:I find this strange:

Code: Select all

<log code="5" time="1448717080">activating state 1</log>
<log code="0" time="1448717080">Found enough free space to record</log>
<log code="5" time="1448717080">activating state 1</log>
<log code="0" time="1448717080">Filename calculated as: &apos;/media/hdd/movie/20151128 2125 - SBS HD - Fargo&apos;</log>
<log code="6" time="1448717080">prepare ok, waiting for begin</log>
<log code="0" time="1448717080">Found enough free space to record</log>
<log code="0" time="1448717080">Filename calculated as: &apos;/media/hdd/movie/20151128 2125 - SBS HD - Fargo_001&apos;</log>
<log code="6" time="1448717080">prepare ok, waiting for begin</log>
<log code="5" time="1448725500">activating state 3</log>

That's taken from the Fargo recording, but the X-File S1 E3 log is the same.

Do two recordings for each of those timers show up in the Movie Player, with one of them empty, and the other a proper recording?

Hi Peter,

Two files each - yes, but both are empty, as shown below:

Code: Select all

Z:\movie>
Z:\movie>dir 20151128*
 Volume in drive Z is Harddisk
 Volume Serial Number is 9EB4-8E38

 Directory of Z:\movie

28/11/2015  09:24 PM               321 20151128 2125 - ONE - The X-Files_001.ts.meta
28/11/2015  09:24 PM                 0 20151128 2125 - ONE - The X-Files_001.ts
28/11/2015  09:55 PM         2,355,536 20151128 2025 - ONE - The X-Files.ts.sc
28/11/2015  09:24 PM               321 20151128 2125 - ONE - The X-Files.ts.meta
28/11/2015  09:24 PM               249 20151128 2125 - ONE - The X-Files.eit
28/11/2015  09:24 PM                 0 20151128 2125 - SBS HD - Fargo_001.ts
28/11/2015  09:24 PM               238 20151128 2125 - SBS HD - Fargo.eit
28/11/2015  09:24 PM               299 20151128 2125 - SBS HD - Fargo_001.ts.meta
28/11/2015  09:55 PM            97,856 20151128 2025 - ONE - The X-Files.ts.ap
28/11/2015  09:24 PM               299 20151128 2125 - SBS HD - Fargo.ts.meta
28/11/2015  09:24 PM               238 20151128 2125 - SBS HD - Fargo_001.eit
28/11/2015  09:55 PM                24 20151128 2025 - ONE - The X-Files.ts.cuts
28/11/2015  09:24 PM                 0 20151128 2125 - ONE - The X-Files.ts
28/11/2015  09:55 PM     4,080,588,880 20151128 2025 - ONE - The X-Files.ts
28/11/2015  09:24 PM                 0 20151128 2125 - SBS HD - Fargo.ts
28/11/2015  09:24 PM               249 20151128 2125 - ONE - The X-Files_001.eit
28/11/2015  08:24 PM               249 20151128 2025 - ONE - The X-Files.eit
28/11/2015  10:17 PM               338 20151128 2025 - ONE - The X-Files.ts.meta
              18 File(s)  4,083,045,097 bytes
               0 Dir(s)  3,302,870,769,664 bytes free

Z:\movie>

prl wrote:
Code: Select all
Interesting that X-Files "S1 E2" @ 20:25 recorded successfully, but has two timers.
Did it actually have two timers?

Yes, that is not a copy/paste error in my previous post - there really was two timers. I don't recall creating the two for S1E2, nor seeing those two timers listed (plus the S1E3 timer) prior to Saturday evening.

prl wrote:The Fargo timer seems to be coming from an AutoTimer, but the X-Files recordings seem to be from one-off manual timers. Is that correct?

Yes, correct.
The vast majority of my timer recording issues detailed in this thread are from AutoTimer generatd timers, but not all.were.
They all have 2 entries for "activating state 1" and hence double empty output - sometimes the 'duplicate' files are "_001" suffixed, but sometimes they're not (i.e. same file, refer this example issue: Camp Lakebottom 23.11.2015 16:42 - 23.11.2015 17:14 in post viewtopic.php?f=47&t=9791&view=unread#p131289).

So far, there are 9 failed timer recordings since being on the November (beta) firmware - there weren't any whilst on the Aug firmware. Perhaps that was just luck.

Cheers
Geoff

prl · Post by **prl** » Sun Nov 29, 2015 17:32

I had a look at the code when I looked at your post earlier, and I can't work out how you get those log sequences at all!

IanSav · Post by **IanSav** » Sun Nov 29, 2015 18:05

Hi Geoff,

I was looking to see if you had any bouquets that ended in ".del". Those files appeared to cause my Beyonwiz no end of grief. I deleted all the bouquet files and performed a full rescan and I can't reproduce the problems I was previously experiencing. If you had any of those files I was going to suggest a delete and rescan for you as well.

Regards,
Ian.

Grumpy_Geoff · Post by **Grumpy_Geoff** » Mon Nov 30, 2015 16:56

Thanks gents.

It appears the tuner gets allocated. What then prevents the progression from state 1 to state 2 (apart from 20 seconds of time)?
Two entries for "activating state 1" / "prepare ok, waiting for begin"
No entries for "activating state 2" / "start recording", as the recordings never get to start

Shall I enable some logging? If so, how do I go about it - I couldn't find anything in MENU > Setup.

Grumpy_Geoff · Post by **Grumpy_Geoff** » Sun Dec 06, 2015 17:08

Sigh, sigh, sigh - another failed timer recording.

I stopped the (ineffective) recording timer at 12:31 wall clock time when I realised the T4 had failed once again.
I then started an instant recording of the same program - luckily the main race was about 10 mins away from starting; whew!

Now later, whilst preparing this whinge, when looking in /media/hdd/movie, I can see an "*_002" version of the 'original' timer is now recording and its duration is 22m:47s less than my instant recording of the same program. It appears to have started by the AutoTimer plugin at 12:55 as a result of a schedule change.

The timer produced -
20151206 0855 - TEN DIGITAL - LIVE_ V8 Supercars_ Coates Hire Sydney 500.ts (empty)
20151206 0855 - TEN DIGITAL - LIVE_ V8 Supercars_ Coates Hire Sydney 500_001.ts (empty)
20151206 0855 - TEN DIGITAL - LIVE_ V8 Supercars_ Coates Hire Sydney 500_002.ts (recording)

My instant recording is being written to -
20151206 1232 - TEN DIGITAL - LIVE_ V8 Supercars_ Coates Hire Sydney 500.ts

Log snippet attached, from time window 8:52:34 AM to 9:00:17 AM if anyone can make sense of the log entries.
I'm wondering if this timer failure is result of a race/lock condition between the AutoTimer plugin and the timer file (or something similar) as the (EPG?) entry -
{573}[EPGC] schedule finished(1449363300)
appears at 8:55:00 AM, which is 1 second before the timer is due to fire (at 1449363301) and this is amongst the list of AutoTimer entries being processed (thread 559?).

Timer log shown below, as usual for these type of failures, 2 initial lots of "activating state 1" / "prepare ok, waiting for begin" but sadly nothing further.

Code: Select all

<timer begin="1449363301" end="1449386758" serviceref="1:0:1:685:607:1014:EEEE0000:0:0:0:" repeated="0" rename_repeat="1" name="LIVE: V8 Supercars: Coates Hire Sydney 500" description="Join Matt White, Mark Larkham and Rick Kelly for all the action as the V8 Supercars head to Sydney Olympic Park for the Championship&apos;s high octane grand finale, the Coates Hire Sydney 500." afterevent="auto" eit="17465" tags="" disabled="0" justplay="0" always_zap="0" descramble="1" record_ecm="0" isAutoTimer="1">
<log code="500" time="1448785429">[AutoTimer] Try to add new timer based on AutoTimer V8 Supercars.</log>
<log code="15" time="1449300285">record time changed, start prepare is now: Sun Dec  6 08:54:41 2015</log>
<log code="5" time="1449363281">activating state 1</log>
<log code="5" time="1449363281">activating state 1</log>
<log code="0" time="1449363281">Found enough free space to record</log>
<log code="0" time="1449363281">Filename calculated as: &apos;/media/hdd/movie/20151206 0855 - TEN DIGITAL - LIVE_ V8 Supercars_ Coates Hire Sydney 500&apos;</log>
<log code="6" time="1449363281">prepare ok, waiting for begin</log>
<log code="0" time="1449363281">Found enough free space to record</log>
<log code="0" time="1449363281">Filename calculated as: &apos;/media/hdd/movie/20151206 0855 - TEN DIGITAL - LIVE_ V8 Supercars_ Coates Hire Sydney 500_001&apos;</log>
<log code="6" time="1449363281">prepare ok, waiting for begin</log>
<log code="15" time="1449376300">record time changed, start prepare is now: Sun Dec  6 08:54:40 2015</log>
<log code="5" time="1449376304">activating state 3</log>
<log code="12" time="1449376304">stop recording</log>
<log code="15" time="1449377712">record time changed, start prepare is now: Sun Dec  6 08:54:41 2015</log>
<log code="5" time="1449377712">activating state 1</log>
<log code="0" time="1449377712">Found enough free space to record</log>
<log code="0" time="1449377712">Filename calculated as: &apos;/media/hdd/movie/20151206 0855 - TEN DIGITAL - LIVE_ V8 Supercars_ Coates Hire Sydney 500_002&apos;</log>
<log code="6" time="1449377712">prepare ok, waiting for begin</log>
<log code="5" time="1449377712">activating state 2</log>
<log code="11" time="1449377712">start recording</log>
</timer>

Times (AWST):
1449363281 = 8:54:41 AM
1449363301 = 8:55:01 AM
1449376300 = 12:31:40 PM
1449376304 = 12:31:44 PM
1449377712 = 12:55:12 PM

Cheers
Geoff

warkus · Post by **warkus** » Mon Dec 07, 2015 19:18

Grumpy, you're not alone...

I have just had this happen, last night...

I set a new auto timer up on Saturday for ABC2, Octonauts, as the new series 4 started yesterday and my kids are mad Octonauts fans.

I haven't had too close s look at the circumstances yet, so I will have to do that and report back, but...

It seemed to work fine, the auto timer saved and it rescanned the EPG as it does. Said it added a few new timers in, not unusual as I think Octonauts is on several times a day on ABC2.

Then late Sunday when I looked in the directory I set to save these in aptly named Octonauts, it had 6 actual recordings, and then had octonauts_002 through to octonauts_034 and all zero bites in size...

I just thought this was one of those things, a glitch or something, so I didn't look closely at the file extension etc but I will make sure I investigate more thoroughly next time...

Interestingly enough, isn't camp Lakebottom on ABC3? Perhaps it's an issue with the ABC channels?

I have to say I've never seen it before now, not once.

Mark

Grumpy_Geoff · Post by **Grumpy_Geoff** » Tue Dec 08, 2015 18:18

Hi Mark,

warkus wrote:Grumpy, you're not alone...

X-Files - 'we are not alone'.

warkus wrote:I have just had this happen, last night...
I set a new auto timer up on Saturday for ABC2, Octonauts, as the new series 4 started yesterday and my kids are mad Octonauts fans.
I haven't had too close s look at the circumstances yet, so I will have to do that and report back, but...

If you still have your timer for that failed recording instance, press 'i Info' on it to show the timer log (or you can view all of the timers in the file \\BEYONWIZT4\Root\etc\enigma2\timers.xml). Does the timer show -

- 2 entries timed the same for "activating state 1" and "prepare ok, waiting for begin"
- no entries for "activating state 2" / "start recording" (so it never started to record)
- an entry for "activating state 3" / "stop recording"?

warkus wrote:Then late Sunday when I looked in the directory I set to save these in aptly named Octonauts, it had 6 actual recordings, and then had octonauts_002 through to octonauts_034 and all zero bites in size...
I just thought this was one of those things, a glitch or something, so I didn't look closely at the file extension etc but I will make sure I investigate more thoroughly next time...

For that many files (33?), I think that's possibly a different issue than I've experienced - the timer log will confirm that though (maybe I am alone

).
I think Octonauts is only shown once daily Mon-Sat so there shouldn't have been 6 actual recordings (unless you got the AutoTimer wrong, e.g. not restricted it to your Favourites bouquet).

Did you notice if the timer happened to occupy (lock) the relevant tuner past the end-time of the timer (that has been my observation on the times I've been present when it has occurred?

warkus wrote:Interestingly enough, isn't camp Lakebottom on ABC3? Perhaps it's an issue with the ABC channels?

This isn't a broadcaster issue, as I've had it occur on different networks.

Cheers
Geoff

MrQuade · Post by **MrQuade** » Tue Dec 08, 2015 18:23

Grumpy_Geoff wrote: Did you notice if the timer happened to occupy (lock) the relevant tuner past the end-time of the timer (that has been my observation on the times I've been present when it has occurred?

Might I make a suggestion that you disable EPGRefresh for a week or so and see if the issue keeps occurring?

That plugin used to be a bit notorious for locking tuners to a channel. It was associated with enabling the autotimers option within EPGRefresh, though I think you already have that one disabled?

Either way, I would suggest to take it out of the equation if you are seeing tuner lockouts.

prl · Post by **prl** » Tue Dec 08, 2015 18:26

Has everyone who's seeing this problem set MENU>Channels>Autotimer, MENU>Setup>Guess existing timers based on begin/end to off?

If Guess is on, AutoTimers tend to go a bit crazy sometimes.

simoncasey · Post by **simoncasey** » Tue Dec 08, 2015 18:28

Grumpy_Geoff wrote:
warkus wrote:Then late Sunday when I looked in the directory I set to save these in aptly named Octonauts, it had 6 actual recordings, and then had octonauts_002 through to octonauts_034 and all zero bites in size...
I just thought this was one of those things, a glitch or something, so I didn't look closely at the file extension etc but I will make sure I investigate more thoroughly next time...
For that many files (33?), I think that's possibly a different issue than I've experienced - the timer log will confirm that though (maybe I am alone ).
I think Octonauts is only shown once daily Mon-Sat so there shouldn't have been 6 actual recordings (unless you got the AutoTimer wrong, e.g. not restricted it to your Favourites bouquet).

There was 4 episodes of Octonauts shown back to back on Sunday night.

Which then suggests is this related to short shows where you have a large padding and it is not clear when the timer kicks off which show is the right one.
I recall that in some of Geoff's examples, it was for kids shows where a few were recorded in sequence.
And while it wasn't limited to ABC, they do show a lot of short kids shows on ABC2 and 3.
There's a setting in autotimers that can make that issue worse.
(And prl just posted that setting while I was posting!)

prl · Post by **prl** » Tue Dec 08, 2015 18:36

simoncasey wrote:...
There was 4 episodes of Octonauts shown back to back on Sunday night.

Which then suggests is this related to short shows where you have a large padding and it is not clear when the timer kicks off which show is the right one.
...
There's a setting in autotimers that can make that issue worse.
(And prl just posted that setting while I was posting!)

That's exactly why I asked

Grumpy_Geoff · Post by **Grumpy_Geoff** » Tue Dec 08, 2015 19:30

MrQuade wrote:Might I make a suggestion that you disable EPGRefresh for a week or so and see if the issue keeps occurring?
That plugin used to be a bit notorious for locking tuners to a channel. It was associated with enabling the autotimers option within EPGRefresh, though I think you already have that one disabled?

Thanks for the suggestion. I gave up on an automated EPGRefresh 2-3 weeks ago, in an attempt to diagnose/avoid this timer issue, and ran it manually when no timers were firing, I never had the 'after refresh run AutoTimers' option enabled.
I then gave up on it altogether and created 6 back-to-back record-to-trash timers - worked like a bought one!

Grumpy_Geoff · Post by **Grumpy_Geoff** » Tue Dec 08, 2015 19:33

prl wrote:Has everyone who's seeing this problem set MENU>Channels>Autotimer, MENU>Setup>Guess existing timers based on begin/end to off?

If Guess is on, AutoTimers tend to go a bit crazy sometimes.

Hi Peter,

Thanks for the suggestion, however I nuked that option back in September when I found timer creation issues

Grumpy_Geoff · Post by **Grumpy_Geoff** » Tue Dec 08, 2015 19:51

Hi Mark,

How many AutoTimer entries do you have?
How long does it take to process them - using OpenWebif / AutoTimer / Simulate; how long does it take to show the "AutoTimer Preview" screen (you have to wait for the 'spinner' shown at the very bottom of the window to update the screen if it had previously been shown in this session).

I used to have 39 AutoTimer entries -
[Task] job Components.Task.Job name=AutoTimer #tasks=39 completed with [] in None
Now I have 5 - as I've IceTV'ed the rest for this T4 (with these remaining 5 as a work in progress). These 5 AutoTimers take approx 3 seconds to process - I'm wondering whether the 39 AutoTimer entries I previously had was taking more than 20 seconds to process and somehow locking the "timers.xml" file between the 'prepare' and 20 seconds later when the recording should have started. That is why the issue is not consistent.

Yep, quite possibly grasping at straws.

Cheers,
Geoff

warkus · Post by **warkus** » Tue Dec 08, 2015 22:35

Apologies everyone, I didn't check back here today so I didn't realise there was a need to respond, oops...

Only just got in, been at daughters netball finals, eill check and post back info soon, or tomorrow morning if I fall asleep on lounge, very realistic possibility...

Only thing I will say is yes there were exactly 4 episodes taped correctly, I thought 6 but I was working off the top of my head, but the kids tell me there were 4 and they all worked fine. After that it was like 002 onwards and a lot of them and all zero length.

I'll come back with more soon.

Ps, it's worked flawlessly since then and recorded exactly the correct shows since including the one episode of Octonauts that shows daily since Sunday. If they do another back to back this Sunday it will be an interesting test to see if it does it again.

Mark

Grumpy_Geoff · Post by **Grumpy_Geoff** » Wed Dec 09, 2015 19:19

Grumpy_Geoff wrote:...
I used to have 39 AutoTimer entries -
[Task] job Components.Task.Job name=AutoTimer #tasks=39 completed with [] in None
Now I have 5 - as I've IceTV'ed the rest for this T4 (with these remaining 5 as a work in progress). These 5 AutoTimers take approx 3 seconds to process - I'm wondering whether the 39 AutoTimer entries I previously had was taking more than 20 seconds to process and somehow locking the "timers.xml" file between the 'prepare' and 20 seconds later when the recording should have started. That is why the issue is not consistent.

Okay, I've remembered that the OpenWebif AutoTimer 'simulate' timings will most likely be faster than the normal AutoTimer processing as simulate doesn't check timers/folders for uniqueness if 'Require description to be unique' is set to "Any service/recording",
I had that set for many of my son's AutoTimers. This morning when I removed just 1 of the remaining 4 AutoTimers, and pressed GREEN/Save, the resultant AutoTimer popup took 9 seconds to display on the T4.
No doubt the overall duration is dependent on how many recording files/folders/timers there are to check for each matching EPG entry.
If the extended duration AutoTimer processing is the cause of my timer failures, then I should know within a week going by past experience as I've only 1 AutoTimer left now

warkus · Post by **warkus** » Thu Dec 10, 2015 00:15

Sorry grumpy...

Ok, time to answer the questions...

I have 31 auto timers at the moment the most recent added was Octonauts.

It took 18 seconds from start to showing the popup message in the test I just did.

Mark

warkus · Post by **warkus** » Thu Dec 10, 2015 00:46

Grumpy_Geoff wrote:
For that many files (33?), I think that's possibly a different issue than I've experienced - the timer log will confirm that though (maybe I am alone ).
I think Octonauts is only shown once daily Mon-Sat so there shouldn't have been 6 actual recordings (unless you got the AutoTimer wrong, e.g. not restricted it to your Favourites bouquet).

Did you notice if the timer happened to occupy (lock) the relevant tuner past the end-time of the timer (that has been my observation on the times I've been present when it has occurred?

Sorry no I didn't notice if it locked the tuner, I actually didn't notice the zero bite files till much later Sunday night.

I can confirm that Octonauts was on 4 times back to back Sunday and it recorded each of them correctly.

Grumpy_Geoff · Post by **Grumpy_Geoff** » Thu Dec 10, 2015 09:37

Hi Mark,

Thanks for the replies..

Do you have many AutoTimers defined with 'Require description to be unique' set to "Any service/recording"?

Was your timing taken from OpenWebif 'simulate' or from GREEN/Save on the AutoTimer listing screen?

Have you viewed the timer log for the failed Octonauts timer - does it show the same symptoms as mine do? With the timer creating 33 sequenced .ts files, numbered 002 to 034, it doesn't sound like it is - particularly since the 4 episodes recorded correctly on Sunday.

warkus · Post by **warkus** » Thu Dec 10, 2015 10:39

Only 3 of my timers have require description to be unique set...

The time was taken from the unit itself.

Press save from the auto timers screen - automatically triggers a rescan, so press save and start timer, press exit twice to return to live TV and wait. Then the popup is eventually displayed.

Time was 18 seconds.

Interestingly enough I may have accidentally found a trigger, but I need to do further investigation on it...

I was playing around with the auto timers last night after the test above...this as in an effort to remember exactly what I did that night I set the Octonauts timer up.

If you press save on the auto timer screen, and go back in and press save again, inside the 18 seconds in my case before it finishes the first scan, then exit to the live TV You get VERY weird results from multiple auto timer completed pop ups...

I remember doing this the night I set the Octonauts auto timer up. I set it, pressed save, remembered I didn't put the channel number on the auto timer description (which is just a little anal thing I do) so I went straight back in and did that but didn't modify anything else that would affect the timer itself, and pressed save again.

I also remember getting 2 auto timer Windows popup to say completed but didn't think anything of it...

So based on some experimenting I did last night with trying to repeat that, it does appear as though the completed pop ups contradict each other with differing results. So I'm going to monitor my recordings now over the next few days and see if I have inadvertently caused similar things to happen to timers coming up today...

I'll keep you posted, I know it's a long shot but you never know...

As for viewing the log, I have my old timers retained set to 1 day so they were no longer in the timer list for me to check but if you're saying there is a log file I can check let me know where it is and I'll open it and attach...

Mark

Grumpy_Geoff · Post by **Grumpy_Geoff** » Thu Dec 10, 2015 11:21

Hi Mark,

warkus wrote:Only 3 of my timers have require description to be unique set...
The time was taken from the unit itself.
Time was 18 seconds.

Even though you only have 3 'require unique' AutoTimers and I had many more, your timing of 18 seconds for AutoTimer processing could still make the elapsed time an issue if it occurred after the first 3 seconds of a timer's prepare stage - if my theory holds....

warkus wrote: As for viewing the log, I have my old timers retained set to 1 day so they were no longer in the timer list for me to check but if you're saying there is a log file I can check let me know where it is and I'll open it and attach...

Nup, not to my knowledge. The log is within the timer itself (see one of my earlier entries) and the timers are contained in file timers.xml.
I'm thinking your issue is different to mine - from what I can tell, your programs actually got recorded, but you had 33 *additional* empty recordings for one of the programs, sequenced from _002 to _034.
You didn't have a null recording, right?

warkus · Post by **warkus** » Thu Dec 10, 2015 16:56

No i don't appear to have had a null recording as far as i can tell, because there were 4 episodes back to back for the octonauts on Sunday and we had 4 episodes taped...

Bummer about the logs, i will keep a very close eye on it and if it happens again, i will go into the log straight away.

brianh · Post by **brianh** » Fri Dec 11, 2015 16:03

Just had a spate of these on the T3, zero bytes & zero size.

First thing I checked was to manually start three recordings and verified the tuners were all OK - they were.
Timers that failed:
Judge Judy was one set by ICE, Dr Phil by timers from the EPG - both zero bytes for the past two days.
Judge Judy was recording today while I was home so I tried to play the recording file from the Media play list - wouldn't play, just comes up with the menu to "stop playing the file" with all the choices of whether to return to list, delete file, etc.

I tried to navigate to that recording channel through the EPG but the picture just froze - I had to use the 'back" button to return to the last playable channel. The info bar and all other indications are that the file was recording OK - except it wasn't.

I looked at the log, all the timers that are zero show the sequence of "activating state...." 1, 2 or 3 at the appropriate times - except that today's judge judy showed that it started at the time for Dr Phil, then re-commenced again at the correct time for judge judy.

Other files just show the correct times in the logs.

I also had a weird issue with "Live at the Apollo - there were a stack (at least four) files created with identical start times and identical content, no problem with them - then there were three recordings all at another time that seemed to have identical timer data but different content and one was zero bytes.
One of the logs indicated that there was a timer that "tried to mess with" another autotimer.... I think that was the wording in the file....

I checked the settings and found the Auto timers"Guess ending time" was on (or whatever it was, can't see previous posts in edit mode) - so I've now set it to off. I also found a setting along the lines of "apply to all one time timers" (which would be anything from ICE) and set that to "apply to timers with same EIT" (or whatever the wording is)

I'll need to wait until tomorrow now to check the results.... if anyone wants some logs, tell me where & how to dig and I'll do my best to get them...

Grumpy_Geoff · Post by **Grumpy_Geoff** » Fri Dec 11, 2015 16:48

brianh wrote:...
Timers that failed:
Judge Judy was one set by ICE, Dr Phil by timers from the EPG - both zero bytes for the past two days.
Judge Judy was recording today while I was home so I tried to play the recording file from the Media play list - wouldn't play, just comes up with the menu to "stop playing the file" with all the choices of whether to return to list, delete file, etc.

I see that both Judge Judy and Dr Phil are on the TEN Network - is TEN currently okay to view?

Cheers.
Geoff

brianh · Post by **brianh** » Fri Dec 11, 2015 20:56

Yes, that channel was locked out during his recording but was able to be watched as soon as the recording finished

prl · Post by **prl** » Fri Dec 11, 2015 21:37

Could there be a dead tuner in play?

brianh · Post by **brianh** » Sat Dec 12, 2015 08:31

brianh wrote:Just had a spate of these on the T3, zero bytes & zero size.

First thing I checked was to manually start three recordings and verified the tuners were all OK - they were.......

Not as far as my testing could tell - although I was expecting a fourth channel to be viewable, until I remembered I was on the T3....

Gully · Post by **Gully** » Sat Dec 12, 2015 08:49

brianh wrote:Not as far as my testing could tell - although I was expecting a fourth channel to be viewable, until I remembered I was on the T3....

Not totally ridiculous if you chose one to view that was from the subset of the 3 providers you were recording.

brianh · Post by **brianh** » Sat Dec 12, 2015 09:26

Gully wrote:
brianh wrote:Not as far as my testing could tell - although I was expecting a fourth channel to be viewable, until I remembered I was on the T3....
Not totally ridiculous if you chose one to view that was from the subset of the 3 providers you were recording.

Unfortunately not that intelligent an instinct - I was deliberately stepping through the different providers... and it took me a good few seconds to work out why I couldn't get that extra channel.....

simoncasey · Post by **simoncasey** » Sat Dec 12, 2015 09:39

Being that from the reports it often seems to happen when multiple recordings are on the same channel, it might be worth trying 2 manual recordings on each channel ie a total of 6.

tonymy01 · Post by **tonymy01** » Sat Dec 12, 2015 09:42

Ok, how about instead of dead tuner, just a poorer reception one that has some problems tuning some/one but not other broadcasters? I can't remember if any with this issue tried a 4 way splitter instead of daisy chain? Might really cut reception though with 6+dB drop of the splitter.

simoncasey · Post by **simoncasey** » Sat Dec 12, 2015 09:50

brianh wrote:Yes, that channel was locked out during his recording but was able to be watched as soon as the recording finished

I'm requoting an earlier post here which I think means that Brian couldn't watch live TV on the channel while the problem was occurring. This does seem to imply a tuner or broadcast problem rather than a problem with the timer.

brianh · Post by **brianh** » Sat Dec 12, 2015 22:20

simoncasey wrote:
brianh wrote:Yes, that channel was locked out during his recording but was able to be watched as soon as the recording finished
I'm requoting an earlier post here which I think means that Brian couldn't watch live TV on the channel while the problem was occurring. This does seem to imply a tuner or broadcast problem rather than a problem with the timer.

Simon is correct - unable to watch live TV on TEN while recording that channel, with the bug in effect.

Checked the tuner signal, they're all good..... I don't have any issues with TEN here, there was a definite "lock-out" while recording - no way I could see that channel, e.g I was on 7.

As soon as I tried to navigate to TEN while the recording was happening, the picture just froze on whatever was being viewed on 7 - it wouldn't even go to TEN. I had to use the back button to start watching on 7 again.

As soon as the recording was done, I could navigate to TEN with no problem....

simoncasey · Post by **simoncasey** » Sat Dec 12, 2015 22:27

Was it just ten or were one and eleven blocked too?

About the Forum

Join us