<div dir="ltr">On Mon, Nov 4, 2013 at 7:15 PM, mark <span dir="ltr"><<a href="mailto:perkins1724@hotmail.com" target="_blank">perkins1724@hotmail.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 02/11/13 02:31, John Finlay wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
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<br>
changed to still work with mythtv but to make post-processing of the<br>
losslessly transcoded file impossible. Even mythffmpeg can't process<br>
the cut files.<br>
</blockquote>
<br>
No, we had no intention of adding DRM/"lock in" to MythTV. Just a bug<br>
that someone needs to figure out. If someone can figure out what<br>
MythTV is breaking (and, ideally, how to fix MythTV to not break it),<br>
we'll put that patch in...<br>
<br>
</blockquote>
For anyone who has had a problem with 0.26 and 0.27 lossles mpeg2<br>
mythtranscode I think I figured out the problem and added a patch to<br>
<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.<br>
<br>
John<br>
</blockquote>
<br></div>
John, thank you greatly for your efforts they are much appreciated. I have applied the patch however have only tested on three files. All three worked successfully so very promising so far. Will continue to test as much as I can over the next week.<div class="HOEnZb">
<div class="h5"><br><br></div></div></blockquote><div>Ditto, thanks John! I applied the patch last Friday and have tested with multiple recordings including SD and HD (both 720p and 1080I), all worked successfully. </div>
</div></div></div>