skipping fouled up again

[johnsonx42]

I wouldn't assume that your working directory is the scripts directory... yes, that's where the script is called from, but that may not be where it's running. That's why my example postprocessing.bat (which is what I still use, though I'm back to running it parallel) begins with a cd command. Even if you put everything in scripts, then start with 'cd \users\public\npvr\scripts'.

[mvallevand]

The first line of my c:\users\public\npvr\scripts\PostProcessing.bat file

Code:

echo Postprocessing.bat invoked on %1 recorded from channel %2 >>postprocessing.log

I have PostProcessing.bat and comskip files in c:\users\public\npvr\scripts. I do not have a postprocessing.log file, which means PostProcessing.bat isn't getting called.

To elaborate on what johnsonx42 said ">> postprocessing.log" would be in the default directory, so you aren't necessarily looking at the right location.

You also should include logs, they show whether the bat file is found and whether it exits.

Martin

[johnsonx42]

yep, what martin said completes my explanation.

the alternative is to use full pathnames for every single file, every time. that's very prone to errors though, far easier to just start with a CD command.

[Wakalaka]

the cd command fixed my problem. i should have copy/pasted your batch file, but instead did a visual compare and missed what was staring at me. thanks for the kick!