New AviSynth tool - AvsP v1.4.0 (6/5/07)

[qwerpoi]

Update: I created a website (http://www.avisynth.org/qwerpoi/) for AvsP, be sure to check it out, there's a ton of info in there, even long-time users are bound to learn something.

AvsP is (yet another) text editor for AviSynth, with all the exptected bells and whistles (syntax highlighting, autocompletion, calltips, video preview, etc). So what's different about this one? Let's take a look at this screenshot:

http://img168.imageshack.us/img168/4764/screenshotv110ha6.png (http://www.avisynth.org/qwerpoi/Demo.htm)

Notice the slider bars next to the video image? Basically, you can define any number of them to replace any numerical value in your script (in this case, the "hue" and "sat" arguments to Tweak), essentially giving your AviSynth script an instant gui environment. Cool, huh? (Note that you don't have to memorize any syntax, see link to demo below.) Also notice that the program is a tabbed text editor with a single attached video preview. What that means is that you can compare the video of different scripts without having to align multiple windows (anyone remember alt-tabbing multiple instances of VirtualDub? :) ) Anyway, the program has tons of other features, such as:

> built-in crop editor
> bookmark frame numbers in menu
> macro language for complete control of the program
> graphical front-end for avs2avi

You should read the program's readme for more info. The program itself doesn't require installation, doesn't write to the registry, and doesn't require installing any framework, so no harm in giving it a try, just unzip it to your directory of choice and off you go. You can download it here (the filesize is 5.2MB):

AvsP Download page (http://www.avisynth.org/qwerpoi/Download.html)

-> bugfix for v1.4.0 (http://forum.doom9.org/showthread.php?p=1029437#post1029437)

Mirror for v1.4.0 (http://www.savefile.com/files/784607) (savefile.com)
Mirror for v1.3.9 (http://www.savefile.com/files/696932) (savefile.com)
Mirror for v1.3.8 (http://www.savefile.com/files/667523) (savefile.com)
Mirror for v1.3.7 (http://savefile.com/files/536560) (savefile.com)
Mirror for v1.3.6 (http://savefile.com/files/507148) (savefile.com)
Mirror for v1.3.5 (http://www.savefile.com/files/414243) (savefile.com)

Japanese translation (http://niiyan.s8.xrea.com/blosxom/avisynth/tool/20060920-avsp-ja.htm) (translated by niiyan)
Russian translation (http://avisynth.org.ru/avsp) (translated by Fizick)
German translation (http://forum.gleitz.info/showpost.php?p=301023&postcount=14) (translated by Henrikx)
French translation (http://homepages.nildram.co.uk/~cestial/AvsP/) (translated by Alain2)
Spanish translation (http://forum.doom9.org/showthread.php?p=1000504#post1000504) (translated by zemog)
Portuguese translation (http://forum.doom9.org/showthread.php?p=1011750#post1011750) (translated by Veiga)
Italian translation (http://people.ee.ethz.ch/~rporetti/AvsP_Trad/AvsP_translationITA.zip) (translated by khs81)

The program runs on Windows XP and win98. Anyway, I feel that the program can really revolutionize the way you use AviSynth (I've been developing it on and off for more than 2 years), so please give it a shot, and post back with any feedback.

If you're still not convinced, check out this flash-based demo (http://www.avisynth.org/qwerpoi/Demo.htm), it goes over the program's fundamental features, including a demonstration of creating user sliders.

[Pookie]

Hey ! Nice app. I'm testing it out right now. Seems peppy. Python, right ?

Can't seem to do an external preview at the moment. Looks like the opened *.AVS file isn't being passed as a variable name to the player.

[unskinnyboy]

Quite nice! Toying around with it right now.

I know this is still under development, but couple of quick questions anyway:

1) Why does commenting a line or a block of text comes up as '#~' instead of just '#'. I know it doesn't matter what comes after the # once it is commented, but still curious as to why.

2) Entering a frame no. at the bottom and hitting enter takes quite an amount of time (a few seconds, but noticably annoying still) for the preview window to reposition itself at the new frame. I can understand taking time to seek to a new frame thousands of frames away, but there is a notable lag to seek to even a 100 frames away. But, if no one else has a problem with this, it is probably just my slow laptop (1.4 GHz P4M, 1 GB RAM).

Maybe more later once I poke around more..Best thing I like so far -> the preview window being attached to the main window.
Great tool. Thanks. :)

P.S: External preview is b0rked. Confirmed. Sounds like either a path problem (spaces in path?) or a name issue (what is being opened is sample.avs but what is being passed is previewX.avs, where X = 1,2,3..etc).

[qwerpoi]

@Pookie,
Hmm, strange about the external preview not working, works fine for me using media player classic - can you tell me what program you're trying to run (shot in the dark)? And yes, it's python (with wxpython) - how did you know? :)

@unskinnyboy,
1) Block comments use #~ to distinguish them from regular comments, basically to allow commenting or uncommenting a bunch of selected text (which would get screwed up if there were commented lines in the selected text).

2) Yes, jumping to a frame might be slow on older machines, but it may also depend on the script, try a simple AviSource on a reasonable resolution file and see if it's still slow. Runs pretty well on my laptop which has similar specs to yours.

And yes, despite all the features the program has, I also think that the attached video preview is the best one - it's pretty much the reason I wrote the whole thing to begin with :) .

[danpos]

@qwerpoi

It's a neat piece of software. The external preview is working fine in my system (tested with MPC, Mplayer).

Keep up the good work. :)

Regards,

[Mug Funky]

couple of suggestions (i really dig the slider idea...)

- f5 to refresh script, rather than shift-f5. mainly because VDmod does it that way, and i keep inadvertently closing and opening the preview window (also 1 key is quicker than 2 for an action that's likely to be performed often).

- preview window is docked onto script window... perhaps it could be free-floating? it could get tricky with big frame sizes is all.

another thing that'd be cool is if sliders could get some kind of realtime update... like if the last processed frame were held in memory and manipulated from there, rather than the script itself updating each time. this is probably not too workable though.

[qwerpoi]

@danpos
Thanks :)

@Mug Funky
- You're right about the F5 keyboard shortcut, I'll change it in the next version. As a temporary workaround you can hit F5 twice for the same effect, hee hee :)

- Yes, the preview window is docked, and will ALWAYS REMAIN THAT WAY! :devil: I know that there are advantages to a free-floating window (primarily screen real estate), but the docked window allows for a tight interaction between multiple scripts and the video preview, useful for filter chain comparisons without any window management. It's a design choice, so far I find the advantages outweigh the disadvantages, I'll wait and see what others think.

As far as realtime update for the sliders, as you mentioned, not easy. Perhaps possible if the program was communicating with avisynth directly instead of through .avs files, which is something I've considered doing (although not anytime soon :) ).

[Pookie]

@Pookie,
Hmm, strange about the external preview not working, works fine for me using media player classic - can you tell me what program you're trying to run (shot in the dark)?



Mplayer (of the Mencoder family)

[qwerpoi]

Mplayer (of the Mencoder family)
Ah, someone correct me if I'm wrong, but last I checked mplayer can't play back .avs files, which is what the external preview function uses to achieve playback.

[unskinnyboy]

Block comments use #~ to distinguish them from regular comments, basically to allow commenting or uncommenting a bunch of selected text (which would get screwed up if there were commented lines in the selected text).
OK, then what is the keyboard/menu shortcut for commenting/uncommenting a single line? I can't seem to find it. Which is why I thought commenting via CTRL+Q seems to be the only option you have provided.

Ah, someone correct me if I'm wrong, but last I checked mplayer can't play back .avs files, which is what the external preview function uses to achieve playback.
MPlayer can play avs files. For me, the external preview doesn't work in MPC (v6.4.9.0) or VirtualDubMoD (v1.5.10.2) - the only two I have tried so far. VirtualDubMoD gives me a Cannot open file "preview1.avs": The system cannot find the path specified message. MPC gives me a File not found error. To confirm that it wasn't an issue with spaces in the path (once too often I have seen this issue with alpha/beta versions of many software), I moved MPC to C:\ root, but same error.

[qwerpoi]

OK, then what is the keyboard/menu shortcut for commenting/uncommenting a single line? I can't seem to find it. Which is why I thought commenting via CTRL+Q seems to be the only option you have provided.
Sorry, no command for single line commenting/uncommenting, the Ctrl-Q command is provided for temporarily killing some lines of code (following the scheme of some programming editors such as SciTe).

MPlayer can play avs files. For me, the external preview doesn't work in MPC (v6.4.9.0) or VirtualDubMoD (v1.5.10.2) - the only two I have tried so far. VirtualDubMoD gives me a Cannot open file "preview1.avs": The system cannot find the path specified message. MPC gives me a File not found error. To confirm that it wasn't an issue with spaces in the path (once too often I have seen this issue with alpha/beta versions of many software), I moved MPC to C:\ root, but same error.
Ah ha, you caught me! Spaces in the external program filename are not a problem, but spaces in the .avs filename are. To verify this, you should be able to save a script like C:\test.avs and preview it just fine. I'll fix this asap.

[qwerpoi]

Okay, new version 1.0.3 (see first post to download), only two changes:

* fixed issue with spaces in filenames when using external preview (thanks unskinnyboy, Pookie)

* changed refresh keyboard shortcut to F5 (to be more similar to vdub), shift-F5 now hides the preview (suggested by Mug Funky)


Anyone needing to update from an older version, just replace the old exe with the new one.

[danpos]

@qwerpoi

A small suggestion: what about do you open an account at geocities (http://geocities.yahoo.com/) and so host there yours files? It's free and hasn't such annoying tickets for download anything like rapidshare.

Regards,

[qwerpoi]

@qwerpoi

A small suggestion: what about do you open an account at geocities (http://geocities.yahoo.com/) and so host there yours files? It's free and hasn't such annoying tickets for download anything like rapidshare.

Regards,
Aw, I didn't want to do anything like get a geocities account and manage a website and stuff :( . But since I don't like rapidshare either and since you asked so nicely, it's done (the download link on the first post has been updated).

[Pookie]

Yes indeed, v1.03 is working with external preview. :D

Thanks a lot for the app.

[G_M_C]

Aw, I didn't want to do anything like get a geocities account and manage a website and stuff :( . But since I don't like rapidshare either and since you asked so nicely, it's done (the download link on the first post has been updated).

But for me ... neither screenshot nor download-link is working atm.

Is there some alternative ?

[qwerpoi]

But for me ... neither screenshot nor download-link is working atm.

Is there some alternative ?
The screenshot should be working now, for the program download, it seems that you have to right-click and "save target as" to download (url gets mangled otherwise), I added the rapidshare link in case the first link doesn't work. Sorry about any temporary inconvenience.

[danpos]

@qwerpoi

Thanks for take my suggestion into account, mate! You're superb! :)

Regards,

[Richard Berg]

This is super cool.
Aw, I didn't want to do anything like get a geocities account and manage a website and stuff
I will PM you once I get some stupidity ironed out.

[ricardo.santos]

geocities download not working

[Jacquers]

Geocities (free version) has some limits on how much data per hour you can download. Wait a while and try again.

[qwerpoi]

Geocities (free version) has some limits on how much data per hour you can download. Wait a while and try again.
Yep, sorry about the awful geocities hourly download limit (it works out so only one person can get the program in an hour :scared: ), you can always use the rapidshare link if the first one isn't working. Hopefully there'll be a better distribution method forthcoming.

[Jeremy Duncan]

Yep, sorry about the awful geocities hourly download limit (it works out so only one person can get the program in an hour :scared: ), you can always use the rapidshare link if the first one isn't working. Hopefully there'll be a better distribution method forthcoming.

Try savefile.com
http://www.savefile.com/

[Pookie]

Mirror for v1.03

http://dl025.filefactory.com/dl/f/b7bcba/b/9/h/3c73f7dffb264c8f/


qwerpoi, I'll remove the link if you don't want it mirrored.

[foxyshadis]

Can you serialize your options into a text format, like xml? Also, can you split options into actual options, and a separate syntax.def for avisynth syntax? If you do, I can quickly add definitions for many third party plugins out there and submit them to you. I'd also like to know if you can add the definition popup whenever it reaches a comma, as well, to see what other arguments are available, as well as perhaps using italics to separate named from unnamed arguments (instead of the script-function convention of quotes).

I think I'm going to be using this; even if it's not as refined as editplus, the popup and preview are too cool!

Oddly, it doesn't seem to like % (modulo) at all, syntax highlighting on the rest of the line is disabled. Not that it's used often in avisynth, heh.

[qwerpoi]

I'll be updating the download links using avisynth.org's ftp shortly (you've got PM Richard Berg), which should solve any download issues (thanks for the help and suggestions Richard Berg, Pookie, danpos, Jeremy Duncan, and anyone I may have missed :) ).

Can you serialize your options into a text format, like xml? Also, can you split options into actual options, and a separate syntax.def for avisynth syntax? If you do, I can quickly add definitions for many third party plugins out there and submit them to you.
I kind of like having all my options come from the single dat file, but I can understand what you're saying. At least as a temporariy comprimise I can work on optionally reading avisynth syntax from a seperate file. I'm not sure if you already know this, but you can quickly add (or delete) third party filter info from the menu command Options -> AviSynth filters (in fact nearly all the options the user would want to edit can be configured in the Options menu). But I agree it is a bit of a pain to add a bunch of filters at one time.

I'd also like to know if you can add the definition popup whenever it reaches a comma, as well, to see what other arguments are available, as well as perhaps using italics to separate named from unnamed arguments (instead of the script-function convention of quotes).
Definition popup calltips on comma should be doable, I'm not so sure about italics in the popup calltips though (I'm using wxpython's implementation of Scintilla, which afaik doesn't have rich-edit capabilities in popup calltips seen in other programming editors). I'll look it over.

Oddly, it doesn't seem to like % (modulo) at all, syntax highlighting on the rest of the line is disabled. Not that it's used often in avisynth, heh.
Yep, you caught me - I cheated with the syntax highlighting, I'm using a pre-defined lexer for the Octave language, which is similar to avisynth except for minor differences like you found (comments in Octave are either # or %). I'll have to write my own custom lexer for avisynth eventually, which is not entirely straightforward with wxpython. A bit sloppy on my part, but I wanted to release the program since it's mostly unnoticeable and the program offers so many other benefits. Thanks for all the suggestions, I appreciate it, and I'm glad you like the program :).

[tsp]

qwerpoi:
This program looks very good. But as foxyshadis wrote it could be nice if you could add support for reading the syntax from a seperate file as I'm creating a small program that reads the syntax for all installed plugins and write it to a file else I would have to figure out the syntax of your options.dat file.
Another thing would be if it could be posible to use named argument with the sliders like

pointresize(target_width=[<"width", 16, 1024, 512>])

[qwerpoi]

The link on the first post has been updated, hosted on avisynth.org so everything should be gravy (thanks again Richard Berg).

qwerpoi:
This program looks very good. But as foxyshadis wrote it could be nice if you could add support for reading the syntax from a seperate file as I'm creating a small program that reads the syntax for all installed plugins and write it to a file else I would have to figure out the syntax of your options.dat file.
My dat file doesn't have a syntax, it's a binary file (cPickled if you're familiar with Python), but I'll try to allow reading info from a separate file as well. Your program sounds interesting, I didn't know it could be done - I'm looking forward to it.

Another thing would be if it could be posible to use named argument with the sliders like

pointresize(target_width=[<"width", 16, 1024, 512>])

Actually, if you're referring to AviSynth optional arguments it's already possible. Try something like:
Tweak(hue=[<"hue", -180, 180, 91>])
Basically, the chunk of text [<...>] is replaced by a single number when it's saved to an avs script. Your example won't work because pointresize(target_width=640) won't work either (as far as I know). You may have been mislead by my popup calltips, only arguments in double-quotes are optional, a notation I borrowed from the AviSynth docs.

[Henrikx]

@qwerpoi
Good messages over good programs come fast to Germany ;)
http://forum.gleitz.info/showthread.php?t=31104
Great Work ! Thank You !

[tsp]

qwerpoi: You can try my little program. It's written in c++ and source is included.
Get it here:
http://www.avisynth.org/tsp/extract.zip

[qwerpoi]

@qwerpoi
Good messages over good programs come fast to Germany ;)
http://forum.gleitz.info/showthread.php?t=31104
Great Work ! Thank You !
Thanks :)

qwerpoi: You can try my little program. It's written in c++ and source is included.
Get it here:
http://www.avisynth.org/tsp/extract.zip
Thanks for the link, I'll try it out when I get a chance. Maybe I can learn a bit more about AviSynth's internals from it (not sure I'm ready for it, though).

[qwerpoi]

I made a flash-based demo highlighting some of the program's features, you can view it here (http://www.avisynth.org/qwerpoi/Demo.htm) (I added the link to the first post as well).

qwerpoi: You can try my little program. It's written in c++ and source is included.
Get it here:
http://www.avisynth.org/tsp/extract.zip
I tried to run your ExtractFilters program but got a runtime error (abnormal program termination) - does it require a specific version of AviSynth? (I'm running 2.53 on my laptop). Anyway, if you can post some sample output (including some filters with optional arguments) I can try to have my program read from the same format.

[Pookie]

The slider feature is very cool. Good info in the flash demo. If you can make it small enough, perhaps include an Xvid (or mpeg1 or flv) tutorial with future distributions - it'll cut down on having to answer the more basic questions.

[tsp]

qwerpoi:
It works with avisynth 2.5.6. It includes the dll from 2.5.7 alfa(called avisynth257.dll) as it includes a fix so it is posible to get the parameters for the external filters. The dll should be located in the same directory as ExtractFilters. I have updated the zipfile so that it includes an example of the output in avsfilters.txt and extract the internal filters. If you want another output format it should be posible to fix that.

[krisq]

I just want to thank you for this excellent tool.
So... :thanks:

[mimage]

I can't thank you enough!!! This program is outstanding! I've been waiting for something just like this for a long time, and never expected to get something this outstanding. It's a lot like the options that some filters have in Vdub where there is a preview button so you can see changes made in the video as you mess with the filters options but instead of only a few filters it seems to work with just about anything.. I've actually never figured out a way to make any filter in avisynth to work like those filters in vdub with the preview button. This is soo great you have made me soo happy! :D


And again
:thanks:

[qwerpoi]

New version 1.0.4 (see first post for download), again minor changes:

* read in filter info from text file named "avsfilters.txt" (suggested by foxyshadis, tsp)

* popup calltips show whenever cursor is anywhere inside a filter's arguments (suggested by foxyshadis)

* calltips close on left mouse click in the text

A changelog was added to the end of the program's readme.txt. The first new feature, reading filter info from "avsfilters.txt", works like this. Let's say you make a text file containing filter information like this:

AviSourcePlus(clip)
SharpenTwice(clip, amount)
Each line is a separate filter, and there must be at least one open parentheses in the line. If you name this file "avsfilters.txt" and put it in the same directory as AvsP.exe, the next time you start the program up it will read the data from the text file and update its internal database accordingly. Note that you can always edit this info from the menu command "Options -> AviSynth filters", but this gives a convinient way to update a lot of info in one shot. Plus, tsp has made a cool app to automatically generate this info based on all the plugins installed on your specific computer (works with AviSynth 2.5.6 and above), get it here (http://www.avisynth.org/tsp/extract.zip).

As an aside, while we're mentioning editing the filter information, here's a cool tip for you to try. The info that you edit in "Options -> AviSynth filters" determines what shows up for the popup calltips. But they don't just have to be filter arguments, you can add notes to any filter you want. For example, if you have certain settings you use often for a filter like TemporalSoften, you can edit the info in the "Filter arguments" text box like this:

(clip, int radius, int luma_threshold, int chroma_threshold, int "scenechange", int "mode")

Good starting values: TemporalSoften(4,4,8,15,2)
For noisy videos: TemporalSoften(5,4,9,16,3)
(I made up some of those numbers, so don't yell at me later :) ) Now every time you get a popup calltip for TemporalSoften you'll see your notes along with the filter arguments. Especially useful for resize filters, to keep reminders of good width/height values for different aspect ratios.


@Pookie
The flash demo consisted of over 100 screenshots at 800x600, and comes up to 1MB in size. I'm don't think I can convert it to video in under a meg without having it look terrible, but I don't claim to be a low-bitrate champion, so if anyone's up to the challenge, let me know.

@krisq
You're welcome (I seem to be lacking a you're welcome smiley)

@mimage
Wow, I guess those are tears of joy from your avatar :) . Glad you like the program.

[krisq]

is there a way to make sliders jump by mod16 (for resizing)?
I hope you know what i mean because my english is pretty bad ;)

[Fizick]

qwerpoi,
what is license of your prog?

[qwerpoi]

is there a way to make sliders jump by mod16 (for resizing)?
I hope you know what i mean because my english is pretty bad ;)
Unfortunately no, but it's something I've been thinking about. Basically it might be possible to extend the slider syntax to allow the user to define an arbitrary list (doesn't even have to be numbers!). I'll have to go over it in my head some more. In the meantime, I'm sure some savvy scripter can come up with an AviSynth function which takes in a number and converts it to an appropriate mapping (input 1, get 16, input 2, get 32, etc).

[qwerpoi]

qwerpoi,
what is license of your prog?
Dunno :confused: . I developed the program for myself, didn't really intend on releasing it, but it got so good I felt it could benefit the community (gee, I'm the king of modesty). I guess I could gpl it and release the source if the demand is high enough, but I kind of want to be able to control the direction of its development (it's the first gui program I've ever written), at least for now. For the moment, let's just say it's freeware, use at your own risk, feel free to distribute for non-profit reasons. Sorry for the long-winded answer :)

[Mtz]

I'm not good in avisynth, but I have 2 questions:
- how to use "directshowsource" when loadin an avi for example?
- will be ever possible when inserting filter automatically appear sliders for all functions of the filter, with let say "default values"?
When I want to enter a filter it require first letter to be Caps.

enjoy,
Mtz

[qwerpoi]

- how to use "directshowsource" when loadin an avi for example?
If you want to use "directshowsource" when inserting an avi, you can edit the exension-based template using the menu command "Options -> Extension templates", hopefully it's self explanatory. Of course, then all your avi files will be loaded with direcshowsource, so it might be better to just type "DirectShowSource" and then insert the filename (from the context menu, keyboard shortcut is Shift-F9). If you don't like that either, then you can be bold and try and make a macro. Here's the code from the "Template Example" macro included with the program (located in the Macros subdirectory):

# Get the filename via an open dialog box
filename = avsp.GetFilename()

if filename:
# Create a new tab
avsp.NewTab()
# Create and insert the script into the tab
avsp.InsertText(
'AviSource("' + filename + '")\n'
'Sharpen(1.0)\n'
'Info()\n'
)
# Show the video preview
avsp.ShowVideoFrame()

The macro's language is Python, which would be a bit of a chore for a beginner to learn just to make AvsP macros, but hopefully it's simple enough to understand such that you can modify this example to create your own template. Any macro you make will automatically show up in the "Macros" menu. Whew! Them's a lot of options!

- will be ever possible when inserting filter automatically appear sliders for all functions of the filter, with let say "default values"?
It's currently not possible, since my program doesn't directly communicate with AviSynth, all it does is make .avs text files. In theory it's possible assuming AviSynth can provide the appropriate info for any given filter (min and max values for each numerical argument), someone who knows more than me on the subject (tsp?) would be able to answer the question better.

When I want to enter a filter it require first letter to be Caps.
Yep, a word starting with a capital letter is what triggers the autocompletion. Kind of strange, but otherwise the box would pop up whenever you type anything, which would be annoying. You can always manually trigger autocompletion with the keyboard shortcut Ctrl-Space.

I guess all in all it's best not to think of AvsP as some complete graphical environment for AviSynth. AviSynth is and always will be about making text scripts, the beauty is in the simplicity. I wrote AvsP as a means of aiding in that process, not as an alternative or replacement to it.

[foxyshadis]

Cool update! I like the ingenuity of reusing the Octave parser. =D I'm sure writing an avisynth parser would be as simple as slightly modifying the Octave one; it's probably written in a lexical compiler so it shouldn't be too painful.

btw, is your python dist stripped down as much as it can be? That 5 mb will hurt for bandwidth, especially if it gets popular.

[qwerpoi]

Cool update! I like the ingenuity of reusing the Octave parser. =D I'm sure writing an avisynth parser would be as simple as slightly modifying the Octave one; it's probably written in a lexical compiler so it shouldn't be too painful.
Yep, I took a look at some of the sources, but I wasn't able to get an external parser to work with wxPython's implementation of scintilla, wxStyledTextCtrl. Admittedly, I haven't tried very hard, and if any wxpython guru out there wants to make a wxpython-compatible avisynth lexer, I'd be happy for the help :)

btw, is your python dist stripped down as much as it can be? That 5 mb will hurt for bandwidth, especially if it gets popular.
Well, that's about the smallest I've heard anyone getting it down to using py2exe along with upx compression. It should in theory be possible to strip out more python modules, but the bulk of the filesize comes from the python dll and the wxpython dll, which are required. The only other way to reduce the filesize is to use a different gui library. If I use venster (http://venster.sourceforge.net/), for example, I could get the filesize to less than 2mb - unfortunately, venster is not nearly as complete as wxpython (I'm using a lot of tricks with wxpython's snazzy features) and isn't being developed much. The whole filesize thing used to really bug me (I once swore never to write an app bigger than 1MB), but I've come to terms - 4.5mb is reasonable, and I'd rather be developing new features for my program than working with an underdeveloped or extremely difficult framework for the sake of reducing the program's filesize. Still, it's damned embarassing that AvsP clocks in as a bigger download than AviSynth itself :(

[Koti]

Wow , very very cool

Ty :D :D :D

[Dr.D]

Thanks for the great program!
Couple of issues:
1. Could you please add a zoom feature in preview? It's really hard to see the difference between clips starring to tiny window.
2. Numeric keypad's keys (arrows, Ins etc.) don't work.

[qwerpoi]

1. Could you please add a zoom feature in preview? It's really hard to see the difference between clips starring to tiny window.
Well, I'll think about it, but ultimately it would be an artificial comparison - the window's as small as your input video, any zoom besides a doubling point resize would be innaccurate for the sake of comparison. Maybe a magnifying lens sort of feature would work. You could always resize the video in your script if it's that big of a deal, or use AviSynth's Subtract filter if the differences are that subtle.

2. Numeric keypad's keys (arrows, Ins etc.) don't work.
Whoa whoa whoa - that's the first I've heard of that! I've recently been testing on my laptop, so I guess anything's possible. Exactly when does this occur (always, or just in a certain window)?

[Mtz]

... my program doesn't directly communicate with AviSynth, all it does is make .avs text files. In theory it's possible assuming AviSynth can provide the appropriate info for any given filter (min and max values for each numerical argument), someone who knows more than me on the subject (tsp?) would be able to answer the question better.
I was thinking that the creators of the filters (some of them wich require values in the script) for all parameters have some min. and max. values. Avsp to read them from the filter, not from avisynth. ;)

[tsp]

qwerpoi: Thanks for the update. Works great with the import from the textfile. Would you like a dll version that you can include with avsP?

Mtz: Sorry that is not posible. Likewise it is not posible to figure out what parameters has default values assigned.