@fecaleagle said:
Adding additional arguments (channel + title) to the post-process script call was mentioned in the link provided above. I would be satisfied with this as an alternative to a per-channel comskip.ini.
If you’re taking requests on the exposed post-processing arguments, the destination path would be a good one as well. Since post-processing will only pass the original file to the destination path, I’ve been using an inotifywait script to do my post-processing (I don’t prefer my MKVs to have the .ts extension). This allows the file to end up in the destination folder before processing occurs. It also gives me the ability to flag a file for later processing (something I don’t actually utilize but could). If post-processing could expose customizable arguments (a la qbitt******'s implementation), I could do everything I need in post-processing and avoid doing it the hard way.
Here’s a screen-grab of the sort of implementation I’m talking about (with the t-word redacted):
Edit: This could obviously be done without compromising existing post-processing scripts by treating scripts without recognized parameters as they’ve always been treated, i.e., appending the simple grab file path as an argument.
