Quote:
Originally Posted by
Ken.F 
If there is I haven't found it.
Under the "File Watcher" tab do you have "Automatic Cleanup" checked? If so what number is entered on the line for "Cleanup Frequency"?
Yes, I have Automatic Cleanup checked and the number entered on the line for Cleanup Frequency is '7'...
Quote:
Originally Posted by
babgvant
The FW works in a couple ways:
1) detecting new/changed files
2) looking for files w/o artifacts (xml/edl)
If your process changes files in the watched directory the FW will process them again. You can use PC (processing conditions) to determine which profile is executed.
I'm using the profile attached to this thread in an earlier post unmodified. It creates a .dvr-ms file in a temp directory from the .wtv file, processes it with comskip and then deletes the .dvr-ms file. The .wtv file is left untouched, so I'm not sure why it would try to process it again, but it is...continuously.
HOWEVER, I think I may be on to something. For whatever reason a day after I made this post, it suddenly stopped processing every file continuously..only some of them. From what I may have found of those, is a pattern of sorts. It looks like most of them end one processing session in the log with:
Code:
Running comskip this may take a while.
Run C:\\Program Files\\DVRMSToolbox\\Applications\\comskip.exe "C:\\TVScanFolder\\Shane Untamed_NGWILD_2011_07_25_01_57_00.dvr-ms" "C:\\Users\\Public\\DvrmsToolbox\\CommercialsXml"
Finished Commercial Detectection
No commercials found
Action did not complete successfully
Total Duration = 00:43:32.8310291
PW Exit: System.InvalidOperationException: No process is associated with this object.
at System.Diagnostics.Process.EnsureState(State state)
at System.Diagnostics.Process.get_HasExited()
at System.Diagnostics.Process.EnsureState(State state)
at System.Diagnostics.Process.get_ExitCode()
at Durrant.DVRMSFileWatcher.ProcessWrap.ap_Exited(Object sender, EventArgs e)
I see a 'Action did not complete successfully' which is followed by an exception. Then shortly thereafter in the log is another set of 'Start Process: ' where is processes it again, and again, and again.
Not sure why it didn't find commercials in this file, but in any case that still shouldn't be the cause of an "Action did not complete successfully". But would this action cause it to be processed again?
Thanks,
