[mythtv-users] Recommendations needed for new FE box

[David Engel]

On Fri, Jul 27, 2018 at 11:49:30AM -0400, Steve Greene wrote:
> 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?

Peter Bennett can certainly speak more definitively on this, but
here's my two cents.

Peter's recent work on adding MediaCodec support on Android using
ffmpeg should make the task of updating our VAAPI support much easier.
Currently, we use VAAPI directly.  We also previously had no support
for the decoder doing the deinterlacing (like I think VAAPI does for
it's advanced deinterlacing).  We now have that capability thanks to
Peter's MedicCodec work.  So, it should *only* be a matter of
replacing our direct VAAPI support with that provided by ffmpeg, like
we already do for software, VDPAU and MediaCodec.  Of course, the
devil will be in the details.

David

> Steve
> 
> 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
> >

> _______________________________________________
> 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


-- 
David Engel
david at istwok.net