[mythtvnz] reasonably effective commercial detection silence.preset for NZ?

[Nick Rout]

Silence detection is not CPU intensive as it involves no video decoding.

On Mon, May 7, 2018 at 2:59 PM, James Walker <james.walker.nz at me.com> wrote:

> The tooling I have setup is per this wiki page:
> https://www.mythtv.org/wiki/Commercial_detection_with_silences
>
> The processing seems to be reasonably light weight and pretty fast. I do
> have a quad core backend master sever that just shrugs when 2 such jobs are
> processing.  However on older kit I can see how it might be more pushed.
>
> As to effectiveness - the wiki page “advertises” it as working/workable in
> NZ, hence my question to the community.  However having analysed some of
> the shows on various channels I can see how tough it will be to get
> consistent “okay” results. The methods for fading between shows and
> commercials are all over the place.
>
> I’ve been using the skip facilities for years so no issue returning to
> that.  I was just hoping to achieve some processing magic  :-)
>
> Cheers,
> James.
>
> On 7/05/2018, at 2:46 PM, Karl <skooobie at gmail.com> wrote:
>
> Yep. The commercial detection is very processed hungry. And as Stephen
> mentions as we have skip ability (which we can fine tune too) then no real
> need anyway.
>
> On Mon, 7 May 2018, 14:17 Stephen Worthington, <stephen_agent at jsw.gen.nz>
> wrote:
>
>> On Mon, 7 May 2018 08:35:23 +1200, you wrote:
>>
>> >On 06/05/18 20:16, Stephen Worthington wrote:
>> >> I have
>> >> just given up and turned it off so as not to waste all the CPU cycles
>> >> and electricity it was using, as it never worked.
>> >Where do you turn it off?
>>
>> Mythtv-setup > General > Job Queue (Backend-Specific) > Allow advert
>> detection jobs
>>
>> MariaDB [mythconverg]> select * from settings where
>> value='JobAllowCommFlag';
>> +------------------+------+----------+
>> | value            | data | hostname |
>> +------------------+------+----------+
>> | JobAllowCommFlag | 0    | mypvr    |
>> +------------------+------+----------+
>> 1 row in set (0.00 sec)
>>
>> I also changed my recording templates to turn off the option in there
>> that creates the mythcommflag job, and used SQL to do the same in all
>> my recording rules.
>>
>> _______________________________________________
>> mythtvnz mailing list
>> mythtvnz at lists.ourshack.com
>> https://lists.ourshack.com/mailman/listinfo/mythtvnz
>> Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/
>>
> _______________________________________________
> mythtvnz mailing list
> mythtvnz at lists.ourshack.com
> https://lists.ourshack.com/mailman/listinfo/mythtvnz
> Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/
>
>
>
> _______________________________________________
> mythtvnz mailing list
> mythtvnz at lists.ourshack.com
> https://lists.ourshack.com/mailman/listinfo/mythtvnz
> Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ourshack.com/pipermail/mythtvnz/attachments/20180507/0c37d9f1/attachment.html>