See https://hummy.tv/forum/threads/adding-srt-subtitles-to-a-humax-video-file.10491, especially the linked https://hummy.tv/forum/threads/youtube-dl-download-files-from-youtube-com-or-other-video-platforms.8462/post-147408.
So, this behaviour is in fact (would it be unfair to say "surprisingly"?) just as documented and indeed what I can observe.
Two edge cases:
the timeout accumulates, so that after quickly changing channel up, then down, say, with timeout 15s, the info bar is shown for ~30s
invoking the info bar...
You'd think so, but my unsupported recollection says otherwise. But I'm not sure what "recent" change might be responsible. Maybe some CF package, eg, one that hooks the Humax blob? @xyz321?
I see the same thing on the HDR too.
The name INFO_DISPLAY_TIME is used in the blob and looks like the...
I've noticed that the Info-bar timeout doesn't appear to respect any timeout value (Off, 1-20s) set in Menu>Settings>Preferences>Screen Display>Info Display Time. Rather, it's always ~30s.
Is this happening for anyone else? I could swear that quite recently the Info-bar used to disappear too...
It's quite an extensive update, so it needs a new package version. You could upgrade to the 2025.04.01 code, which should still work, by applying this 1-line change.
There doesn't seem to be a specific thread for the epg package (also, the forum doesn't support searching for TLAs).
This output was shown today in the package upgrade dialog:
>>> opkg upgrade epg
Upgrading epg on root from 1.3.0-1 to 1.3.0-3...
Downloading...
Uncommanded resets typically don't appear as crashes. While the Humax s/w is running, apparently one or more of the databases in use is trashed, possibly a flash storage issue, or possibly just Humax s/w. The Humax s/w continues to run, though strange effects may be seen. The next start fails...
Plainly it's not ideal, verging on POSSLQ-exclusive. In due course I could add that sequence to the remote start-up sequence or perhaps organise some CF trickery to send the commands. Or identify which component has gone off-spec and replace it. Could the matching item be in a sacrificial Humax...
My experience after a few weeks with an HDMI-capable AV receiver between the aged Humax, with Pin 19 isolated, and the TV is that the sound is available at turn-on but the TV display is black. Supposing that the set-up had been running at 1080p before turning off, a series of 6 V.Format remote...
Didn't we find some guidance in the spec regarding what period might be "significant" in relation to the what the Humax s/w subtracts from the next scheduled event to calculate its wake-up time?
The TDA9984A HDMI o/p chip isn't meant to support 1920x540, so I suppose something must have made its 1080i seem like 540p.
At least the tuner from which the EPG and TV out is derived developed twisted underwear and then worked again after power cycling. Is that surprising?
I guess component failure when what formerly worked failed first intermittently and then permanently. But digital security is all about introducing new failure modes that manifest themselves as "computer says no": that would especially have applied when a whole lot of HDMI implementations were...
My guess is that because of failing to complete the negotiation the Humax s/w (?) fails to enforce HDCP (which is initially off): https://hummy.tv/forum/threads/green-screen-known-as-hdmi-handshake-for-me-finally-cured.11456/post-176627.
Adding to the above, I suppose a passive switch would...
See https://hummy.tv/forum/threads/adding-srt-subtitles-to-a-humax-video-file.10491, especially the linked https://hummy.tv/forum/threads/youtube-dl-download-files-from-youtube-com-or-other-video-platforms.8462/post-147408.
So, this behaviour is in fact (would it be unfair to say "surprisingly"?) just as documented and indeed what I can observe.
Two edge cases:
the timeout accumulates, so that after quickly changing channel up, then down, say, with timeout 15s, the info bar is shown for ~30s
invoking the info bar...
You'd think so, but my unsupported recollection says otherwise. But I'm not sure what "recent" change might be responsible. Maybe some CF package, eg, one that hooks the Humax blob? @xyz321?
I see the same thing on the HDR too.
The name INFO_DISPLAY_TIME is used in the blob and looks like the...
I've noticed that the Info-bar timeout doesn't appear to respect any timeout value (Off, 1-20s) set in Menu>Settings>Preferences>Screen Display>Info Display Time. Rather, it's always ~30s.
Is this happening for anyone else? I could swear that quite recently the Info-bar used to disappear too...
It's quite an extensive update, so it needs a new package version. You could upgrade to the 2025.04.01 code, which should still work, by applying this 1-line change.
There doesn't seem to be a specific thread for the epg package (also, the forum doesn't support searching for TLAs).
This output was shown today in the package upgrade dialog:
>>> opkg upgrade epg
Upgrading epg on root from 1.3.0-1 to 1.3.0-3...
Downloading...
Uncommanded resets typically don't appear as crashes. While the Humax s/w is running, apparently one or more of the databases in use is trashed, possibly a flash storage issue, or possibly just Humax s/w. The Humax s/w continues to run, though strange effects may be seen. The next start fails...
Plainly it's not ideal, verging on POSSLQ-exclusive. In due course I could add that sequence to the remote start-up sequence or perhaps organise some CF trickery to send the commands. Or identify which component has gone off-spec and replace it. Could the matching item be in a sacrificial Humax...
My experience after a few weeks with an HDMI-capable AV receiver between the aged Humax, with Pin 19 isolated, and the TV is that the sound is available at turn-on but the TV display is black. Supposing that the set-up had been running at 1080p before turning off, a series of 6 V.Format remote...
Didn't we find some guidance in the spec regarding what period might be "significant" in relation to the what the Humax s/w subtracts from the next scheduled event to calculate its wake-up time?
The TDA9984A HDMI o/p chip isn't meant to support 1920x540, so I suppose something must have made its 1080i seem like 540p.
At least the tuner from which the EPG and TV out is derived developed twisted underwear and then worked again after power cycling. Is that surprising?
I guess component failure when what formerly worked failed first intermittently and then permanently. But digital security is all about introducing new failure modes that manifest themselves as "computer says no": that would especially have applied when a whole lot of HDMI implementations were...
My guess is that because of failing to complete the negotiation the Humax s/w (?) fails to enforce HDCP (which is initially off): https://hummy.tv/forum/threads/green-screen-known-as-hdmi-handshake-for-me-finally-cured.11456/post-176627.
Adding to the above, I suppose a passive switch would...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.