Apparently successful recordings fail to playback

briang

Member
Forgive me if this has been asked before. I've been suffering from a spate of recordings stopping during playback, about 10 minutes in or so. The place where they drop out of playback is consistent.

They must appear to be ok, as they are decrypted. I can also shrink them, though the resultant files also drop
out at the same point in playback.

I've just run fix-disk (more in hope than expectation...).

If I can't stop this, does anyone have a suggestion for fixing the files?
 
What is the actual physical size of the files? What was the size of the files before decryption (they might still be in the undelete buffer)?
 
I didn't have undelete installed, so have nothing to compare with currently I've just installed undelete now. Here's an example of a failed recording with the previous successful one.

-rw-r--r-- 1 root root 3259776 Oct 23 22:31 New_ Detectorists_20141023_2158.nts
-rw-rw-rw- 1 root root 1119547392 Oct 23 23:12 New_ Detectorists_20141023_2158.ts
-rw-r--r-- 1 root root 43680 Oct 23 23:27 New_ Detectorists_20141023_2158.thm
-rw-r--r-- 1 root root 13888 Oct 26 19:31 New_ Detectorists_20141023_2158.hmt
-rw-r--r-- 1 root root 3431488 Oct 30 22:32 New_ Detectorists_20141030_2158.nts
-rw-r--r-- 1 root root 43680 Oct 30 22:32 New_ Detectorists_20141030_2158.thm
-rw-rw-rw- 1 root root 488112512 Oct 31 17:40 New_ Detectorists_20141030_2158.ts
drwxr-xr-x 2 root root 4096 Oct 31 17:40 .
-rw-r--r-- 1 root root 276 Oct 31 19:01 .series
drwxr-xr-x 22 root root 24576 Nov 1 23:45 ..
-rw-r--r-- 1 root root 13888 Nov 2 08:21 New_ Detectorists_20141030_2158.hmt
humax# bc
-/bin/sh: bc: not found
humax#
humax# # 1119547392 = 1067 MB # 488112512 = 465 M

The summary suggests a full 30 minute recording, in view of the file sizes, obviously not so.


Perhaps we should put this on ice till I have a before/after decryption example?
 
Given the file sizes I take it these are HiDef recordings, and the first in the list plays OK but the second terminates half way through? We have noted some weird problems recording from the likes of BBC FOUR HD, but I'm not sure this is one of them.
 
If you have redring installed you could check the start and start time of the recordings :-
Code:
[RR] Thu Oct 30 22:03:21 2014: Recording start 32:'/mnt/hd2/My Video/Detectorists/New_ Detectorists_20141030_2203.nts'
[RR] Thu Oct 30 22:03:21 2014:    Recording 1
[RR] Thu Oct 30 22:32:47 2014: Recording end 32.

If you are not running Redring you can get some info. from the Remote Schedule server

Capture.JPG
 
Last edited:
This happened to be BBC4 HD. MOTD on BBC1 HD failed yesterday, however I deleted it before starting this thread.

I have redring installed - V 2.16 - however the last entry is from 2012 - V2.10


+++++++++++++++++++++++++++++++++++++++++++++++++++++++
[RR] Wed Nov 14 22:27:53 2012: Options 0x3
[RR] Wed Nov 14 22:27:53 2012: Timezone: GMT (0)
[RR] Wed Nov 14 22:27:53 2012: Level: ha_blue = 0x40
[RR] Wed Nov 14 22:27:53 2012: Level: ha_rec = 0xfc
[RR] Wed Nov 14 22:27:53 2012: -------------------------------------
+++++++++++++++++++++++++++++++++++++++++++++++++++++++
[RR] Sat Dec 29 23:01:19 2012: Persistent log starting, v2.10
+++++++++++++++++++++++++++++++++++++++++++++++++++++++
[RR] Sat Dec 29 23:01:19 2012: Options 0x3
[RR] Sat Dec 29 23:01:19 2012: Timezone: GMT (0)
[RR] Sat Dec 29 23:01:19 2012: Level: ha_blue = 0x40
[RR] Sat Dec 29 23:01:19 2012: Level: ha_rec = 0xfc
[RR] Sat Dec 29 23:01:19 2012: -------------------------------------

I did a remote schedule 3 years or so ago, just to prove feasibility. I haven't felt the need to revisit. Should I?
 
If you have already set up an account, it would be an easy way to see a recording log by going to :-
https://rs.hpkg.tv/ and scrolling down to 'Recent Activity'
BTW
You may be able get your Redring logging properly by running Web-If >> Diagnostics >> Run Diagnostic >> fix-flash-packages >> Run
 
Recent activity doesn't indicate failure. We know differently



31/10/2014 04:17:24 System booted.
30/10/2014 22:31:09 Recorded: New_ Detectorists/New: Detectorists (33 minutes - BBC FOUR HD)
30/10/2014 22:01:08 Recorded: Peaky Blinders/Peaky Blinders (63 minutes - BBC TWO HD)
30/10/2014 20:55:33 System booted.
30/10/2014 04:22:41 Updated disk contents.

