<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On 29 October 2013 12:48, Jean-Yves Avenard <span dir="ltr"><<a href="mailto:jyavenard@gmail.com" target="_blank">jyavenard@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 28 October 2013 23:01, Anthony Giggins <<a href="mailto:seven@seven.dorksville.net">seven@seven.dorksville.net</a>> wrote:<br>
<br>
> Sounds like this will also resolve the lossless transcoding issues also?<br>
><br>
<br>
</div>can't see why it would...<br>
<br>
the aim is mostly to enjoy all the bug fixes brought by ffmpeg's<br>
mpegts demuxer: its development is much more active than ours. And<br>
there's been a few reports lately of files not playing with myth's<br>
mpegts code; but working with ffmpeg's own<br>
<div class="HOEnZb"><div class="h5"><br></div></div></blockquote><div><br></div><div>Wouldn't mythtranscode share the same demuxer code? </div></div></div><div class="gmail_extra"><br></div><div class="gmail_extra">Anthony<br>
</div></div>