Can you try build 0.81.041?
Ok, I can confirm .ts live detection works alright. Reason for it ended early for me before, was due to lack of understanding how Comskip performs live detection. Comskip seem to use a static interval schedule. I don't know if it's Comskip or Dirmon2 who makes it static. The pattern for live processing are as follows if using Dirmon2 filewatcher.
- First processing interval occurs about 5 minutes after recording starts
- Second processing interval occurs about 10 minutes after the first interval.
- Third to what ever processing interval needed for the actual show occurs every 10 minutes.
Lets say if having a show with 30 minutes of duration:
Live processing Step 1 - 5 minutes into the show
Live processing Step 2 - 15 minutes into the show
Live processing Step 3 - 25 minutes into the show
Live processing Step 4 - should occur after 35 minutes, but by then the recording has ended.
Now, in my case I have a script launched by an after recording task which automatically moves the .txt and .log file for the recording into a subfolder. In Dirmon2 I was using the .txt and .log files as triggers only. So if moving the only triggers, Step 4 will not get executed. Hence the Comskip output never gets finalized. If not moving the trigger files Comskip output gets finalized alright 5 minutes after recording finishes.
All along I did expect Comskip was abled to sense when the recording finishes, but it's obviously not so. Comskip sticks persistently with the static interval schedule. When thinking of it, it was kind of naive believing Comskip could be that smart. That would require some interaction with the PVR system extracting duration parameters for recordings, which is nothing other than wishful thinking if you wanna have a tool working for 50 different PVR systems.
Well, as a defence speech this is the first time using a filewatcher and live detection also for that matter
Takes some time to grasp everything
Thankfully it will get easier when my PVR system recording timers supports file/script launching when recording starts. In that way one can retrieve placeholders/paramaters instantly and use them when calling Comskip, making filewatchers obsolete entirely.
All in all thanks for a work well done erik