I'm loading an avisynth script into vdubmod by command line (batch file) and specifying the .jobs file to run on it. Everytime I do this it comes up with a parse error in vdubmod but when I click ok it continues normally. Any ideas why it may do this? I'd not mind it but the reason for doing the batch file and scripts is to be able to do multiple conversion processes unattended and that's not possible if I have to be around to click ok everytime that parse error pops up._X_X_X_X_X_[small]---------------- How am I? I'm still alive... damn the luck![/small]
Duuuhhh!@!@!@!@!@!@!@! I hate it when I answer my own question. The problem was that in my batch file command line I was specifying the script file for Vdubmod to open and the .jobs file to execute on it. However, the .jobs file also had the script name in it and was complaining about trying to open two of them.
