[boot-settings] Apply settings during boot

Border said:
After yet another wizard reinstall all channels / lcns were reinstalled and there are Adult channels available on the HDR that are accessible, unlocked, and innapropriate for some viewers. eg Lcn 673 adult smiletv3 which the HDR Fox displays without problems .

Wizard resets and OTA rescans are bothersome as these channels are reinstalled.
Click to expand...
Easily fixed with tunefix.

Did anyone ever try my suggestion in post #75?
 
This package doesn't appear to work as intended on my box, I installed as Content Sharing keeps turning itself off!

However with this when Content Sharing is off it just seems to persuade the webif its back on without actually turning it back on, so detectAds tries to run on a file but then reports length error (full size of file) as it can't access it.

I have to switch Content Sharing on with the box menus then reboot to restore normal operation, which is more hassle than before!
 
Something is seriously odd on your box,

While Content Sharing turning itself is not unknown it is not normally a regular event, Once or twice a year is more normal
When I turn it on/off with the box menus I don't need to reboot nor do I experience any problems from the boot settings

Clutching at straws a bit
  • have you tried rebuilding the dlna index from diagnostics menu?
  • have you ever altered the decryption key?
  • have you kept the original, encrypted, recording for further debugging?
  • can you decrypt the file using the webif interface or autodecrypt when it is in the 'appears to be on but isn't' state
  • anything in the logs? (chaseget, detectads, auto.log)
 
MymsMan said:
When I turn it on/off with the box menus I don't need to reboot nor do I experience any problems from the boot settings
Click to expand...

I only have to reboot with the boot-setting faking the Content Sharing setting. It turns off 2 to 3 times a week!

MymsMan said:
have you tried rebuilding the dlna index from diagnostics menu?
Click to expand...
No, just done that though, see if it has an affect.

MymsMan said:
have you ever altered the decryption key?
Click to expand...
No

MymsMan said:
have you kept the original, encrypted, recording for further debugging?
can you decrypt the file using the webif interface or autodecrypt when it is in the 'appears to be on but isn't' state
Click to expand...
Their in the bin, I can check next time it happens.

MymsMan said:
anything in the logs? (chaseget, detectads, auto.log)
Click to expand...
This is the auto log, detectads.log is and always has been empty, regardless of log settings.

