<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Sun, Oct 27, 2013 at 2:32 AM, 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 27 October 2013 19:54, John Pilkington <<a href="mailto:J.Pilk@tesco.net">J.Pilk@tesco.net</a>> wrote:<br>
<br>
> OK, thanks for that. This looks as if it's a special situation, although<br>
> probably easy to reproduce, or encounter by chance. I doubt that it's worth<br>
> making a full-time switch back to ffmpeg but the workaround could be useful.<br>
<br>
</div>my plan for 0.28 is to update the FFmpeg original mpegts demuxer to<br>
support the features (mostly subtitles) mythtv's own demuxer supports.<br>
<br>
When that happen; there will be no need for using special switch<br></blockquote></div><br></div><div class="gmail_extra">Does that switch work with mythbackend as well? Could it make the commercial flagger work as well as it did in 0.24? I know ffmpeg has active development, but it seems that all they do is break stuff (APIs, command line arguments, formerly working features, etc.)<br>
<br>Karl<br></div></div>