Government Finally Reveals When It Wants Freeview Gone

If the beloved 'crystal radio' electronics project will stop working soon, then that will be a sad enough day.
Old valve radio - can't use anymore, you need DAB(+). Soon, the good old telephone and TV... sorry, can't use anymore - you need broadband. Older (or computer/Internet illiterate) pensioner: "Dab-what... broad-what?".
Sad days for the older generation - especially if they have nobody close to support them.
 
There is a much more fundamental problem that the people running the 'consultation' have seemingly failed to grasp, which is one of numeric overflow.
DVB uses Modified Julian Dates (MJD) in its EPG data and to ease calculations between DD/MM/YYYY and MJD, has certain fixed points covering 200 years (which ought to be enough for anyone, right?).
These are 1 Mar 1900 = MJD 15079 and 28 Feb 2100 = MJD 88127 (which neatly avoids the /100 & /400 leap year problems - 2000 was a leap year every 4, 2100 isn't).
When they were designing/specifying the system in 1995, they decided to use MJD and 10 Oct 1995 was already day 50000.
The real trouble is that they only allocated 16 bits for the value of the day (and effectively wasted 2 of them to start with), so the max MJD in DVB is 65535 = 22 Apr 2038, which is nowhere near the other year 2100 calculation limit.
It seems like folks have finally caught on.
I'm staggered to read that the 'geniuses' at BBC R&D, DVB and some others in the industry only cottoned on to this a couple of years ago.
I, and others, have known about it for a lot longer.
Articles that have recently come to my attention:
https://www.bbc.co.uk/rd/articles/2026-11-televisions-unix-time-2038
https://dvb.org/news/dvb-si-update-solves-the-2038-date-rollover/

It seems they have 'fixed' this by re-allocating one of the bits they originally wasted to mean something else i.e.
MJD 0 is now 23 Apr 2038 and MJD 32767 is way in the future (9 Jan 2127)
There is also scope to use the other bit they originally wasted to give another 45 years or so (MJD 32768 to MJD 49151).

None of this will fix existing broken kit of course, but it's a start for fixing anything new or that can be updated from here on in.
 
Seems likely the HDR Fox T2 will die either on 19 Jan 2038 due to 32 bit signed unix time rollover, or 23 April 2038 due to modified Julian date 16 bit rollover. If the first doesn't get it (do we know whether Humax used signed or unsigned time?) the second will. I can't see Humax issuing an update for this, and it doesn't feel like something that can be fixed with custom firmware.

EDIT: live TV will probably still work. But without a working EPG the HDR Fox T2 seems pretty pointless to me.
 
Last edited:
At least they have fixed a similar problem with the mainframe computers used by the US military to control their nuclear missiles. 2028 was the deadly rollover date in that instance!
 
None of this will fix existing broken kit of course, but it's a start for fixing anything new or that can be updated from here on in.
In my code, it was trivially easy to adapt to the new rules - add two lines, and alter a single comparison in one more.
Code which previously handled 1900-2038 now handles 1948-2100.
 
Back
Top