[mythtv] "ClassicComm" detector vs "Comm2" detector
Eduard Huguet
eduardhc at gmail.com
Wed Nov 5 12:10:01 UTC 2008
>
> ---------- Missatge reenviat ----------
> From: "Peter Martens" <petermartens.list at gmail.com>
> To: "Development of mythtv" <mythtv-dev at mythtv.org>
> Date: Tue, 4 Nov 2008 20:56:30 +0100
> Subject: Re: [mythtv] "ClassicComm" detector vs "Comm2" detector
> > CommDetect2 is
> > such an alternative, written by
> > Robert Tsai. I think it worked quite okay for him. Your millage may
> > vary wildly depending on the kind
> > of channel you are commflagging.
> >
> I expect you are lining in the Netherlands?
> How is commflagging working for you? I suppose commercial breaks are
> too long over here (NL) to get detected well. Most of th time there is
> 1,5 min. commercial at the end that doesn't get detected. Many years
> ago I worked much better. What about you?
>
> Peter
>
Hi,
By looking at the code inside ClassicCommDetector.cpp I found an
(apparently) undocumented setting, "CommDetectMaxCommBreakLength", with a
default value of 395s (6 min and a half). As this matched the maximum skip
jump I as observing, I set this value to 900 (15 min) and commercial
skipping is working realy finer now... :D
I still haven't tried CommDetector2, but I didn't found any "maximum skip"
setting for it, so probably for this reason it's working better for you than
classical.
Best regards,
Eduard
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mythtv.org/pipermail/mythtv-dev/attachments/20081105/2d589cc9/attachment.htm
More information about the mythtv-dev
mailing list