<br><br><div class="gmail_quote">On Tue, Dec 18, 2012 at 10:11 AM, Ian Evans <span dir="ltr"><<a href="mailto:dheianevans@gmail.com" target="_blank">dheianevans@gmail.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 Tue, Dec 18, 2012 at 8:48 AM, Ronald Frazier <<a href="mailto:ron@ronfrazier.net">ron@ronfrazier.net</a>> wrote:<br>
> On Mon, Dec 17, 2012 at 10:51 PM, Ian Evans <<a href="mailto:dheianevans@gmail.com">dheianevans@gmail.com</a>> wrote:<br>
>> Just wondering what's happening with Myth's internal lossless<br>
>> transcode. ...how did mythtranscode going from 100% solid to a<br>
>> 100% failure for many of us?<br>
><br>
> No idea, but after someone else posted here about the 0.25<br>
> mythtranscode working fine with 0.26, I reinstalled it (by downloading<br>
> 0.25 source, recompiling, and then manually copying over mythtranscode<br>
> and the necessary libraries), and it's been working like a charm for<br>
> me.<br>
<br>
</div>Yeah, I've heard that too and have done it as well, but it's a pain to<br>
remember to replace it each time I do security updates on my system.<br>
Not knowing the development process I'm just curious how, if the old<br>
one works, it's not tossed back into .26? Why is there still a broken<br>
component in .26?<br>
<br>
Kevin, I'm not on master, but are you saying that it could be external<br>
ffmpeg code? Should I be updating my ffmpeg and see if that fixes the<br>
issue?<br></blockquote><div><br></div><div>Myth incorporates ffmpeg into it's code at certain intervals. You would need to update Myth to a version that has a fixed ffmpeg (assuming the problem is in the ffmpeg code). Master has a more recent ffmpeg library incorporated than 0.26 does. It's possible that what you're experiencing is fixed as a result. If not, then at least you've added the data point to the discussion that the issue still exists in master.</div>
</div>