They all work fine. Initially there were some teething problems, due to a bad installation of AviSynth, though that cause was not immediately apparent (meaning I spent hours experimenting and Googling before the moment of that realisation…). Versions installed:
- AviSynth 2.5.8 rev. 2
- AvsP 2.0.2
- Avs2Avi (Created 6 July 2004, size on disk 84 KB)
The main symptom of the teething problems: An AviSynth [.avs] script ran OK inside AvsP, to save to an AVI file, but before the dialog could ask me what codec, it failed with error message saying it could not open the source (.avs) file. At first, an AviSynth [.avs] script ran OK inside AvsP, but the following issues existed:
- From AvsP, tried to save to an AVI file, but before the dialog could ask me what codec, it failed with error message saying it could not open the source (.avs) file.
- Tried earlier versions of AvsP, v 2.0.1 and v1.4.0. These gave error messages saying that the source file could not be opened, and further that a Python object for the file in question was a null object.
- Error message: The Requested Operation Requires Elevation.
- Suggested the need for the program to be run with Administrator status.
- Traceback (most recent call last):
- File “AvsP.pyo”, line 1857, in OnIdle
- AttributeError: ‘NoneType’ object has no attribute ‘CanRead’
- No need for Python to be installed, AvsP (2.0.2) comes with its own copy of a library file for a compatible version of Python (python25.dll).
- Initially tried setting all three programs to Compatibility (Windows XP SP3) and also to Administrator mode.
- The former made no detectable difference.
- The latter stopped the error message.
- At that stage, the dialog appeared to work with no error message but no output file was created.
- Error message: The Requested Operation Requires Elevation.
- Tried earlier versions of AvsP, v 2.0.1 and v1.4.0. These gave error messages saying that the source file could not be opened, and further that a Python object for the file in question was a null object.
- Tried VirtualDub (latest version, 1.9.11).
- VirtualDub was initially unable to open the [.avs] file.
- This suggested that either VirtualDub or the “codec” (AviSynth) was not working properly, either in their own right or in the particular environment of my system (Windows 7 on MacBook Pro).
- Downloaded latest stable version of AviSynth (2.5.8 rev.2).
- Now VirtualDub could open the [.avs] file ok
- Tried AvsP again.
- Worked fine.
- Interestingly, one advice (from Feb 2011) was: <<use VirtualDub via commandline instead of avs2avi>>, as that <<consists of very old VirtualDub’s codes.>>
- Can use VirtualDub from its GUI also.