[mythtv-users] Unexpected gotchas with Digital transmission

[Gary Buhrmaster]

On Wed, Apr 26, 2017 at 8:05 PM, Jay Foster <jayf0ster at roadrunner.com> wrote:
....
> Here in the USA, we will soon face the same issue.

Define "soon".

> Cable is not ATSC,
> AFAIK.  For OTA users, the roll out of ATSC 3.0

No one has predicted that the transition will be
"soon" except for demo/stunt programming due
to the (existing) dearth of TV sets that can receive
it, and the (existing) dearth of "dongles" (and/or STBs)
that can receive it for existing TVs.  The FCC NRPM
requires stations to continue to broadcast ATSC 1.0
while allowing ATSC 3.0 transmission, and, btw,
there are no "extra" frequencies available, so
(strong, sometimes cutthroat) competitors will
need to work together in a market to offer a
transition strategy, and they are not yet allowed
to stop ATSC 1.0.

> will require new hardware
> (different modulation) and software (H.265 vs MPEG2). Is there any
> development in mythtv to support ATSC 3.0?

Likely there will be some needed, but as long
as the hypothetical hardware manufacturers
(none currently exist) of tuners supply drivers
that are v4l compliant things should "just work"
(and if they do not offer v4l drivers you should
not support their hardware by buying it), as the
current FFMpeg in MythTV already supports
H.265.  It likely should be noted that ATSC 3.0
allows (but does not require) content protection.