02/11/2014 04:18:17 System booted.
02/11/2014 01:06:50 Recorded: The Football League Show/The Football League Show (81 minutes - BBC ONE HD)
01/11/2014 23:44:50 Recorded: Match of the Day/Match of the Day (87 minutes - BBC ONE HD)
01/11/2014 20:37:07 Uploaded 0 EPG entries, 317.00 bytes.

I'll report back in a while about redring. I've reinstalled as per your sugggestion. Web-If >> Diagnostics >> Run Diagnostic >> fix-flash-packages >> Run





I
 
Redring.logging not fixed. I scheduled a recording, which has completed.

ls -la /mod/tmp/redring.log
-rw-rw-rw- 1 root root 0 Nov 2 16:37 /mod/tmp/redring.log


Thanks for the help btw. I thought the old Topfield community was good. This place is outstanding.
 
Out of interest, how are you decrypting? If you're using the new web interface built-in method of flagging a folder for auto-decrypt, or the top level folder for recursive auto-decrypt, then I'd be surprised if it's causing the problem as it always checks that the decrypted file has the same size as the original.

Perhaps we should put this on ice till I have a before/after decryption example?
Sounds like a plan : )
 
I've reinstalled as per your sugggestion. Web-If >> Diagnostics >> Run Diagnostic >> fix-flash-packages >> Run
fix-flash-packages isn't really a full reinstall, but you can do this with :- Web-If >> Diagnostics >> Package >> redring >> Force re-install
 
I'm actually unsure how I set up decrypting, I just followed a secret-sauce recipe on here 2-3 years ago. There's nothing obvious to me in packages. I have unencrypt - 0.1.4 & auto-unprotect - 1.0.9 - Utility for automatically unprotecting HD files when they are recorded.

Any pointers, would be helpful.

Redring is still not loggging, despite a full reinstall - Remote scheduler caught my recording of Bananas in Pyjamas, this morning, post reinstall, however nothing logged




Filename: redring_2.16_mipsel.opk
Description: Cause the Humax to display a red LED ring when recording in
standby + other functions. [Attempt to fix stuck-on-blue problem]
Installed-Time: 1415003473


ls -lart /mod/tmp/*.log
-rw-rw-rw- 1 root root 1159720 Apr 5 2013 /mod/tmp/auto.log
-rw-r--r-- 1 root root 92 Jun 15 22:45 /mod/tmp/crash.log
-rw-rw-rw- 1 root root 162861 Nov 2 08:21 /mod/tmp/rs.log
-rw-rw-rw- 1 root root 0 Nov 2 16:37 /mod/tmp/redring.log
-rw-rw-rw- 1 root root 184 Nov 3 02:06 /mod/tmp/empty_dustbin.log
-rw-rw-rw- 1 root root 11649 Nov 3 09:11 /mod/tmp/unencrypt.log

It's apparently not a general logging issue.

I'd dearly like to fix this problem B, especially if it provides diags for problem A - incomplete recordings,
 
Things have moved on: unencrypt is deprecated and is behind the times; the WebIF methods of decryption and auto-decryption have built-in safeguards and are recommended. See Things Every... (click) section 5 and follow the link for decryption.

I don't know whether the unencrypt process is responsible for your incomplete files, but it could be. The alternative is that the recording was incomplete in the first place.
 
I see. You mean this.

"Method 2 (WebIF-mediated auto-decryption):
  1. Ensure content sharing is turned on (Humax settings, see note 3);
  2. For HiDef ensure auto-unprotect is installed (not necessary for StDef recordings);
  3. For any particular folder, use WebIF media browser OPT+ button "auto-decrypt" option to decrypt any present and future recordings in that folder; or
  4. For any particular folder, use WebIF media browser OPT+ button "recursive auto-decrypt" option to decrypt any present and future recordings in that folder and any sub-folders (all levels). To decrypt all of My Video set the recursive auto-decrypt flag on the My Video folder (use the path links at the top of the listing to get to Media, My Video is listed in there)."
It appears I am not following this this in view of my crontab
1,31 1-23 * * * /mod/sbin/unencrypt "/mnt/hd2/My Video" > /mod/tmp/unencrypt.log 2>&1

I'd be entirely happy to adopt this method instead. As you say we don't know whether unencrypt process is responsible for my incomplete files, but it could be.

Unless you have a burning need to prove it (I don't), I'll ditch the cron entry and rejoin the herd. If I still have a problem, then it was irrelevant, but I'm not using a deprecated method.
 
Uninstall the unencrypt package - that should remove the cron entry too.
 
So it has cron entry gone. Pretty unpadlock icon against My Videos. Hopefully this will eliminate the partial recordings. I shall monitor.

An observation. If I had a product exhibiting this behaviour, with a closed firmware. I'd be looking to having to replace it, out of warranty. Because of the nature of this site, I'm pretty optimistic. I bloody love it. Thanks again.

I'll be happy to entertain suggestions for redring logging in the interim :) My life isn't complete without something to fix
 
It wouldn't exhibit this particular behaviour (presuming it is a decryption failure giving you this grief), but there have been plenty of other hiccups that required (and still require) and up-issue of the Humax firmware if we didn't know how to work around them!
 
Back
Top