Code: 
3638    15/01/2019 10:28:10 -     DEFER - 0 ad breaks detected, Incomplete data retrieval 2230194176 bytes missing (02:12:31) - 1547548990
3637    15/01/2019 10:28:10 - detectads:=============================================================
3636    15/01/2019 10:28:10 - detectads:done...processed /mnt/hd2/My Video/Films/Stonehearst Asylum_20190115_0232.ts in 607.043s 00:10:07 - 0 ad breaks detected
3635    15/01/2019 10:28:10 - detectads:/mod/tmp/Stonehearst Asylum_20190115_0232-dec.ts deleted
3634    15/01/2019 10:28:10 - detectads:Qid 1989 target start 10:43:10
3633    15/01/2019 10:28:10 - detectads:Queing /mnt/hd2/My Video/Films/Stonehearst Asylum_20190115_0232.ts for retry of detectads due to significant file length error
3632    15/01/2019 10:28:10 - detectads:/mnt/hd2/My Video/Films/Stonehearst Asylum_20190115_0232.ts Incomplete data retrieval 2230194176 bytes missing (02:12:31)
3631    15/01/2019 10:28:10 - detectads:
3630    15/01/2019 10:28:10 - detectads:Final bookmarks:
3629    15/01/2019 10:28:10 NS(3582)- New Program Length = 0s
3628    15/01/2019 10:28:10 NS(3582)- Wrote 0 entries to /mnt/hd2/My Video/Films/Stonehearst Asylum_20190115_0232-crop. Stripped 0 packets (0k) of EPG data
3627    15/01/2019 10:28:10 NS(3582)-
3626    15/01/2019 10:28:10 - detectads:After process loop
3625    15/01/2019 10:28:10 - detectads:EOF detected
3624    15/01/2019 10:28:10 - detectads:
3602    15/01/2019 10:18:08 - detectads:info@          frame - frame (mmm:ss-mmm:ss) frame (mm:ss.s)  frame (mmm:ss)
3601    15/01/2019 10:18:08 - detectads:info@          Start - End    Start - End      Duration         Interval      Level/Count
3600    15/01/2019 10:18:08 - detectads:debug@< preroll, > postroll, - advert, ? too few silences, # too short, = comm flagged
3599    15/01/2019 10:18:08 - detectads:debug@longer than 1500 frames in total. Cuts will be padded by 0 frames
3598    15/01/2019 10:18:08 - detectads:debug@Clusters are composed of a minimum of 5 silences closer than 2376 frames and must be
3597    15/01/2019 10:18:08 - detectads:debug@Frame rate is 25.00, Detecting silences below 679094 that last for at least 5 frames
3596    15/01/2019 10:18:08 - detectads:debug@Threshold=-70.0, MinQuiet=0.20, MinDetect=5.0, MinLength=60.0, MaxSep=95.0, Pad=0.00
3595    15/01/2019 10:18:08 - detectads:Initial bookmarks:
3594    15/01/2019 10:18:08 - detectads:adDetect pids 3693 3697 3698 3699
3593    15/01/2019 10:18:04 - No expire flags in filesystem, suppressing scan.
3592    15/01/2019 10:18:04 - Active flags: sweeper shrink dedup nodetectads decrypt detectads
3591    15/01/2019 10:18:04 - Scan completed (2.084 seconds)
3590    15/01/2019 10:18:03 NS(3582)- progLen = 0s, 0 bookmarks, HD = 0
3589    15/01/2019 10:18:03 - detectads:crop pids 3619 3620
3588    15/01/2019 10:18:03 - detectads:starting
3587    15/01/2019 10:18:03 - detectads:Target option: 1 Target path: /mnt/hd2/My Video/Films
3586    15/01/2019 10:18:03 - detectads:Content Sharing Enabled
3585    15/01/2019 10:18:03 - detectads:Padding out points by 4 secs and ignoring program end bookmark
3584    15/01/2019 10:18:03 - detectads:orphan file list
3583    15/01/2019 10:18:03 - detectads:==DETECTADS Chase Run: /mnt/hd2/My Video/Films/Stonehearst Asylum_20190115_0232.ts
3582    15/01/2019 10:18:02 - Scanning media for flags...
3581    15/01/2019 10:18:02 - De-queuing 1989 - detectads - /mnt/hd2/My Video/Films/Stonehearst Asylum_20190115_0232.ts
chaseget.log

Code: 
4983    15/01/2019 10:28:10 - CG(3693)- DLNA Server is still NOT running. Giving up
4982    15/01/2019 10:28:10 - CG(3693)- DLNA Server is NOT running.
4981    15/01/2019 10:27:10 - CG(3693)- DLNA Server is NOT running.
4980    15/01/2019 10:26:09 - CG(3693)- DLNA Server is NOT running.
4979    15/01/2019 10:25:09 - CG(3693)- DLNA Server is NOT running.
4978    15/01/2019 10:24:09 - CG(3693)- DLNA Server is NOT running.
4977    15/01/2019 10:23:09 - CG(3693)- DLNA Server is NOT running.
4976    15/01/2019 10:22:09 - CG(3693)- DLNA Server is NOT running.
4975    15/01/2019 10:21:09 - CG(3693)- DLNA Server is NOT running.
4974    15/01/2019 10:20:09 - CG(3693)- DLNA Server is NOT running.
4973    15/01/2019 10:19:09 - CG(3693)- DLNA Server is NOT running.
4972    15/01/2019 10:18:09 - CG(3693)- DLNA Server is NOT running.
4971    15/01/2019 10:18:08 - CG(3693)- ChaseGet /mod/tmp/Stonehearst Asylum_20190115_0232-inp.ts
 
Last edited:
Ah DLNA Server is NOT running. is a totally different kettle of fish from Content Sharing Disabled
You don't have a problem with the Content share becoming disabled, it was active when checked by detectads 1 second earlier. Chaseget would have repeated the disabled message if it was disabled.

Normally the DLNA server runs when then system is active but is stopped when recording in standby mode, chaseget wakes the system from standby if the system is in standby but this should have caused a System power on attempted message in the log.
So why was the DLNA server not running if the system was not in standby?
It appears that it starts up on system start-up but something is causing it to stop, your network must still be active or you wouldn't be able to access the webif.
 
