What I Learnt about my Humax (or CF) Today

It seemed a bit unworkable for general usage then, which is probably why it never got pursued. I don't know whether anything has changed which makes it better/easier now.
 

11/06/2026 - What I Learnt about my Humax (or CF) Today​

The "main chip" in the HD/HDR-Fox T2 is the Broadcom BCM7405 System on a Chip (SoC).
The chip package is a 34 x 34 ball grid array (BGA) with each 'ball' only 1mm in diameter.
Only 976 positions are used, with a segregated square of balls in the middle containing power and ground for the chip and separate subsystems (USB, Ethernet, HDMI, Audio, Video DAC, clocks, RF/UHF, SATA).
Then the four sides of the outer balls are separated into one side for the memory bus connections, one side for USB/Ethernet/HDMI/Audio/RF/UHF/clocks/SATA/EJTAG, one side predominantly GPIO, and one side to PCI/EBI-VRAM/GPIO.
 
Last edited:
Yes, although support for a client certificate is only currently in an ancient dev branch of my on-box youtube-dl it was PRed into the real yt-dl (see linked post) and is in yt-dlp. When the useless maintainer gets around to merging the PR, it could be included in the package. Once you have the cert you just pass it with --client-certificate cert_filename so it's not very hard to use. But I'm not aware of other sites for which device certificates are known that change the extraction.

I should add that each site's extractor needs tweaking to use the cert as well. Also neither my original nor the yt-dlp CLI allows specifying a cert per site, as might conceivably be relevant for a playlist containing links to multiple cert-able sites; it should probably be made visible as an "extractor-arg", which doesn't exist now in yt-dl except via something like --bbc-client-certificate ....

But in the great battle between disk space and pixel resolution I'm generally going for less of both. My wife's phone has more pixels than any display attached to our Humaxen.
 
Last edited:
/df said:
Yes, although support for a client certificate is only currently in an ancient dev branch of my on-box youtube-dl it was PRed into the real yt-dl (see linked post) and is in yt-dlp. When the useless maintainer gets around to merging the PR, it could be included in the package. Once you have the cert you just pass it with --client-certificate cert_filename so it's not very hard to use. But I'm not aware of other sites for which device certificates are known that change the extraction.

I should add that each site's extractor needs tweaking to use the cert as well. Also neither my original nor the yt-dlp CLI allows specifying a cert per site, as might conceivably be relevant for a playlist containing links to multiple cert-able sites; it should probably be made visible as an "extractor-arg", which doesn't exist now in yt-dl except via something like --bbc-client-certificate ....

But in the great battle between disk space and pixel resolution I'm generally going for less of both. My wife's phone has more pixels than any display attached to our Humaxen.
Click to expand...
Thanks @/df , very useful information - I will venture into trying to get this working on my HDR-Fox T2 box and see how far I get. My focus is on iPlayer. Will be challenging for me (only Python I've done is a Sudoku solver after skim reading a couple of books), but that's half the fun! Thanks for taking the time posting the code that you did (even though, as some 'BH' guy said, "Christ, that was 5 years ago!"), it's really useful to me - as is the PR. 🙏
 
You must log in or register to reply here.
Back
Top