In Avisynth, is there situations when the order of the functions matter? I believe the "LoadPlugin" function has to always come first, if you are using it, but are there other situations where "order matters"?
The reason I ask is because I wrote a Avisynth Batch Scripting front-end a few years ago (the more I post here the bigger it gets) for personal use. I would like to add it to my TShed Project, which will be shared with the community as soon as Sourceforge approves it. It will have to be heavily modified as it was really only made for one person.
I want to keep some of the GUI options (colorspace, crop, border etc etc) currently on the form but I want to add kind of a freehand window so you can modify the script. So I was trying to find out if order really matters when calling some of the functions.
Also, when I say "Avisynth Batch Scripting", think of this example (which is almost always the case for me):
1) You have 20 files.
2) Most of the files are uniform (same size, width, codec etc etc)
3) You want to quickly shoot out Avisynth scripts for them
I use my personal to create them. Right now, all the files have to have the same attributes, but the modified version will allow them to be different. Right now I am just exploring the idea as it seems like it could get a little too complicated and there may be something out there similar to this already, but it would be a challenge.
FYI, below is a screen shot of what it looks like now. I am sure it is extremely limited for most of the advanced users here, but with a little help that can be changed.
![]()
+ Reply to Thread
Results 1 to 2 of 2
-
-
Originally Posted by Maikeru-sama
They don't have to be at the top of the file, but it's customary to put them all together at the head.
(Though I have all mine autoload so I don't need to bother in the scripts, people say if you have dozens of plugins loaded it will slow it down, and there may be conflicts. But so far it's okay for me.)
You should do denoising before you do sharpening, for instance.
And normally resize after that.
NB: In your screenshot, "Add Boarders" should be "Add Borders".
Mostly I use FitCD to get a script started and edit in Ultraedit. (It has an Avisynth mode and I can add macros for the functions I use.)
If I'm trying out filters and adjusting parameters, I use AvsP.
When I have a batch of similar files I just copy the AVS files and use Ultraedit to change the AviSource lines.
Similar Threads
-
Avisynth batch scripter run-time error 380
By dude112 in forum Video ConversionReplies: 4Last Post: 13th Oct 2010, 12:13 -
Batch Test AVISynth (avs) files
By tevert in forum Video ConversionReplies: 9Last Post: 2nd Apr 2010, 10:38 -
A few ideas for a Video Editor for AVIsynth Scripting
By vhelp in forum EditingReplies: 4Last Post: 2nd Jan 2009, 23:47 -
Avisynth Batch Scripter
By stevenca in forum EditingReplies: 0Last Post: 7th Apr 2008, 02:30 -
Avisynth scripting
By demonwarrior in forum Newbie / General discussionsReplies: 9Last Post: 24th Dec 2007, 00:05