Me too am getting the DLNA server not running.
It started producing the error on 08/01/19. It had not happened since the start of the chaseget log on 14/12/18
Code: 
14/12/2018 19:34:30 - CG(3641)- System power on attempted
14/12/2018 20:10:07 - CG(7353)- System power Off attempted, ChaseGet power On was at 19:34:30 
14/12/2018 20:33:47 - CG(3676)- System power on attempted
14/12/2018 21:10:07 - CG(7538)- System power Off attempted, ChaseGet power On was at 20:33:47 
15/12/2018 16:33:26 - CG(3811)- System power on attempted
15/12/2018 17:50:06 - CG(10927)- System power Off attempted, ChaseGet power On was at 16:33:26 
16/12/2018 14:46:24 - CG(3870)- System power on attempted
16/12/2018 16:10:07 - CG(11168)- System power Off attempted, ChaseGet power On was at 14:46:24 
17/12/2018 21:05:06 - CG(3993)- System power on attempted
17/12/2018 22:10:08 - CG(10306)- System power Off attempted, ChaseGet power On was at 21:05:07 
20/12/2018 20:02:59 - CG(3794)- System power on attempted
20/12/2018 21:10:07 - CG(9904)- System power Off attempted, ChaseGet power On was at 20:02:59 
22/12/2018 16:01:17 - CG(3802)- System power on attempted
22/12/2018 17:10:07 - CG(9913)- System power Off attempted, ChaseGet power On was at 16:01:17 
23/12/2018 18:04:40 - CG(13183)- ChaseGet /mod/tmp/The Chase_ Celebrity Special_20181223_1801-inp.ts
23/12/2018 18:59:28 - CG(13183)- ChaseGet end /mod/tmp/The Chase_ Celebrity Special_20181223_1801-inp.ts Size 2508963840 bytes
25/12/2018 15:13:44 - CG(3808)- ChaseGet /mod/tmp/A Christmas Chase_ Celebrity Special_20181225_1510-inp.ts
25/12/2018 15:13:45 - CG(3808)- System power on attempted
25/12/2018 16:13:39 - CG(3808)- ChaseGet end /mod/tmp/A Christmas Chase_ Celebrity Special_20181225_1510-inp.ts Size 2614362112 bytes
25/12/2018 16:33:07 - CG(10889)- System power Off attempted, ChaseGet power On was at 15:13:45 
25/12/2018 18:36:44 - CG(9132)- ChaseGet /mod/tmp/Apollo 13_20181225_1833-inp.ts
25/12/2018 18:36:44 - CG(9132)- System power on attempted
25/12/2018 19:30:06 - CG(9132)- ChaseGet end /mod/tmp/Apollo 13_20181225_1833-inp.ts Size 1098862592 bytes
25/12/2018 19:34:10 - CG(15858)- ChaseGet /mod/tmp/Apollo 13_20181225_1931-inp.ts
25/12/2018 20:19:44 - CG(20713)- ChaseGet /mod/tmp/Coronation Street_20181225_2016-inp.ts
25/12/2018 21:18:45 - CG(15858)- ChaseGet end /mod/tmp/Apollo 13_20181225_1931-inp.ts Size 2074402816 bytes
25/12/2018 21:19:38 - CG(20713)- ChaseGet end /mod/tmp/Coronation Street_20181225_2016-inp.ts Size 2516353024 bytes
25/12/2018 21:22:28 - CG(27780)- ChaseGet /mod/tmp/New_ Torvill and Dean_20181225_2119-inp.ts
25/12/2018 23:17:27 - CG(27780)- ChaseGet end /mod/tmp/New_ Torvill and Dean_20181225_2119-inp.ts Size 3903647744 bytes
25/12/2018 23:33:07 - CG(7664)- System power Off attempted, ChaseGet power On was at 18:36:44 
26/12/2018 17:37:04 - CG(3905)- ChaseGet /mod/tmp/The Chase_ Celebrity Special_20181226_1733-inp.ts
26/12/2018 17:37:04 - CG(3905)- System power on attempted
26/12/2018 18:36:16 - CG(3905)- ChaseGet end /mod/tmp/The Chase_ Celebrity Special_20181226_1733-inp.ts Size 2788704256 bytes
26/12/2018 19:30:38 - CG(14163)- ChaseGet /mod/tmp/Coronation Street_20181226_1927-inp.ts
26/12/2018 20:00:11 - CG(14163)- ChaseGet end /mod/tmp/Coronation Street_20181226_1927-inp.ts Size 1260118016 bytes
27/12/2018 17:01:58 - CG(3870)- ChaseGet /mod/tmp/The Chase_ Celebrity Special_20181227_1658-inp.ts
27/12/2018 17:01:58 - CG(3870)- System power on attempted
27/12/2018 18:00:34 - CG(3870)- ChaseGet end /mod/tmp/The Chase_ Celebrity Special_20181227_1658-inp.ts Size 2544496640 bytes
27/12/2018 18:13:07 - CG(10290)- System power Off attempted, ChaseGet power On was at 17:01:58 
28/12/2018 17:01:41 - CG(3898)- ChaseGet /mod/tmp/The Chase_ Celebrity Special_20181228_1658-inp.ts
28/12/2018 17:01:41 - CG(3898)- System power on attempted
28/12/2018 18:00:39 - CG(3898)- ChaseGet end /mod/tmp/The Chase_ Celebrity Special_20181228_1658-inp.ts Size 2554671104 bytes
28/12/2018 18:13:07 - CG(10336)- System power Off attempted, ChaseGet power On was at 17:01:41 
29/12/2018 15:34:00 - CG(3940)- ChaseGet /mod/tmp/The Chase_ Celebrity Special_20181229_1530-inp.ts
29/12/2018 15:34:00 - CG(3940)- System power on attempted
29/12/2018 16:32:42 - CG(3940)- ChaseGet end /mod/tmp/The Chase_ Celebrity Special_20181229_1530-inp.ts Size 2608865280 bytes
29/12/2018 16:53:07 - CG(11330)- System power Off attempted, ChaseGet power On was at 15:34:00 
29/12/2018 18:20:00 - CG(3628)- ChaseGet /mod/tmp/Apollo 13_20181229_1816-inp.ts
29/12/2018 18:20:00 - CG(3628)- System power on attempted
29/12/2018 19:14:30 - CG(3628)- ChaseGet end /mod/tmp/Apollo 13_20181229_1816-inp.ts Size 1114112000 bytes
29/12/2018 19:18:22 - CG(9551)- ChaseGet /mod/tmp/Apollo 13_20181229_1915-inp.ts
29/12/2018 21:00:32 - CG(9551)- ChaseGet end /mod/tmp/Apollo 13_20181229_1915-inp.ts Size 2049728512 bytes
29/12/2018 21:13:06 - CG(21643)- System power Off attempted, ChaseGet power On was at 18:20:00 
30/12/2018 19:01:44 - CG(3591)- ChaseGet /mod/tmp/Celebrity Chase Christmas Special_20181230_1858-inp.ts
30/12/2018 19:01:44 - CG(3591)- System power on attempted
30/12/2018 20:02:56 - CG(3591)- ChaseGet end /mod/tmp/Celebrity Chase Christmas Special_20181230_1858-inp.ts Size 2663526400 bytes
31/12/2018 17:01:57 - CG(3908)- ChaseGet /mod/tmp/The Chase_ Celebrity Special_20181231_1658-inp.ts
31/12/2018 17:01:57 - CG(3908)- System power on attempted
31/12/2018 18:00:48 - CG(3908)- ChaseGet end /mod/tmp/The Chase_ Celebrity Special_20181231_1658-inp.ts Size 2526486528 bytes
31/12/2018 18:13:07 - CG(10540)- System power Off attempted, ChaseGet power On was at 17:01:57 
01/01/2019 04:02:48 - CG(4001)- ChaseGet /mod/tmp/The Chase_20190101_0359-inp.ts
01/01/2019 04:02:48 - CG(4001)- System power on attempted
01/01/2019 04:49:59 - CG(4001)- ChaseGet end /mod/tmp/The Chase_20190101_0359-inp.ts Size 2047807488 bytes
01/01/2019 04:53:07 - CG(8512)- System power Off attempted, ChaseGet power On was at 04:02:48 
01/01/2019 21:03:14 - CG(14006)- ChaseGet /mod/tmp/New_ The Yorkshire Vet Winter____20190101_2100-inp.ts
01/01/2019 22:00:19 - CG(14006)- ChaseGet end /mod/tmp/New_ The Yorkshire Vet Winter____20190101_2100-inp.ts Size 2617016320 bytes
02/01/2019 20:32:57 - CG(3041)- ChaseGet /mod/tmp/Coronation Street_20190102_2029-inp.ts
02/01/2019 21:00:09 - CG(3041)- ChaseGet end /mod/tmp/Coronation Street_20190102_2029-inp.ts Size 1135325184 bytes
05/01/2019 16:39:55 - CG(3708)- ChaseGet /mod/tmp/The Chase_ Celebrity Special_20190105_1636-inp.ts
05/01/2019 16:39:55 - CG(3708)- System power on attempted
05/01/2019 17:38:07 - CG(3708)- ChaseGet end /mod/tmp/The Chase_ Celebrity Special_20190105_1636-inp.ts Size 2580250624 bytes
05/01/2019 17:53:07 - CG(10509)- System power Off attempted, ChaseGet power On was at 16:39:55 
06/01/2019 17:01:21 - CG(3985)- ChaseGet /mod/tmp/The Chase_ Celebrity Special_20190106_1658-inp.ts
06/01/2019 17:01:21 - CG(3985)- System power on attempted
06/01/2019 18:01:12 - CG(3985)- ChaseGet end /mod/tmp/The Chase_ Celebrity Special_20190106_1658-inp.ts Size 2510077952 bytes
06/01/2019 18:13:07 - CG(10774)- System power Off attempted, ChaseGet power On was at 17:01:21 
06/01/2019 21:04:04 - CG(14772)- ChaseGet /mod/tmp/New_ Manhunt_20190106_2100-inp.ts
06/01/2019 21:04:46 - CG(14816)- ChaseGet /mod/tmp/SAS_ Who Dares Wins_20190106_2101-inp.ts
06/01/2019 22:01:20 - CG(14772)- ChaseGet end /mod/tmp/New_ Manhunt_20190106_2100-inp.ts Size 1839484928 bytes
06/01/2019 22:03:01 - CG(14816)- ChaseGet end /mod/tmp/SAS_ Who Dares Wins_20190106_2101-inp.ts Size 2651521024 bytes
07/01/2019 19:31:37 - CG(2925)- ChaseGet /mod/tmp/The Chase_ Celebrity Special_20190107_1928-inp.ts
07/01/2019 20:00:10 - CG(2925)- ChaseGet end /mod/tmp/The Chase_ Celebrity Special_20190107_1928-inp.ts Size 678383616 bytes
07/01/2019 21:03:03 - CG(12547)- ChaseGet /mod/tmp/New_ Manhunt_20190107_2059-inp.ts
07/01/2019 22:01:55 - CG(12547)- ChaseGet end /mod/tmp/New_ Manhunt_20190107_2059-inp.ts Size 1859489792 bytes
08/01/2019 20:01:57 - CG(4155)- ChaseGet /mod/tmp/The Secret Life of the Zoo_20190108_1958-inp.ts
08/01/2019 20:01:57 - CG(4155)- DLNA Server is NOT running.
08/01/2019 20:01:57 - CG(4155)- System power on attempted
08/01/2019 21:01:39 - CG(4155)- ChaseGet end /mod/tmp/The Secret Life of the Zoo_20190108_1958-inp.ts Size 3002208256 bytes
08/01/2019 21:04:58 - CG(9972)- ChaseGet /mod/tmp/New_ Manhunt_20190108_2101-inp.ts
08/01/2019 22:02:35 - CG(9972)- ChaseGet end /mod/tmp/New_ Manhunt_20190108_2101-inp.ts Size 1641402368 bytes
08/01/2019 22:13:07 - CG(16948)- System power Off attempted, ChaseGet power On was at 20:01:57 
12/01/2019 16:01:38 - CG(3932)- ChaseGet /mod/tmp/The Chase_20190112_1558-inp.ts
12/01/2019 16:01:38 - CG(3932)- DLNA Server is NOT running.
12/01/2019 16:01:38 - CG(3932)- System power on attempted
12/01/2019 16:59:44 - CG(3932)- ChaseGet end /mod/tmp/The Chase_20190112_1558-inp.ts Size 2542673920 bytes
13/01/2019 14:41:19 - CG(3807)- ChaseGet /mod/tmp/The Chase_20190113_1438-inp.ts
13/01/2019 14:41:19 - CG(3807)- DLNA Server is NOT running.
13/01/2019 14:41:19 - CG(3807)- System power on attempted
13/01/2019 15:40:59 - CG(3807)- ChaseGet end /mod/tmp/The Chase_20190113_1438-inp.ts Size 2530037760 bytes
13/01/2019 15:53:07 - CG(9957)- System power Off attempted, ChaseGet power On was at 14:41:19 
13/01/2019 18:04:11 - CG(3545)- ChaseGet /mod/tmp/New_ Dancing on Ice_20190113_1801-inp.ts
13/01/2019 18:05:10 - CG(3545)- DLNA Server is NOT running.
13/01/2019 20:01:48 - CG(3545)- ChaseGet end /mod/tmp/New_ Dancing on Ice_20190113_1801-inp.ts Size 6560899072 bytes
13/01/2019 21:05:04 - CG(19770)- ChaseGet /mod/tmp/SAS_ Who Dares Wins_20190113_2101-inp.ts
13/01/2019 22:03:42 - CG(19770)- ChaseGet end /mod/tmp/SAS_ Who Dares Wins_20190113_2101-inp.ts Size 2771243008 bytes
What's been changed to cause this?
 
