[mythtv-users] Any setting in GUI to stop advert detection jobs?

[Tony Gould]

thanks all. I definitely want to try that wrapper posted by Thomas, as it
would be great to have advert detection working again. Just to clarify, I
have a combined FE/BE, so disabling advert detection on the BE was simply
leading to the queue filling up with jobs that were never executed. I think
rather than changing my rules, if I want to disable it, I will do it
channel by channel (by checking the "no ads on this channel" option).

On 23 December 2015 at 22:51, Hika van den Hoven <hikavdh at gmail.com> wrote:

> Hoi blind,
>
> Wednesday, December 23, 2015, 11:44:24 PM, you wrote:
>
> > On Tue, 22 Dec 2015 23:39:26 +0100
> > Hika van den Hoven <hikavdh at gmail.com> wrote:
>
> >> Hoi Tony,
> >>
> >> Tuesday, December 22, 2015, 11:17:22 PM, you wrote:
> >>
> >> > Ever since I upgraded to 0.27 (from something very old like 0.21),
> >> > the advert detection has stopped working (I'm in the UK). I'd like
> >> > to turn it off altogether as it's just running my system for no
> >> > reason. Last night I unchecked the setting which allows running
> >> > advert detection jobs, but the jobs were still spawned and my
> >> > backend sat there and didn't turn itself off as it usually does.
> >>
> >> > I'm aware I could go through and mark each channel as being advert
> >> > free (either manually or via SQL if I can figure out the table and
> >> > field name), but it would be nice if there was some way to simply
> >> > turn off commercial detection.
> >>
> >> > thanks!
> >>
> >> You have to turn it of in everyone of your rules. For new rules you
> >> turn it of in the template(s).
>
> > Stupid question:  How do you edit the template?
>
> On a frontend, the are in the rulelist. I don't think you can edit
> them in Mythweb.
>
> >> A short could be placing a dummy command in place of the regular
> >> commercial detection command.
>
> > Individual backends can be configured to not do any commercial
> > detection, or meta-data lookup, and other stuff.
>
> Yes and as I understood, that is what he did. Only that will not stop
> the tasks from being submitted, so if you disable it on all backends,
> your task list gets filled up with waiting tasks.
>
> > Feature request:  When a backend is configured to not do something
> > could the shut down procedure (mythshutdown --status or whatever
> > it is) not prevent a shut down because there are pending jobs
> > that that particular machine was never going to do anyway?
>
> > And where should I submit feature requests to?
>
>
>
>
>
> Tot mails,
>   Hika                            mailto:hikavdh at gmail.com
>
> "Zonder hoop kun je niet leven
> Zonder leven is er geen hoop
> Het eeuwige dilemma
> Zeker als je hoop moet vernietigen om te kunnen overleven!"
>
> De lerende Mens
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20151224/0249495a/attachment.html>