Thanks. Verified that it works for me as well. Much appreciated.

Great! Let me know when to retry to see if fixed.

I believe I have the latest firmware and the latest UI version applied to my HDHR Flex 4K. When in the guide, I’m able to scroll down all the way to my Fox 145.1 channel and I can see there are channels below it like 145.100 and I know they are there, but I cannot scroll to them in the interface on ...

In theory having such a digital signature is a good thing so you know the broadcast came from the broadcaster. In the past only a few rogue broadcasts have ever happened. I believe Lon mentioned those occurrences. So it is useful from a repudiation standpoint. However, if it’s used to force DRM ...

So then I guess if the HDHomerun Flex 4K/HD Homerun app doesn’t receive DRM capabilities from A3SA and high noon was to go into effect, all ATSC 3.0 stations, regardless of whether they use DRM encryption or not, would become unwatchable for us?

Maybe I have the wrong take away from this is being done, but it seems like perhaps there’s an analogy:
DRM is to Encryption as High Noon is to Digital Signature.

So in the case of DRM, the data is encrypted and the playing software can’t decode it unless the A3SA gives them the keys to decrypt and ...

Thanks for correcting me. So what is the expected behavior of the HDHR app on all supported platforms should “high noon” get turned on at some point? Perhaps many stations are already compliant with the requirements for “high noon”?

I’ve been catching up on the “high noon” discussions for ATSC 3.0. Setting aside whether we agree with whether the high noon should or shouldn’t happen, does the fact that the HD Homerun Flex 4K device is Nextgen TV Certified mean that we will be able to watch channels that jump through the “high ...

These issues seem to have corrected themselves now. Channel and show content images now render for all my channels including the two WBFF ATSC 3.0 stations in HDHR and Channels apps.

If you did something on your end, thanks!

Hey, I just noticed WBFF in Baltimore 145.1 and 145.100 don’t display their channel logos like all the other stations.

Also WBFFMob 145.100 is new to me. Not sure when it appeared. Normally the subchannels for ATSC 3.0 didn’t tune in the past to show anything. Is this a test of an MOB capability ...

I’m not sure where to feed this in, but why do you have green/black corporate app logo and a red/blue colored splash screen. And now you are deciding on a blue background, which is fine, but they kinda clash to my eyes. However I was thinking you’d keep your green logo for icon recognition and use a ...

Yeah, I guess what I’m getting at is Apple has their own DRM technology, which I’m guessing is fine to deliver the high quality video and sound content to their devices, but it’s not Google’s Widevine. It would be great if Network streaming devices could use “equivalent” available encryption ...

SD would hopefully mention the slew of devices that support reasonable streaming encryption all the way to the end device, but isn’t Widevine, that should be permitted by the A3SA for transport and is currently in use for streaming.

It would also seem that they are trying to address the issue in non-technical ways (as well as technical) by pursuing the Multiple Dwelling Unit market. Currently people needing a DRM gateway solution is probably around 2.5 x HDHR 4K Flex devices sold, which is a small segment of the ATSC 3.0 ...

Ah, now you might be able to talk sense to Google and get them to convince A3SA that what you want to do is sufficient to protect DRM encrypted media. I don’t believe A3SA has the technical people to make such decisions on their own. So Google probably advises them on the technical stuff regarding ...