DaveNLR wrote: Tue Jul 01, 2025 2:47 am
Is there any consideration to making an Android dongle you could plug into the HDMI port on a single TV that could connect to the tuner to decode the DRM channels?
The Z company is attempting this, with hardware devices, and has already had the rug pulled out from under them once. I will be surprised if their next attempt (supposedly due December) doesn't have the same results.
The Z company already said that version 4.0 of their firmware, you can have just your main Z device and all other devices with the app itself would be able to watch ATSC 3.0 with DRM. No need for other client devices. That is coming soon, so it will behave like the current HD Homerun device as a real gateway service. I hope Silicondust can do something, instead of giving excuses of why their current $199 is useless with ATSC 3.0 DRM. Competition is good.
DaveNLR wrote: Tue Jul 01, 2025 2:47 am
Is there any consideration to making an Android dongle you could plug into the HDMI port on a single TV that could connect to the tuner to decode the DRM channels?
The Z company is attempting this, with hardware devices, and has already had the rug pulled out from under them once. I will be surprised if their next attempt (supposedly due December) doesn't have the same results.
The Z company already said that version 4.0 of their firmware, you can have just your main Z device and all other devices with the app itself would be able to watch ATSC 3.0 with DRM. No need for other client devices. That is coming soon, so it will behave like the current HD Homerun device as a real gateway service. I hope Silicondust can do something, instead of giving excuses of why their current $199 is useless with ATSC 3.0 DRM. Competition is good.
I think you are multiple steps behind in the news. They just had their "viable" hardware-to-hardware implementation rejected by the A3SA, nevermind anything with a software client. They're going to try again in December (still hardware-to-hardware).
DaveNLR wrote: Tue Jul 01, 2025 2:47 am
Is there any consideration to making an Android dongle you could plug into the HDMI port on a single TV that could connect to the tuner to decode the DRM channels?
The Z company is attempting this, with hardware devices, and has already had the rug pulled out from under them once. I will be surprised if their next attempt (supposedly due December) doesn't have the same results.
some would think that a retired engineer from a local broadcaster would have a lot more pull to get atsc 3.0 widely accepted, sad to say even seasoned engineers cannot move those loggerheads at a3sa.
to further boster what nickk said about the device not having the capacity to decrypt, the fruit is in the pie.
A3SA Policy: Individual Viewer Data Not Tracked by Content Protection Technology
March 7, 2024
ATSC 3.0 Security Authority LLC (“A3SA”) operates, via a contractor, a proxy server to process requests from ATSC 3.0 receivers (such as televisions or set-top boxes) for cryptographic credentials to decrypt ATSC 3.0 television broadcast signals encrypted by Google’s Widevine technology pursuant to the A3SA content protection specifications.
Because such receivers use the Internet to make requests for decryption credentials, the proxy server is necessarily provided with the Internet protocol (“IP”) address of each receiver based on the Internet service used at its location (e.g., a household). As part of the decryption credentials request, the receiver also provides a unique device identifier to the proxy server. A3SA does not collect or authorize the collection on its behalf of any other personally identifiable information as part of the transaction to process a request for decryption credentials. Viewer data may be collected by third parties in the delivery of ATSC 3.0 broadcasts apart from A3SA’s decryption credentials transactions. Please refer to the applicable policies of these third parties for their privacy practices.
A3SA uses the IP address and device identifier to 1) process and fulfill requests for decryption credentials (i.e., to deliver to the requesting receiver decryption credentials that are enabled for that specific receiver), 2) to streamline subsequent requests from the same receiver, and 3) to monitor the performance and efficiency of the proxy server and to troubleshoot and fix problems which might arise. A3SA does not use or authorize the use of the IP address or device identifier for any other purpose (e.g., marketing to you) and does not provide either one to third parties, nor does it acquire marketing data from third parties to match up to the IP address and device identifier. A3SA may be legally required to preserve or disclose such information in response to a lawful order of a court or agency of government or law enforcement.
The logs of the A3SA proxy server which include the IP addresses and device identifiers are preserved only for as long as reasonably necessary to fulfill the purposes described above (generally anticipated to be up to sixty (60) days), and are then deleted.
this information though not practical to this forum is helpful in understanding what happens in the handshake between two devices.
