<div dir="ltr">On Fri, Nov 1, 2013 at 12:01 PM, John Finlay <span dir="ltr"><<a href="mailto:finlay@moeraki.com" target="_blank">finlay@moeraki.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote">
<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><br></font></span></blockquote><div>Before I try my hand at compiling a new mythtranscode I want to make sure I am doing the right thing. You posted two different patches in ticket #11213 but the last one mpeg2fix.cpp.patch20131031 appears to be fix... or are both patches needed??</div>
<div><br></div><div>Mike </div></div></div></div>