<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 11/2/2013 7:59 AM, Anthony Giggins
      wrote:<br>
    </div>
    <blockquote
cite="mid:CAKpY+ao8HO_R+-wGKT_V_DB53=hNV4YEqrTtFBx6o2jJg02wjA@mail.gmail.com"
      type="cite">
      <div dir="ltr"><br>
        <div class="gmail_extra"><br>
          <br>
          <div class="gmail_quote">On 2 November 2013 02:01, John Finlay
            <span dir="ltr">&lt;<a moz-do-not-send="true"
                href="mailto:finlay@moeraki.com" target="_blank">finlay@moeraki.com</a>&gt;</span>
            wrote:<br>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              <div class="im">On 9/29/2013 5:21 PM, Michael T. Dean
                wrote:<br>
                <blockquote class="gmail_quote" style="margin:0 0 0
                  .8ex;border-left:1px #ccc solid;padding-left:1ex">
                  On 09/29/2013 04:33 PM, John Finlay wrote:<br>
                  <blockquote class="gmail_quote" style="margin:0 0 0
                    .8ex;border-left:1px #ccc solid;padding-left:1ex">
                    I'm beginning to think that mythtranscode has been
                    intentionally changed to still work with mythtv but
                    to make post-processing of the losslessly transcoded
                    file impossible. Even mythffmpeg can't process the
                    cut files.<br>
                  </blockquote>
                  <br>
                  No, we had no intention of adding DRM/"lock in" to
                  MythTV. &nbsp;Just a bug that someone needs to figure out.
                  &nbsp;If someone can figure out what MythTV is breaking
                  (and, ideally, how to fix MythTV to not break it),
                  we'll put that patch in...<br>
                  <br>
                </blockquote>
              </div>
              For anyone who has had a problem with 0.26 and 0.27
              lossles mpeg2 mythtranscode I think I figured out the
              problem and added a patch to <a moz-do-not-send="true"
                href="http://code.mythtv.org/trac/ticket/11213"
                target="_blank">http://code.mythtv.org/trac/ticket/11213</a>
              that should fix the problem.<span class="HOEnZb"><font
                  color="#888888"><br>
                  <br>
                  John</font></span>
              <div class="HOEnZb">
                <div class="h5"><br>
                </div>
              </div>
            </blockquote>
            <div><br>
            </div>
            <div>Thanks John,<br>
              <br>
            </div>
            <div>When this gets merged can someone please advise which
              version it's in?<br>
              <br>
            </div>
            <div>Cheers,<br>
              <br>
            </div>
            <div>Anthony <br>
            </div>
          </div>
          <br>
        </div>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
mythtv-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a>
<a class="moz-txt-link-freetext" href="http://www.mythtv.org/mailman/listinfo/mythtv-users">http://www.mythtv.org/mailman/listinfo/mythtv-users</a>
</pre>
    </blockquote>
    <br>
    I will be very thankful to have transcoding working again.&nbsp; However
    will this be a valid long term fix?&nbsp; It looks like
    avcodec_encode_video is deprecated and replaced by
    avcodec_encode_video2.&nbsp;&nbsp; Does more investigation have to be done
    into how to incorporate avcodec_encode_video2 correctly?<br>
    <br>
    John<br>
  </body>
</html>