Crop fails on manual use of Detect Adverts

[paultry]

No, what happened is the backup copy of the original uncropped file failed to be created as expected, so the process took the least risky option and aborted. Under normal circumstances this wouldn't happen, but the invisibility of error messages definitely doesn't help.


Not standard, but the result of meddling fingers while you were exploring. An edge case.


No need, it will happen any time you try to re-run a crop without tidying up from the previous run properly.

Given circumstances already stated, not knowing that file in _original from a decrypt process has to be deleted before a separate crop process is run isn't reasonably characterised as "meddling fingers", and to call running a separate crop process as an "edge case" is also unrepresentative. Please, moderate your tone.

 

[paultry]

Is anything shown in webif-error.log (viewable via the diagnostics page) following a crop attempt?

As an experiment try a Detectads run with cropping within detectads and see if that runs (can specify -crop y -debug 2 in "Process options" if you don't want to change the global setting)

I did check in webif-error.log previously, but IIRC it was empty. When I run your experiment (specifying -crop y -debug 2 in "Process options), without deleting the copy in _original created by the decrypt process, it does work. The cropping process results in 2 files in media/My Videos. One is the file including bookmarks, and the other is cropped.

So different result when running crop separately to running with detectads.

 

[Black Hole]

Please, moderate your tone.

That was moderate!

If you're that touchy, goodbye.

 

[paultry]

That was moderate!

If you're that touchy, goodbye.

Not touchy, discerning. Unlike you Brian.