<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 11/09/2016 02:20 PM, John P Poet
      wrote:<br>
    </div>
    <blockquote
cite="mid:CACSqvJ=RrUPSzOe=MefGc6SEV4ZocdDAhycBojSCib591YP=Vg@mail.gmail.com"
      type="cite">
      <div dir="ltr">On Wed, Nov 9, 2016 at 12:07 PM Gary Buhrmaster
        <<a moz-do-not-send="true"
          href="mailto:gary.buhrmaster@gmail.com">gary.buhrmaster@gmail.com</a>>
        wrote:<br>
        <div class="gmail_quote">
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">On Wed,
            Nov 9, 2016 at 6:41 PM, Peter Bennett <<a
              moz-do-not-send="true" href="mailto:pgbennett@comcast.net"
              class="gmail_msg" target="_blank">pgbennett@comcast.net</a>>
            wrote:<br class="gmail_msg">
            <br class="gmail_msg">
            > MythTV does not detect the subtitles.<br
              class="gmail_msg">
            <br class="gmail_msg">
            What version of MythTV?  There was a discussion about<br
              class="gmail_msg">
            4 months ago where (I think) a dev thought the FFMpeg<br
              class="gmail_msg">
            in 0.28 should have the needed support (but it was<br
              class="gmail_msg">
            unverified, and AFAIR no one confirmed/denied).<br
              class="gmail_msg">
            <br>
          </blockquote>
          <div><br>
            Maybe start here:<br>
            <br>
            <a moz-do-not-send="true"
              href="https://code.mythtv.org/trac/ticket/12893">https://code.mythtv.org/trac/ticket/12893</a>
            <br>
            <br>
          </div>
          <div>I have a patch which I can contribute from a work
            colleague, which adds it for a 2 or 3 year old version of
            ffmpeg, but I am pretty sure it does not apply against the
            current ffmpeg.<br>
             <br>
          </div>
          <div>John<br>
            <br>
          </div>
        </div>
      </div>
    </blockquote>
    Thanks John<br>
    <br>
    Is it acceptable to add a fix to our local ffmpeg, knowing that it
    will be lost when we pull in the next version? If so I can give this
    a test and see what happens.<br>
    <br>
    One problem - it may work with ffmpeg but fail with vdpau and other
    hardware assisted decoders.<br>
    <br>
    Peter<br>
  </body>
</html>