Detect Ads no longer running

ribrob

Member
I'm not sure whether this is related to a recent update of Detect Ads, or a system crash result in it being disabled, but it's not longer running for me.

This rule was working fine for months...

Screen Shot 2016-12-30 at 22.50.24.png

...but now nothing.

Running a test of the rules set i get this...

Screen Shot 2016-12-30 at 22.50.15.png

And there's nothing in the queue pending...

Screen Shot 2016-12-30 at 22.54.08.png

Any idea what's gone awry and how to get it running automatically again?

Thanks in advance.

Rob
 
The output says that the job is already queued. Detectads uses its own queue, click on OPT+ next to any recording and choose 'Detect Adverts'. The next screen should show you the contents of the detectads queue.
 
DetectAds doesn't (yet) use the new system queueing mechanism so wont show on that queue view.

Check the DetectAds log on the diagnostic page to see when it last ran and if there are any signs of problems.
 
Looking at the logs i see the below.

The logs start mentioning "Content Sharing Disabled" - at the point the ads are no longer being removed.

Is it related?

Rob


321 13/11/2016 17:15:48 DA(3109)- DETECTADS: /media/My Video/- Process/Rango_20161113_1444.ts
322 13/11/2016 17:16:36 DA(3109)- ad break found 0:00-0:21 (0 - 21)
323 13/11/2016 17:26:45 DA(3109)- ad break found 24:11-28:47 (1451 - 1727)
324 13/11/2016 17:33:20 DA(3109)- ad break found 42:32-47:08 (2552 - 2828)
325 13/11/2016 17:42:21 DA(3109)- ad break found 68:28-73:04 (4108 - 4384)
326 13/11/2016 17:52:40 DA(3109)- ad break found 96:22-100:21 (5782 - 6021)
327 13/11/2016 18:01:57 DA(3109)- ad break found 120:44-127:01 (7244 - 7621)
328 13/11/2016 18:01:57 DA(3109)- Final bookmarks: 21 1451 1727 2552 2828 4108 4384 5782 6021 7244 7621
329 13/11/2016 18:01:57 DA(3109)- ad detection.processed in 2769.038s 00:46:09 - 6 ad breaks bookmarked, crop starting
330 13/11/2016 18:08:43 DA(3109)- done...processed in 3175.31s 00:52:55 - 6 ad breaks cropped out
331 20/12/2016 15:25:06 DA(2869)- DETECTADS: Queued /media/My Video/- Process/Rise of the Guardians_20161220_1345.ts for advert detection, Qid 233
332 20/12/2016 15:25:06 DA(2871)- ==DETECTADS Chase Run: /media/My Video/- Process/Rise of the Guardians_20161220_1345.ts
333 20/12/2016 15:25:06 DA(2871)- Content Sharing Disabled
334 Content Sharing Disabled -cannot decrypt files
335 20/12/2016 15:28:01 DA(3557)- ==DETECTADS Chase Run: /media/My Video/- Process/Rise of the Guardians_20161220_1345.ts
336 20/12/2016 15:28:01 DA(3557)- Content Sharing Disabled
337 20/12/2016 15:48:01 DA(6921)- ==DETECTADS Chase Run: /media/My Video/- Process/Rise of the Guardians_20161220_1345.ts
338 20/12/2016 15:48:01 DA(6921)- Content Sharing Disabled
339 20/12/2016 16:08:02 DA(10251)- ==DETECTADS Chase Run: /media/My Video/- Process/Rise of the Guardians_20161220_1345.ts
340 20/12/2016 16:08:02 DA(10251)- Content Sharing Disabled
 
Menu>Settings>System>Internet Setting>Content Share = on. If content share is switched off, Detectads cannot function as it uses the DLNA server (enabled by turning on content share) to decrypt on the fly.
 
Ah - that'll be it then! No idea why that setting's changed itself though.

Thanks for the help!
 
It can, and does, switch itself off from time to time. Just one of those things one needs to be aware of. Have you done a factory reset - that definitely switches it off, and one has to set a few things up again that are not immediately obvious.
 
Have you done a factory reset - that definitely switches it off, and one has to set a few things up again that are not immediately obvious.
Is there a handy list of what gets switched off and how it might affect the CF somewhere BH?
 
I've been contemplating running one up, but I need to clear a few things off my deck first. It came to my attention recently.

Incidentally, two of my boxes are reporting auto-decrypt failure - I've not looked into it, but it "feels" like one of the package updates has broken it.
 
If your install poweron-channel then, in Diagnostics, File Editor you can update /mod/boot/pox. There is an option to ensure the DLNA server is on (turned on) at each start up.
 
If your install poweron-channel then, in Diagnostics, File Editor you can update /mod/boot/pox. There is an option to ensure the DLNA server is on (turned on) at each start up.
This really should be the default or at least modifiable via the POC settings page rather than the obscure route of the Diagnostics file editor
 
Perhaps content sharing has switched itself off:rolling:
No, I've checked (and I would have been surprised if the same thing happened on two machines simultaneously).

I don't have time to run any more investigation at the moment, it will just have to wait.
 
Back
Top