<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/1/2013 1:53 PM, Michael Stucky
wrote:<br>
</div>
<blockquote
cite="mid:CAMN+uBU2P85tzTvzC0gdV9c3KcruSqLyjLojQGbWKFtdQCKTRg@mail.gmail.com"
type="cite">
<div dir="ltr">On Fri, Nov 1, 2013 at 12:01 PM, John Finlay <span
dir="ltr"><<a moz-do-not-send="true"
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 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>
<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>
<br>
</div>
</div>
</div>
</blockquote>
The latest patch supersedes the earlier patch - it's the one labeled
mpeg2fix.cpp.patch20131031. I couldn't see a way to indicate that
the older patch was superseded.<br>
<br>
John<br>
</body>
</html>