MymsMan said:
You don't have a problem with the Content share becoming disabled, it was active when checked by detectads 1 second earlier.
Click to expand...

If it is on, why is the box menu saying it is off? And why does changing the setting there fix the immediate issue?
 
I changed the logging to report when the server is not running and Power on/off attempts with the last chaseget update that prevented it waiting indefinitely.
Previously they were only logged with debugging logging level turned on.
In @Trev 's case it is showing the system working correctly, the server is not running because the system is is standby so it issues a power on to activate the system and there are no subsequent Not running messages for that programme. Later the system is powered off again after the recording completes. You are not seeing the loop of repeated Not Running messages a minute apart
 
Thanks Myms. Just wondered why 'all of a sudden' it started showing in the log. But you just explained that, thanks.
Me too will go away (for now).
 
Matthew said:
If it is on, why is the box menu saying it is off? And why does changing the setting there fix the immediate issue?
Click to expand...
I suspect the box is actually showing whether or not the DLNA server is active combing the two different flags for display convenience, The Webif DLNA Reset page shows the two flags separately [B]Server Status[/B] Enabled -> Running.
Re-enabling it via the box would restart the server - something that should happen automatically every time the box comes out of standby.
AFAIK we have no way in the webif to start/stop the DLNA server other that bringing the using the remote control power on/off commands.
I don't know of any diagnostics that could show why the DLNA server was not running while it was powered on - hopefully rebuilding the DLNA database will cure the underlying problem. Maybe @af123 can suggest other things to try if that doesn't improve things
 
