<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"><<a href="mailto:finlay@moeraki.com" target="_blank">finlay@moeraki.com</a>></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. Just a bug that someone needs to figure out. 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 href="http://code.mythtv.org/trac/ticket/11213" target="_blank">http://code.mythtv.org/trac/<u></u>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>