2017-02-27, 01:42 PM
Would you consider adding an option for NScriptHelper.exe that would return the number of currently active recordings?
With pre- and post-padding overlap (primarily on hour show changeover times), I'm semi-frequently seeing 6+ recordings going on simultaneously. When you add in 1 playback stream and 1 or 2 comskip batches, it seems that the main recording drive is sometimes being overwhelmed. I already throttle the comskip processing to limit it to 2 concurrent processes all the time. But I was thinking that possibly limiting it to 1 (or 0) when the number of active recordings is above a certain count might help. Making that change to my script would be fairly easy if NScripthelper.exe could return the current active recording count.
With pre- and post-padding overlap (primarily on hour show changeover times), I'm semi-frequently seeing 6+ recordings going on simultaneously. When you add in 1 playback stream and 1 or 2 comskip batches, it seems that the main recording drive is sometimes being overwhelmed. I already throttle the comskip processing to limit it to 2 concurrent processes all the time. But I was thinking that possibly limiting it to 1 (or 0) when the number of active recordings is above a certain count might help. Making that change to my script would be fairly easy if NScripthelper.exe could return the current active recording count.
However, I'm seeing that when shows end at the same time, with channel numbers that are close to each other, then more than one instance of comskip that be started by the script before the script checks again to see if comskip is already running. When multiple instances of comskip are running full speed ahead they can overwhelm the disk subsystem.