Oh no, the problem is back again and it fails every day currently. It has occurred since I had the crash when setting up the new aerial so that may be significant.

Looking a the DLNA Server Information is says: Server Status Enabled - Not Running.
In the box menu it says Content Sharing: Off

Simply turning Content Sharing: On does nothing (Server Information remains as above) Leaving Content Sharing alone and trying to reset the server gives:

Code: 
To reset the DLNA Database, disable Content Sharing in the Humax menus at
Settings->System->Internet Setting->Content Share
and click the button again.

I have to turn Content Sharing On, then Off, then reset DLNA Server, then turn Content Sharing On again to restore operation.

So any idea what is actually going wrong?

PS The setting appears to change whilst the box is in operation!
 
prpr said:
Possibly you have a corrupted recording that is upsetting DLNA. Finding it might be tricky though.
Click to expand...
Or a corrupted entry in the DLNA database that causes the server to shut down when it encounters it.
Rebuilding the DLNA database cures the problem until another corruption occurs which could easily be caused by a crash whilst updating.
 
MymsMan said:
Or a corrupted entry in the DLNA database that causes the server to shut down when it encounters it.
Click to expand...
Yes, but he's already been through the DLNA database reset procedure, so I think the balance of probabilities is on a bad recording rather than a random crash during an update.
I think the only way out of this is via divide and conquer - move all recordings off and see if it restores reliability. If it does, then put half of them back and repeat until you find which half causes the problem. It's tedious and time-consuming and you need external storage to match at least the size of all recordings.
 
prpr said:
Yes, but he's already been through the DLNA database reset procedure, so I think the balance of probabilities is on a bad recording rather than a random crash during an update.
Click to expand...
Rebuilding the database at least provided a three week respite from the problem while it was almost daily before.
If it was a recording problem why would rebuilding database cure it albeit temporarily

We know that databases on the Humax are not the most robust with occasional problems reported on the queue, sysmon, epg and others
 
You must log in or register to reply here.
Back
Top