[mythtvnz] Commercial detection

[Nick Rout]

On Sat, Jan 16, 2010 at 11:39 AM, Steve Hodge <stevehodge at gmail.com> wrote:
> On Sat, Jan 16, 2010 at 9:10 AM, Tortise <tortise at paradise.net.nz> wrote:
>>
>> How long will it take in
>> reality to get DVB-T comm detection working as well as mpeg2?  What's
>> strange about that?

Tortise: I assume you are referring to the difference between h264 and
mpeg2, nothing to do with the delivery mechanism (dvb-t)

>
> Does the video format/container make any difference for commercial
> detection? I thought detection was all content-based.
>

yes its looking at the frames to see what is /isn't there

> I think commercial detection worked better for me in 0.21 than 0.22, but I
> haven't played with the options to try to figure out what works the best
> with 0.22.
>

Having started with a fairly low end BE/FE combo I turned comm
detection off as it used too many resources.

Now I have a separate frontend I may turn it on again. However for the
few recordings I have commflagged, it worked well. This was mpeg2
files on 0.21. I commflagged a couple for a demo at clug.

http://www.mythtv.org/wiki/Commflagging and
http://www.mythtv.org/wiki/Commflagging_in_the_UK have good info,
including on the latter page some alternative commflaggers to try.