Trev
The Dumb One
Not true, at least Ian_j and I have had it. I have had it several times, although the recording has been decrypted when I look at them.only one user has reported decryption problems since
Not true, at least Ian_j and I have had it. I have had it several times, although the recording has been decrypted when I look at them.only one user has reported decryption problems since
There are two variations of auto processing:
The problem seems to be related to the DLNA indexer and it is difficult to predict when that will run, it varies from a few seconds to hours and even when indexed it is not clear when the index is safe to use.
- Autotrigger - processes a single recording and is triggered by end of recording so will always start within seconds of the the recording finishing
- Auto - runs on a timed basis at 5, 25, 45 minutes past the hour (can be adjusted by editing chrontabs) and processes all recording that autotrigger failed to handle
Using a link and the DLNA helper (as suggested by BH in post #10) seems to have reduced the problem for detectads, only one user has reported decryption problems since I introduced the change but retrying laterbworks for Auto so perhaps the easiest fix is just to remove the alert message and only generate the log message.
Note I was referring to Decryption length error messages issued by DetectaAds chaserun processingwhich resulted in -Len Err files being created, I know Trev and others suffered from these in the past but I have only seen one report of a DetectAds related decryption problem since I made the changes a few weeks ago.Not true, at least Ian_j and I have had it. I have had it several times, although the recording has been decrypted when I look at them.
That is a lot more than other users have reported, can you post the auto.logI regularly get auto-decrypt-failed notifications, and currently have 8 listed in my pending system notifications.
My latest batch of auto-decrypt-failed notifications date from 18/12/2015 - 22/12/2015, and my auto.log does not cover this period.That is a lot more than other users have reported, can you post the auto.log
I've had this message for every recording of Britain on Film, 5 so far. On every occasion the episode has been decrypted fine when I've checked it.
View attachment 2452