[mythtv-users] 0.26 commercial flagging issue, or network issue?

[Mike Perkins]

On 10/01/13 15:32, Mark Goldberg wrote:
> On Wed, Jan 9, 2013 jppoet wrote:
>
>> the version of ffmpeg that ships with 0.26 is rather intolerant of
>> damage in the video. Especially on one channel, I had a lot of
>> mythcommflag failures with status 140.
>
> I believe this is the case. I also convert recorded shows to a smaller
> format version using the ffmpeg in F17 and they complain of numerous
> encoding errors, but never fail, while comflagging fails on many shows.
>
>> The latest development version of myth bundles a new version of ffmpeg
>> which is MUCH better, and I have not had a single mythcommflag failure
>> with it. Note that by definition, the latest *development* version is
>> a moving target, and my not be bug free.
>>
>> Before anyone asks, it is *extremely* unlikely Myth 0.26 will be
>> repackaged with the new version of ffmpeg. Stock ffmpeg is missing a
>> lot of features that Myth needs, and modifying ffmpeg to work with a
>> given version of Myth requires a substantial amount of effort.
>
> I hope that is not the decision made. In my case, there are two channels
> that virtually always fail comflagging. These are the same channels that
> gave VDPAU problems and appear to come from an MPEG encoder
> that produces errors. They modified VDPAU to hide the errors as the
> TV stations will not modify their encoders.
>
> It is not an option to go to the development version in a production
> environment.
>
One answer might be to run a 'pre-clean' pass with something like Projectx as 
part of your comflagging/transcoding script. I believe that Projectx is more 
capable of handling stream errors and will produce a clean output you can then 
run through comflagging.

-- 

Mike Perkins