Has anyone who has upgraded to the new Humax beta software (1.02.27) experienced any problems with recordings?
My box was set to record two consecutive programmes on C4 HD today - 12:25 and 12:55. The box was in full standby prior and woke up correctly 15 minutes prior to the first recording and recorded it successfully.
(
Start Time Sat Apr 14 12:29:12 2012 BST (Scheduled: Sat Apr 14 12:25:00 2012 BST)
End Time Sat Apr 14 12:55:08 2012 BST (Scheduled: Sat Apr 14 12:55:00 2012 BST)
)
The second one did not begin recording straight away and was still not recording by 13:09. At that point I turned the box fully on using the remote control and straight away it said "START RECORD" (or something similar) on the front panel and started recording.. It stopped at the proper time so I have a 14 minute recording and presumably if I hadn't intervened it would have just completely failed.
(
Start Time Sat Apr 14 13:09:57 2012 BST (Scheduled: Sat Apr 14 12:55:00 2012 BST)
End Time Sat Apr 14 13:24:55 2012 BST (Scheduled: Sat Apr 14 13:25:00 2012 BST)
)
I've never seen this behaviour with 1.02.20 so I'm wondering if it could be a bug introduced in the latest version. I'll see if I can reproduce this later.
My box was set to record two consecutive programmes on C4 HD today - 12:25 and 12:55. The box was in full standby prior and woke up correctly 15 minutes prior to the first recording and recorded it successfully.
(
Start Time Sat Apr 14 12:29:12 2012 BST (Scheduled: Sat Apr 14 12:25:00 2012 BST)
End Time Sat Apr 14 12:55:08 2012 BST (Scheduled: Sat Apr 14 12:55:00 2012 BST)
)
The second one did not begin recording straight away and was still not recording by 13:09. At that point I turned the box fully on using the remote control and straight away it said "START RECORD" (or something similar) on the front panel and started recording.. It stopped at the proper time so I have a 14 minute recording and presumably if I hadn't intervened it would have just completely failed.
(
Start Time Sat Apr 14 13:09:57 2012 BST (Scheduled: Sat Apr 14 12:55:00 2012 BST)
End Time Sat Apr 14 13:24:55 2012 BST (Scheduled: Sat Apr 14 13:25:00 2012 BST)
)
I've never seen this behaviour with 1.02.20 so I'm wondering if it could be a bug introduced in the latest version. I'll see if I can reproduce this later.