2010-09-29, 22:09
Quote:The overhead and absence of the file have stopped me from doing this. mythicalLibrarian basically reverts the file to it's original form and then runs it as new. Some people have a NAS setup where the file gets recorded locally and then gets transferred across the NAS. This can take up to 10 minutes each way. If every 1/2 hour the file is rerun, it takes 10 minutes one way and 10 minutes the other way. Then, on top of that, each file will be redone, so it might be that every 1/2 hour, 10 hours of work are added to the que.Code:Would it be possible to have the doover run every time mythicalLibrarian runs?
I, too, copy my recordings to a NAS drive. Would it be possible to rethink the --doover process? Could you process the doover files in place (in my case on the NAS), and thus making it feasible to run --doover every time mythicalLibrarian runs?
Quote:Yes. That's correct. Try a manual update. When running scan mode, mythicalLibrarian sends out sequential library update requests. For some reason the first one starts the update and the 2nd one stops it. It is a XBMC issue, but it should be fine after it gets onto a normal schedule of 1 recording at a time.
A manual update always works, but I would like it to be automatic. I don't quite follow what you are saying above. Are you saying that if two files are being processed at the same time, (i.e. two MythTV recordings finish at the same time), that the automatic update library will fail?