I and others used the beta firmware without issue for weeks before it became an official release. My box offers Record Whole Series, Record Single Programme and Watch from the epg. And record or watch from a manual recording reservation same as it always did. So what precisely are you missing ?

Same problem here so i e-mailed humax here's the reply :

Dear Sir,

Changes were made on 1.00.15 software to resolve issues with scheduled recording failures. The failures happened when the Event ID information for a programme set to record changed and the Foxsat-HDR did not detect and schedule correctly. IN the 1.00.15 software, each time the EPG is accessed the product will make sure that the complete EPG is refreshed, this should take in the region of 45 seconds and you can then schedule recordings; during this period you can navigate the EPG. If you wish to quickly access the EPG to schedule a recording then you can do so by pressing the Schedule button on the remote and then pressing the red button to access the EPG; during this process the EPG is not updated.

Tried the Schedule Button On The Remote ( Never Used It Before ) Then The Red Buttons And It Works Fine Now

Thanks David

Thanks for sharing that email - very helpful.

At least that email suggests a sane reason for the change - it's not Humax being incompetent or difficult. (unless you think they should have solved the problem another way - like checking the event IDs in the background - I'm sure the usual suspects will be along in a moment to tell us how utterly stupid Humax are for not doing that!).


Anyway, I might be being paranoid, but reading between the lines, that email seems to say that using the "schedule, red" work-around risks missed recordings. It'll only happen when the broadcasters change an event ID between the last time the Humax grabbed the data and you trying to set the recording, but in such a case, it will go wrong.

(I'm going to have to go and find out what an Event ID is now! Can't make any intelligent comments until I do. Not promising any intelligent comments afterwards either ).

Cheers,
David.

http://myhumax.org/forum/topic/is-it...lures#post-880

Yes, I'd seen that thread.

Two separate issues there: changing event IDs, and re-using the same programme CRID for a different programme. You can check the latter in a debug menu on the Humax which makes it show you the CRIDs, but I have no idea about the former. I'm not sure the two separate issues were properly differentiated in the experiments reported in that thread.


So are you reading that email as talking about two different things - i.e. that the changes to fix the missed recordings when the event ID is changed are separate from the changes which mean you can't record from the Guide for ~40 seconds? i.e. the using Schedule+Red won't cause any problems?

If they mean it that way, then we just return to conclusion 1: Humax are incompetent for trashing the Guide button for no good reason.

Seriously, I wish Bob Cat would tell us which it is - either Schedule+Red is perfectly safe to use, or not.

Cheers,
David.

The problem with the event id's has been around since the launch of ITV1-HD. It seems to affect specific programmes as mentioned in the thread. Awaiting the download of a new epg to set a recording is not a guarantee that in the event that ITV won't still cause a recording failure. Particulary during the run of a series recording.

However I only ever use schedule/red to schedule recordings including a lot of ITV-HD and not had a failed recording for weeks, not since a spate of failings on ITV1-HD caused problems on both Freeview and Freesat.

As I don't record the programmes that seem to be regulary affected I can't tell if setting using guide will make a significant difference. As anyone scheduling a recording while recording will seamlessly access the cached epg anyway I doubt the difference is that much,

From the Digital Video Broadcasting (DVB);
Specification for Service Information (SI) in DVB systems :-

Note the "uniquely allocated ......", this is important.
Basically, the Series & Program CRIDs you can see on the Humax in the EPG are for identifying future programmes that may be linked or standalone. If it's a series, when that timer has executed, it looks forward for that Series CRID, and a Program CRID that is not the same as the one it is just executing, i.e. not a repeat within the series. That's all those CRIDs are/were used for.

When you set a recording timer from the EPG, it also stores the event_id, which you can't see, with that timer. This event_id, according to the specs, must be unique for the life of the EPG. So, the box is looking in the SI data stream, for the Running Status Flag of that event_id, to change from future to present (EITp/f), indicating that the program is now starting, so start recording. Of course, if naughty broadcasters, like ITV had/have been doing, change the event_id during it's lifetime, then the timer will be looking for the wrong event_id, and will never see the RSF change, it hasn't got a cat in hell's chance, because the broadcaster changed the unique key; so you will get an unexplained failed recording.

Obviously, Humax have changed something in 1.00.15 to try and catch these situations, and improve it for us users, who would have no idea what was going on. Pure speculation, but maybe the box downloads the whole EPG now, and checks current timers against the new EPG for event_id changes, possibly using the Prog CRIDs as it's reference? Also, not letting you set a new timer until it has completed the download, in case the event_ids were wrong in the cached EPG? But, not being a Humax engineer, I obviously don't know how they've improved this event checking in the code to try and cater for broadcaster errors