<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Fri, Nov 1, 2013 at 1:16 PM, Michael T. Dean <span dir="ltr"><<a href="mailto:mtdean@thirdcontact.com" target="_blank">mtdean@thirdcontact.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 11/01/2013 12:01 PM, John Finlay wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
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.<br>
</blockquote>
<br></div>
Nice. (Especially how you tracked down the relevant change, which will make the patch/report much easier to review.)<br>
<br>
And while people wait for the fix, they (in the US) might want to look at:<br>
<br>
<a href="http://www.newegg.com/Product/Product.aspx?Item=N82E16822149396" target="_blank">http://www.newegg.com/Product/Product.aspx?Item=N82E16822149396</a></blockquote><div><br></div><div>just curious...how long does it usually take for a patch to be reviewed and make its way into the -fixes updates?<br>
<br></div><div>Thanks. <br></div></div></div></div>