[mythtv-users] Recommendations needed for new FE box

Steve Greene sgreene820 at gmail.com
Fri Jul 27 15:49:30 UTC 2018

If there are any developers monitoring the discussion, I'd welcome some
input behind the project management challenges involved in adding advanced
interlacing support for Intel chips. If a few of us users could cough up
some funds for a bounty, would that change the complexion of the problem?


On Thu, Jul 26, 2018 at 10:09 PM, Stephen Worthington <
stephen_agent at jsw.gen.nz> wrote:

> On Thu, 26 Jul 2018 13:19:29 -0500, you wrote:
> >My cable provider (Comcast, ugh) now uses .ts containers that use H.264,
> >and that works fine.
> Comcast would have been using MPEG2 Transport Stream containers before
> the change to H.264 for the video.  The old MPEG2 video was always
> delivered in a transport stream container on any cable or broadcast
> system.  MythTV used to store to .mpg files (which implies a Program
> Stream format), when the container was actually a transport stream.
> But eventually that was fixed and MythTV now stores to .ts files to
> make it clear that they are in transport stream format.  If you still
> have any old .mpg files recorded by MythTV, use a program like
> mediainfo or ffprobe and you will see that they are actually transport
> stream files.
> So the only change that Comcast made was to use H.264 video for the
> video streams instead of using MPEG2 video.
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20180727/c05e6b55/attachment.html>

More information about the mythtv-users mailing list