<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Tue, Dec 24, 2013 at 7:56 AM, Brian J. Murrell <span dir="ltr"><<a href="mailto:brian@interlinx.bc.ca" target="_blank">brian@interlinx.bc.ca</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="im">On Tue, 2013-12-24 at 10:24 -0500, Daryl McDonald wrote:<br>
><br>
> The STB is a cable company supplied "motorola DCT700" into a PVR-150<br>
<br>
</div>Which is why this works so well. This is that same known quantity that<br>
I was talking about in my posting that mythcommflag (ffmpeg really)<br>
knows how to deal with really well.<br>
<br>
So your experience is in fact adding support to my theory (which in and<br>
of itself might be preaching to the choir) about the content of already<br>
encoded streams fouling up mythcommflag.<br>
<br>
Cheers,<br>
b.<br></blockquote><div><br></div><div>Sorry to bust your theory, Brian... ;-) Daryl actually said that the recordings from the PVR-150 were the ones that were ~40%ish. Which matches with my experience--I've been using the PVR-500 as long as I've had myth and the thing which changed and broke commflagging for me (I'd guess I'm also at about the 40%ish mark) was the version change from 0.24 to 0.25. At one point, I'd guess around mythtv version 0.22, Comcast switched to all digital and I had to start using set top boxes, but commflagging still worked great for me after that transition. However, I'd agree that it's most likely due to changes in ffmpeg. Possibly the changes made to accommodate the new encodings from OTA, QAM and CableCard made things worse for the PVR-XXX encoding.<br>
<br>Karl<br></div></div></div></div>