New to Avisynth ? Read my Avisynth introduction here to help get you started
Here we go again!
A while back I wrote some custom scripts that explored the choreography of multiple video inputs using Avisynth. While the scripts worked, it has to be said that they were messy as my understanding of Avisynth scripting was that of a struggling novice. Now that I’ve learnt a little bit more I’ve attempted to clean up and simplify the scripts. I’ve also added some enhancements that were the result of some of the suggestions raised in this forum post . Namely these are adding an external soundtrack source, and creating scripts that allow a full screen zoom of a single video after the initial display of all nine videos (See Nines_06.avs thru to Nines_10.avs in the video examples above)
If all this sounds confusing so far and you are new to Avisynth , I would recommend reading my Avisynth introduction to help get you started
A zipped folder containing the scripts can be downloaded from elow, but in keeping with previous posts I have also made available a project folder containing all the scripts and example source media. It is a fully working example and intended for test purposes. Once a user is satisfied that the scripts work, they will need to replace the test media with that of their own
Note – I would advise unzipping the download in to an empty folder
The project folder contains 10 wmv videos of the type created in Windows Movie Maker. Nine of these are videos we wish to fly in and out of the screen while the tenth is a short texture loop video of just a few seconds long that will provide the background animation. A soundtrack mp3 is also included. Unless the scripts are altered it is important that the source media is named as follows:
01.wmv
02.wmv
03.wmv
04.wmv
05.wmv
06.wmv
07.wmv
08.wmv
09.wmv
texture.wmv
music.mp3
It is possible that source videos other than wmv’s may work depending on the codecs installed on a users system. Please be aware however that the name of these source videos should be reflected within the scripts if they differ. For example, if a video source called mymovieclip.avi is intended to be used as a replacement for 01.wmv, then01.wmv within the aviscript must be altered to become mymovieclip.avi . (Renaming "mymovieclip.avi" as "01.wmv" also seems to work as an alternative method to that of altering the script.)
The videos may be of any length and all will be either looped or trimmed to match the length of the centre video which is 01.wmv . In this respect 01.wmv acts as a control video and should also be considered the main feature video. The framerate of all the other videos will be converted if necessary to match that of 01.wmv . The resolution of the final project will match that of 01.wmv, so for good quality results ensure that 01.wmv is a high resolution clip.
The texture loop should only be a few seconds long and is set to loop within the scripts. More texture loops are available here
The mp3 soundtrack is set to be trimmed and faded within the scripts to match the length of the final video.
To get the most out of the scripts I would expect a user to alter and probably improve them to their own requirements. If deciding to alter the scripts I would recommend using AVSP as the scripts have been formatted to look neat and tidy within it. Displaying the scripts in something like notepad does not appear to preserve the tab information resulting in a messy look.
I have attempted to try and make certain key features of the project easy to alter within the scripts under the following headings within the scripts (I’ll leave it to the user to explore these)
SOURCE VIDEOS AND AUDIO SOUNDTRACK
USER DEFINED SETTINGS
Ultimately a user will need to go in at a much deeper level to make more exacting alterations. It can be tricky ! These scripts are really just intended as examples to show some of the things that are possible and to provide a small measure of quick customisation
EXPERIMENT AND HAVE FUN !
Notes – The scripts were tested on windows XP home edition with Avisynth version 2.57 installed. I’ve tested and rendered the scripts within Virtualdub-MPEG2 and NicsWM9 Encoder to good effect