Thank you very much for this explanation. Most informative.

I believe I remember that there was an explanation given by an SD rep quite some time back in some random forum thread about why the time to tune to an ATSC 3.0 channel takes longer than the time to tune to an ATSC 1.0 channel. I can't seem to find that posted explanation, but would like a repeat if...

If all you want to do is watch ATSC 3.0 DRM Live content on only one TV you should buy a nongateway device. But keep in mind that you can only watch on the connected TV I fully well understand and appreciate the conceptual difference in the two products. As I have expressed many times I really have...

There is no time frame to give. Though SD may get such out sooner, and many of us hope so, I've heard rumblings from non-SD sources that formal approval of non-DTCP2 methods of communications with apps are about a year away from being formally approved (SD has provisional approval for an approach t...

AGAIN, set-top-boxes follow a different set of rules. Whatever has been "SOLVED" there does not apply to the HDHomeRun at all. Of course not. But "they" HAVE apparently "solved" whatever total set of issues faced them, as they can at least low the LIVE VIEW of DRM cont...

ATSC 3.0 audio is fully supported on Windows with the HDHomeRun app. No codec pack required. Wait... are you referring to the cloud-assisted decoding automatically invoked by the Windows app as what you call "fully supported"? Windows 10 or Windows 11? Yes, it does work and produce sound ...

While waiting for the SD-published "DRM solution" for my Flex 4K to materialize (if/when it ever does...), I have placed an order for a dual-tuner Zapperbox M1. It will be here next Monday. I will continue my playing in the ATSC 3.0 sandbox as an early adopter, this time with a whole 'noth...

cordcutter wrote: ↑Sun Oct 15, 2023 2:02 pm I'm on firmware 20230719

Current firmware for Flex 4K is 20231020.

We have confirmed the problem of the last few minutes of a recording playback repeating itself. This problem must have been reported by someone else, but that's still good that you have confirmed it and are working on it. My experimenting has never reached anything near the last few minutes of a re...

Not surprisingly, no response of any kind from SD. Despite the absolute courtroom-allowed video evidence of the multiple defects in v82 of the Roku HDHR app that I posted above, CRICKETS from SD. I would have at least expected some response, any response, acknowledging that the video proof is "...

I am not an SD fanboy by any means. I call them out when they need to be held accountable. What are you claiming that they are not being transparent about? Probably what we're all wanting to hear is an honest and specific "status report", as to exactly: (a) Where does this all stand, both...

From "newly discovered today"... Roku v82 HDHR app FF function (and probably REW function as well, but I haven't tried that) appears to correctly skip forward 30-seconds and set the correct location pointer in INI/CFG for the recording. But it does not resume playback correctly after the 3...

Problem (4) posted above: (4) After restarting the HDHR app, reattempting the playback of a "stuck after FF" recording no longer starts playback. Instead, the fuel gauge reappears suggesting it is still trying to FF or reposition and resume playback at the new location, as if somehow the a...

Problem (3) posted above: (3) With version 82.0 the FF and REW functions appear broken. The first time the FF button is pressed it appears to initiate the expected FF operation. The screen goes black (no audio or video), a "fuel gauge" bar appears and a white "progress indicator"...

Problem (2) posted above: (2) Pushing the black PLAY/PAUSE button while playing a recording causes the onscreen video to pause (i.e. "freeze") but the audio continues un-paused. When the PLAY/PAUSE button is then pressed a second time to resume playback, the video is now presented in a sup...