ScriptWriter 1.5
7/13/2006
Jacob Klint (jklint@juno.com)

ScriptWriter is a tool that aids with Avisynth and Virtualdub 
script creation.  It is designed for batch processing of large
numbers of source video files.

new in version 1.5:
specify filename/extension filters for selective processing of files
w/i a folder

uses user's application data folder for settings

settings stored in xml rather than INI format


Usage:
1.	Create templates.  

	For avisynth, this means taking a
	script you would like to use and replacing the source 
	file with the string "%f" (no quotes). 

	(If you happen to already use the tool Asynther to automate 
	Avisynth script creation, you might notice that this is the 
	exact same format that ASynther uses, so Asynther scripts (*.avst) will
	work correctly with ScriptWriter.  The only exception
	is that the "multiple file" notation has not been
	implemented, so don't use it!  It's not necessary
	for ScriptWriter anyways.)

	For virtualdub, a standard VCF file is all that is necessary.
	Just make your settings in Virtualdub and save them to a file
	("File->Save Processing Settings").  That's it!

2.	Fill in the blanks.

	All fields in both the main window and the options window must be
	filled in.  The fields "avs template suffix" and "vdub suffix" are
	strings that will be appended to their respective output files
	(see #3 below).

3.	Click "Go!".

	If the Avisynth box is checked, then for each file in the source file
	directory, ScriptWriter will insert its name in the avisynth template
	and create a new avisynth template named "%filename%%suffix".For example, 
	a file named "test.avi" with a suffix of " - avisynth.avs" would create 
	a script named "test.avi - avisynth.avs".

	If the Virtualdub box is checked, a couple things could happen.	If avisynth 			
	scripts have also been created, then for each created script, ScriptWriter 
	will enter its name in a job file for virtualdub along with the
	settings specified in the virtual VCF file.  At the end you will have
	one massive ".jobs" file containing all the jobs.  The process will then 
	repeat but the original source files will be used instead and the resulting
	jobs will be placed in a new ".jobs" file.  In the end, two virtualdub job
	files will exist.

	In the case that avisynth scripts were not created, only the second virtualdub
	job file will be created.



That's it!  This is a pretty flexible tool.  I use it take DV clips from my camcorder,
run them through a custom Avisynth template, then create one job file to compress/process
them further in virtualdub.  Note that you have the option of just creating virtualdub 
or avisynth files, so you don't always have to chain them together in this manner.

Other little things: 
- ScriptWriter is written in C#, so it requires the .NET framework

- drag and drop is enabled for all file/directory fields

- All input is checked for errors before processing, so nonsensical/non-existent files, 		
	directories, etc will be caught.  

- Both the avisynth and virtualdub suffixes must be filled in, blank suffixes are 
	not allowed.

- Scripts will not be automatically overwritten if you rerun the program with the same 		
	settings; you will be prompted instead to make a decision

- The file "vdub job template.txt" is used to create the virtualdub jobs file.  You can alter
	this file if for some reason you need to change how the jobs file is formatted.  However,
	to change actual video processing settings, instead save the settings in virtualdub
	as a VCF file and set ScriptWriter to use that in the options dialog