for another example of the failures of atsc3.0 drm check out this thread (https://community.getchannels.com/t/zin ... -hdr/42758)

It shows how atsc 3.0 drm is able to be bypassed using a3sa approved converter boxes.

I thought all android/firetv devices were already supported. What does this add support for? thanks.

I noticed the hdhr app on my onn pro boxes updated with the following What's new: "Device support update". Does this mean you are releasing a new series of hdhrs? thanks.

FYI, I fully expect this post to get moderated, just trying to let sd know about it so they can use it as leverage against the a3sa


[removed by moderator]

Again I ask which is easier/cheaper a redesign or being dragged through the muck.

[removed by moderator]

So my question is why not release flex 2.0 with a different chip.

I sent a message to one of those manufacturers from google and they confirm their atsc 3.0 gateway product supports drm. [removed by moderator - see forum rules]


edit: that other company stat starts in z and ends in box is saying their product is now a gateway device.

The one I was referring to is not listed there. [removed by moderator - see forum rules]

edit: under product description type in "atsc 3.0" with out the quotes It will be in that list.

Someone beat sd to having a atsc 3.0 drm gateway device. I wont post the make or model here but part of it is [removed by moderator]. can sd comment on this?

edit:

Just noticed silicondust is listed here (https://a3sa.com/about-a3sa/) under adopters. can sd comment on that as well?

So encrypted channels don't work on Windows 11... I found that surprising, but that's the situation.

Correct. A3SA mandates the use of Widevine DRM which Microsoft does not support in apps. Widevine for browsers on Windows doesn't work with HEVC video or AC4 audio.


So why not release a ...