grahamlthompson - 1 hour ago
I don't have the box, but has anyone tried pulling the plug overnight ?
I don't know about pulling the plug, pulling teeth may be easier.
It doesn't lose the schedule, it simply doesn't populate and display it when coming out of standby the next day.
There are some ingenious work arounds such as deleting a single channel, i.e. one of the many rubbish ones, which will force a rescan of the schedule, repopulate and display it.
Cold rebooting also solves the problem, so I'd imagine pulling the plug overnight would only result in the same cold reboot the following day.
It happens intermittently for some and not at all for others so only those users where it happens intermittently will have any insight as to causes. At first I though it may be a timing issue where the hard drive isn't 100% ready when coming out of standby, but I believe even those with two boxes 500GB and 1TB haven't seen a pattern.
However, a date change, as BlackGhost alluded to, when the box is in standby could also be the problem. i.e. if the box is still switched on and running after midnight or GMT then it handles the change of date and has no problem with the schedule. However, if the box goes into standby before midnight or GMT then when it comes out of standby it hangs on the schedule as the date is wrong.
This may explain the intermittent behaviour for some users where the box may or may not have been still on and running past midnight or recording during this time. We know the problem does not occur when leaving the box on and not letting it go into standby.
The problem doesn't seem to happen afternoon or evening so it's not length of time in standby. It seems to coincide with date change. Why this happens for some and not at all for others though simply adds to the confusion.
The trouble is it's time consuming to figure out a pattern. It'd be interesting to set a recording to run through midnight/GMT and possibly at other times on other mights which can be easily deleted the next day just to see if a time or pattern can be pinned down. Maybe one of the users that are affected could set an out of hours recording or two.
I assume Humax don't know the exact cause yet.