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

[mgh]

Superb tool for tweaking parameters of Avisynth filters. The sliders make it very easy. Works with your own functions as well.
Three cheers

[qwerpoi]

Another, more universal, idea:


dull = last
sharp = dull.LimitedSharpenFaster(strength=250)
Soothe(sharp, dull, keep=50)


but it's may be too complicated.
Thinking about it, I couldn't even tell you how incredibly useful that would be. So many times, I've done nothing but flip back and forth between vdub and editplus to enable and disable one line (usually I just use interleave if I realize I'm going to be doing it).
Hmm, I may be able to pull off the ... syntax. Ultimately, though, whatever I do for section toggling, it probably won't be as memory efficient as making separate scripts in multiple tabs. In other words, the toggling mechanism requires reloading a modified script every time you toggle (unless I build a script for every permutation of toggle sections). Using multiple tabs loads a script only once per tab, and is easy to switch between (middle-mouse scroll, Ctrl-Tab, keyboard shortcuts ~, 1, 2, 3, 4, etc). But I'll still give this idea a shot, could be useful for large permutations.

@ qwerpoi,
I just love the sliders. ;)
Many thanks. When I get some time, I'll try out your program, I never noticed it before (I need to read the forums more carefully it seems). It looks like you did a great job with all the encoding features, very cool stuff.

Superb tool for tweaking parameters of Avisynth filters. The sliders make it very easy. Works with your own functions as well.
Three cheers
:thanks: Glad you like the program.

[krieger2005]

Your Program can't handle String-Expressions (Syntax-Highlight is wrong) like that:
ScriptClip(Z, """
\ YV12LutXY(X,Y,"<something>")
\""")

[Fizick]

zoom 300% is broken?

[niiyan]

Japanse translation file is here:
http://niiyan.net/?AvsP

[Fizick]

And Russian is here:
http://avisynth.org.ru/avsp/avsp112translation-ru.zip

[qwerpoi]

Your Program can't handle String-Expressions (Syntax-Highlight is wrong) like that:
ScriptClip(Z, """
\ YV12LutXY(X,Y,"<something>")
\""")
Yes, you're right, it doesn't properly handle triple-quoted strings. As I mentioned in an earlier post, I didn't write a syntax highlighter for AviSynth, I just borrowed an already written one for a similar language (Octave). Eventually I'll have to write my own highlighter, it may not be for a while (my to-do list is getting enormous), sorry about the inconvenience.

zoom 300% is broken?
If you're referring to the status bar messages, yes, it's a bug, it'll be fixed in the next release.

Japanse translation file is here:
http://niiyan.net/?AvsP
And Russian is here:
http://avisynth.org.ru/avsp/avsp112translation-ru.zip
Very cool, I tested both out, they work great. I added the links to the first post. As I mentioned before, with any new version I'll be sure to mark any new or changed messages in "__translation.py" so you can just modify your own accordingly.

And just so you guys know, I've been pretty busy lately, the next release will probably be during or right after the weekend. I'm currently working on putting together some documentation for the program as well, something that has been lacking. Well, unless you can read Japanese (http://www.avisynth.info/?AvsP) :) - I believe that wiki was put together by niiyan, not me, so it's about time I start writing docs as well.

[wuziq]

just discovered this app today.. it's awesome. thanks for all your work.

[krieger2005]

Yes, you're right, it doesn't properly handle triple-quoted strings. As I mentioned in an earlier post, I didn't write a syntax highlighter for AviSynth, I just borrowed an already written one for a similar language (Octave). Eventually I'll have to write my own highlighter, it may not be for a while (my to-do list is getting enormous), sorry about the inconvenience.

I can imagine the length of your to-do-list :). It has many aficionados. I am one of them :). Thank you very much.

[niiyan]

Well, unless you can read Japanese (http://www.avisynth.info/?AvsP) :) - I believe that wiki was put together by Niiyan, not me, so it's about time I start writing docs as well.

You're right. I wrote it because I'm very impressed by your program. But what I wrote is just an introduction of AvsP. I'm looking forward to your docs. I can discover something I don't know yet :)

I hope you will call me not "Niiyan" but "niiyan" (in lowercase) ;)

[qwerpoi]

just discovered this app today.. it's awesome. thanks for all your work.
b^_^d You're welcome.

I can imagine the length of your to-do-list :). It has many aficionados. I am one of them :). Thank you very much.
Thanks for understanding. It's actually pretty important that I write my own syntax highlighter for other reasons, since I have user sliders and other AvsP-specific syntax. But it's a fair bit of work, and I never managed to make an external syntax highlighter work with my framework (wxPython), so I'm going to save that task for a later date, since it's unclear how long it will take.

You're right. I wrote it because I'm very impressed by your program. But what I wrote is just an introduction of AvsP. I'm looking forward to your docs. I can discover something I don't know yet :)

I hope you will call me not "Niiyan" but "niiyan" (in lowercase) ;)
Hee hee, sorry about the name mispelling, I edited my earlier post.

For those interested, I've finished a good number of features for the next release, context sensitive help (I think you'll be happy with the implementation), section toggling using the second syntax proposed by Dr. D as discussed earlier, etc. I need to take care of a few small things before releasing, and hopefully I can get the docs out at the same time.

[krisq]

just got an idea:
is it possible for you to add some modifier key ('shift' maybe?) to make sliders jump by mod16 (would be great to set that value in options)? you know, for resizing and stuff...:)

[qwerpoi]

just got an idea:
is it possible for you to add some modifier key ('shift' maybe?) to make sliders jump by mod16 (would be great to set that value in options)? you know, for resizing and stuff...:)
Hum, I think it can be done, I'll try and have something like that in the coming release (no guarantees, though). It's a good request, since sliders can't be used effectively with resizers, but what I wanted to do was to handle resizing with some sort of resize/aspect ratio calculator (like gordian knot), sort of similar to AvsP's crop editor, which is separate from sliders, gives mod information, etc. But since the resize calculator isn't coming anytime soon, I'll try and implement your idea, it could be useful for other things as well.

[Dr.D]

just got an idea:
is it possible for you to add some modifier key ('shift' maybe?) to make sliders jump by mod16 (would be great to set that value in options)? you know, for resizing and stuff...:)
I vote for this idea too, recently I was thinking about this when I tried to use slider for ChromaShift(C), C could be only even.
May be just add an aditional optional parameter for sliders - step:

ChromaShift(C=[<"C", 2, 8, 4, 2>])

means from 2 to 8 with step 2?

[krisq]

I vote for this idea too, recently I was thinking about this when I tried to use slider for ChromaShift(C), C could be only even.
May be just add an aditional optional parameter for sliders - step:

ChromaShift(C=[<"C", 2, 8, 4, 2>])

means from 2 to 8 with step 2?

excellent idea :cool:

[Henrikx]

German translation for AvsP 1.1.2
http://forum.gleitz.info/showpost.php?p=301023&postcount=14

Thx again to qwerpoi

[qwerpoi]

I vote for this idea too, recently I was thinking about this when I tried to use slider for ChromaShift(C), C could be only even.
May be just add an aditional optional parameter for sliders - step:

ChromaShift(C=[<"C", 2, 8, 4, 2>])

means from 2 to 8 with step 2?
I've implemented this in the coming version, slightly differently. Instead of the additional parameter, you specify the step in the slider label, in your example it would be [<"C % 2", 2, 8, 4>], a resize width would look like [<"width % 16", 320, 640, 320>], etc. This upcoming version is going to be tasty :)

German translation for AvsP 1.1.2
http://forum.gleitz.info/showpost.php?p=301023&postcount=14

Thx again to qwerpoi
Excellent! I'll add the link to the first post.

[Henrikx]

@qwerpoi
I try to explain.....
In my first German-translation of AsvP,somebody wished,that I translate Ctrl to Strg (German keyboard) .
For Example : "Cut\tCtrl-X" : u"Ausschneiden\tStrg-X",
But than,every lover-case character becomes interpreted as Control-Funktion ? For Example : Key O without Crtl(Strg) ,a window opened ?

Why ?

[qwerpoi]

@qwerpoi
I try to explain.....
In my first German-translation of AsvP,somebody wished,that I translate Ctrl to Strg (German keyboard) .
For Example : "Cut\tCtrl-X" : u"Ausschneiden\tStrg-X",
But than,every lover-case character becomes interpreted as Control-Funktion ? For Example : Key O without Crtl(Strg) ,a window opened ?

Why ?
Oh, the short answer is that you should not translate the keyboard shortcut part of the strings, they are used by the program to register the actual keyboard shortcuts. I can't explain exactly what happens when you translate "Ctrl" to "Strg", but for the moment you should leave those parts alone.

Actually I'm not sure what's the recommended way to handle this situation, obviously it would be nice to translate the keyboard shortcuts as well. I'll do a little research on this.

[Henrikx]

THX qwerpoi

[qwerpoi]

New release, version 1.1.5 (download link in the first post), this one's a big one. Here's the list of changes:

* show filter documentation by clicking the calltip (suggested by Fizick)

* toggle portions of script text (suggested by Dr. D)

* now possible to specify modulo values with user sliders (suggested by krisq)

* remember path of last saved session (suggested by Dr. D)

* reworked filter presets to be easier to edit

> fixed mouse wheel tab switching when zoomed (thanks Dr. D)

> fixed text visibility issue when using Find or Find next (thanks mkanel)

> fixed small mistakes with some messages (thanks niiyan)

> fixed small bug with recentdir pathname

> fixed minor video preview window sizing issues

> fixed minor bug when closing the only tab

I also created a website (http://www.avisynth.org/qwerpoi/), it covers the majority if not all of AvsP's features, be sure to check it out. The site's a bit rough around the edges (it's my first website, I have no html or css skills), and looks a bit fugly in Internet Explorer. Any comments or suggestions are certainly welcome, but just so you know I'm not going to spend tons of time trying to design a great looking website.

The most noticeable new feature is the ability to open a filter's documentation by clicking on a popup calltip. AvsP automatically tries to find the filter's documentation in certain directories based on filenames. You can edit the search directories, or even specify a file or url to open for each filter. Read more about it here (http://www.avisynth.org/qwerpoi/Text.html) in the "Calltips" section.

Another big new feature is the section toggle tags, as discussed several posts earlier. Section toggle tags allow you to tag a portion of your script for quick enabling/disabling with a check box. Read about it here (http://www.avisynth.org/qwerpoi/UserSliders.html) in the "Section toggle tags" section.

A new addition for user sliders is the ability to specify mod step sizes, useful for resize filters where you want mod 16 widths, etc. Detailed description of the the syntax can be found here (http://www.avisynth.org/qwerpoi/UserSliders.html), at the bottom of the "Basic usage" section. And don't worry, the new syntax is completely backwards compatible, no need to rewrite any macros or scripts.

There are a lot of other changes in this release, so be sure to try it out and report back with any comments or problems.

Note to translators: the new version has about 20 new messages to translate, the new messages are marked in "__translation.py", here's a couple of lines from the file:

messages = {
"Find" : u"",
"Replace" : u"",
"Could not find docs for filter %(name)s!" : u"", # New in v1.1.5

So in order to update your translations, you can find each line with the text "# New in v1.1.5", translate the message, then copy it into your own translation file (the order of the messages is not important). Also note that at the very bottom of the new "__translation.py" is a list of messages that are no longer used (only two), you can delete them from your translation file (although there's no harm in leaving them in).

[krisq]

Really great stuff :D. :thanks:

[Henrikx]

...Update German translation to AvsP 1.1.5

[niiyan]

Updated Japanese translation, too.
http://niiyan.net/?AvsP

[Fizick]

qwerpoi,
thanks for your work!

Avisynth docs for filters works well.
For russian docs I set russian path before english.

One suggestion. I like to open russian general avisynth help on menu
Help -> avisynth help
Can you make its path selectable too?
I like to have

[qwerpoi]

Really great stuff :D. :thanks:
You're welcome b^_^d . Hope the mod sliders are working out okay for you, let me know if you find any problems with them.

...Update German translation to AvsP 1.1.5

Updated Japanese translation, too.
http://niiyan.net/?AvsP
Wow, that was fast! Thanks!


One suggestion. I like to open russian general avisynth help on menu
Help -> avisynth help
Can you make its path selectable too?
Sure, it will be in the next release, which will most likely be in a couple of days, I want to wait a bit to see if there are any small bugs or other simple feature requests posted here that need to be changed as well.

[Fizick]

Russian translation v1.1.5 is at http://avisynth.org.ru/avsp

[Bh4i]

This is a GREAT tool for beginners like me. Thanks man :)

[Revgen]

@qwerpoi

Would you mind implementing a hexadecimal slider. I want to be able to use the slider feature to change the color of the BlankClip filter.

The hexadecimal color values are like these: http://www.avisynth.org/ColorPresets

Only instead of "#" being in front, a "$" has to be used instead. Kinda like "color_blue" is $0000FF instead of #0000FF.

BTW thanks for this wonderful tool.

[qwerpoi]

Russian translation v1.1.5 is at http://avisynth.org.ru/avsp
Thanks, I updated the links on the first post and on the website's download page appropriately.

This is a GREAT tool for beginners like me. Thanks man :)
b^_^d You're welcome man, glad you like the program.

@qwerpoi

Would you mind implementing a hexadecimal slider. I want to be able to use the slider feature to change the color of the BlankClip filter.

The hexadecimal color values are like these: http://www.avisynth.org/ColorPresets

Only instead of "#" being in front, a "$" has to be used instead. Kinda like "color_blue" is $0000FF instead of #0000FF.

BTW thanks for this wonderful tool.
Well, implementing arbitrary list sliders is something I've been thinking about. It may appear in some shape in a future release, but I think there's a very elegant way to deal with your situation already. In your case, you can take advantage of the decimal color format AviSynth uses and make a user defined function. Here's an example script:
function rgb2decimal(int r, int g, int b)
{
return r*65536 + g * 256 + b
}

BlankClip(color=rgb2decimal([<"red", 0, 255, 0>], [<"green", 0, 255, 0>], [<"blue", 0, 255, 0>]))

Now you will have a slider for r, g, and b, which I think is a bit more intuitive than a single slider for the full range of colors. Basically, you can make your own arbitrary list sliders with user defined functions, particularly by taking advantage of AviSynth's Select function. I'll probably add a section to the website describing this type of approach.

[Revgen]

Thanks, I updated the links on the first post and on the website's download page appropriately.


b^_^d You're welcome man, glad you like the program.


Well, implementing arbitrary list sliders is something I've been thinking about. It may appear in some shape in a future release, but I think there's a very elegant way to deal with your situation already. In your case, you can take advantage of the decimal color format AviSynth uses and make a user defined function. Here's an example script:
function rgb2decimal(int r, int g, int b)
{
return r*65536 + g * 256 + b
}

BlankClip(color=rgb2decimal([<"red", 0, 255, 0>], [<"green", 0, 255, 0>], [<"blue", 0, 255, 0>]))

Now you will have a slider for r, g, and b, which I think is a bit more intuitive than a single slider for the full range of colors. Basically, you can make your own arbitrary list sliders with user defined functions, particularly by taking advantage of AviSynth's Select function. I'll probably add a section to the website describing this type of approach.

Yeah, I know about that. I just hate having to use 3 sliders though.:D

I'll just use that method for now. It's better than having no sliders.

Thanks.

[foxyshadis]

But how would you even work a single slider that includes the full range? Changing just the red would be incredibly painful, as you then have to try to realign the green and blue (or, changing just the luma and having to line the two chroma planes back up).

The best solution is a real colorpicker, but who knows how long that could take to implement (and for a function not often used); in the meantime a triple slider is the most functional.

[niiyan]

@qwerpoi
Can you add VirtualDub's "Jump to frame" feature to AvsP?
When you choose "Go > Go To Frame..." in VirtualDub menu or just click "Ctrl + G", "Jump to frame" window appears.
Enter the frame number (or frame at time) in the input box in the window, then you can jump to the frame.

[mkanel]

qwerpoi,

I hate to add to your workload but I've found a bug. When using one of my own functions AvsP reports an error during preview even though I can preview it in AVSEdit and other software.

Here's the report from AvsP:

Traceback (most recent call last):
File "AvsP.py", line 2899, in OnMenuVideoRefresh
File "AvsP.py", line 4093, in ShowVideoFrame
File "wxp.pyo", line 708, in SetRange
NameError: global name 'sys' is not defined

The function just makes a collage of a selectable number of rows and columns and a selectable border size.

You can call it with this Version.Collage

Here's the function that triggered the error:

function Collage(clip clip, int "NumberOfRows", int "NumberOfColumns",int "Borders")
{
NumberOfRows=default(NumberOfRows,2)
NumberOfColumns=default(NumberOfColumns,2)
Borders=default(Borders,2)

Global NumberOfRows=NumberOfRows
Global NumberOfColumns=NumberOfColumns
Global Borders=Borders

Global frame=clip
Global Row=SH(frame.trim(0,-1).addborders(0,0,Borders,Borders),0,0) #Stack Horizontally

MakeCollage=SV(Row,0)
return MakeCollage
}

#Stack Horizontally
Function SH(clip H, int n, int c)
{
n=n+1
return (n==NumberOfColumns) ? H.crop(0,0,-Borders,-0)
\ : SH(stackhorizontal(H,frame.trim(c*NumberOfColumns+n,-1)
\ .addborders(0,0,Borders,Borders)),n,c)
}

#Stack Vertically
function SV(Clip Rows, int c)
{
c=c+1
NewRow=SH(frame.trim(c*NumberOfColumns,-1).addborders(0,0,Borders,Borders),0,c)
return (c==NumberOfRows) ?Rows.crop(0,0,-0,-Borders) : SV(stackvertical(Rows,NewRow),c)
}

Let me know if you need any more information.

Now a question. I would like to have some of my user functions appear with syntext highlighting, I can add them one at a time under options>avisynth filters. I tried adding them to the file avsfilters.txt created by tsp's ExtractFilters progam but AvsP doesn't recognize them. Should it?

Your program keeps getting better and better, Thanks for all the hard work? Mike.

[qwerpoi]

@qwerpoi
Can you add VirtualDub's "Jump to frame" feature to AvsP?
When you choose "Go > Go To Frame..." in VirtualDub menu or just click "Ctrl + G", "Jump to frame" window appears.
Enter the frame number (or frame at time) in the input box in the window, then you can jump to the frame.
This feature is already there, the text box on the video controls at the bottom of the program works almost exactly like VirtualDub's "Jump to frame" window. Just type in a frame or time and hit enter.

I hate to add to your workload but I've found a bug. When using one of my own functions AvsP reports an error during preview even though I can preview it in AVSEdit and other software.
Thanks for bringing it up, I'll try and find out what's going on. And don't worry about my workload, I'm always interested in squashing bugs.

Edit: Found and fixed the problem, it'll be in the next release (a bugfix release, it'll be out in a day or two).

Now a question. I would like to have some of my user functions appear with syntext highlighting, I can add them one at a time under options>avisynth filters. I tried adding them to the file avsfilters.txt created by tsp's ExtractFilters progam but AvsP doesn't recognize them. Should it?
By gum, you're right, I must have broken the feature when I changed the file format a couple of versions ago. I'll get this fixed by the next release.

Your program keeps getting better and better, Thanks for all the hard work? Mike.
You're welcome? :)

[nibbles]

What a great app, but I can't try your new version until my 36 hour encode gets finished!

Any possibilty to get an aspect ratio right click off the preview? Some of my vids are anamorpherric.

AvsP is a huge help. It's brilliant. A bit disconcerting while zooming in and out and switching
between tabs the way it sort of burgers the workspace or doesn't resize the sliders, but you know
that was the old version, where you said the new one has fixes to the preview... so I must try!

Good vibes on this thread. Ok, thanks. :)

[mkanel]

And don't worry about my workload, I'm always interested in squashing bugs.

OK, one more. When using Replace... (Ctrl-H) Replace All works fine but Replace, replaces not the highlighted text but the next instance of the text. So if you want to replace most instances of "ZZZ" with "YYY" if you click on Find Next it will highlight the first instance of "ZZZ" when you click Replace it replaces the NEXT instance not the highlighted instance of "ZZZ" with "YYY". I think I just said the same thing two times, that's my own bug. :)

Thanks again. Mike.

[qwerpoi]

Any possibilty to get an aspect ratio right click off the preview? Some of my vids are anamorpherric.
Um, maybe. Any resize like that makes for an unfair comparison (resizing filters the image), so in my opinion it's best to work with your scripts in its native aspect ratio. If you wanted to see your script in action you could always use the external preview and set the appropriate aspect ratio with your media player. Or you can resize your script with AviSynth itself - any resize my program would do would likely be of lower quality. I'll still give it some thought, though.

AvsP is a huge help. It's brilliant. A bit disconcerting while zooming in and out and switching
between tabs the way it sort of burgers the workspace or doesn't resize the sliders, but you know
that was the old version, where you said the new one has fixes to the preview... so I must try!
Be sure to report back if there are any such problems with the new version, I'm still working on making all that layout code as robust as possible.

OK, one more. When using Replace... (Ctrl-H) Replace All works fine but Replace, replaces not the highlighted text but the next instance of the text.
Good catch! I took a look at my find and replace code, it was a little sloppy (written a loong time ago), I fixed the replace issue, it'll be in the next release.

[honai]

Whoa, great app!

You could make it a little bit more HD-friendly (where screen estate to the right and bottom of the preview pane is limited) by positioning the sliders not to the right of the preview window, but to the right of the code section in a separate pane, preferably resizable.

[qwerpoi]

Whoa, great app!

You could make it a little bit more HD-friendly (where screen estate to the right and bottom of the preview pane is limited) by positioning the sliders not to the right of the preview window, but to the right of the code section in a separate pane, preferably resizable.
It's a good suggestion, but unfortunately one that I probably won't follow up on any time soon. I am aware that the current layout of all the elements is not optimal, particularly for widescreen videos, but the layout code has gotten to be a huge mess, it wouldn't be easy to change. I kind of like the way things are, but ultimately as you say there should be options to make the sliders and/or video preview separate dockable windows.

[krisq]

I've got a stupid question :). Is there a shortcut to switch between text editor and video window?
BTW modulo for sliders is working perfectly :D

[qwerpoi]

I've got a stupid question :). Is there a shortcut to switch between text editor and video window?
Umm, I guess not directly. You can use the Shift-F5 shortcut to hide the preview which automatically shifts focus to the text editor, and from there you can use F5 to show the preview. Is that what you need?

[krisq]

It's a little inconvenient solution for me. Would be a problem to add such a shortcut? Sometimes I need to jump few frames and make a correction in the script and again jump few frames and I hate to use the mouse for this.

[qwerpoi]

New version 1.1.6, mostly a bugfix version, get it from the download page (http://www.avisynth.org/qwerpoi/Download.html). Here are the changes:

* added ability to specify a file or url for AviSynth help (suggested by Fizick)

* added shortcut Shift-Tab to switch focus between the text and video (suggested by krisq)

> fixed bug with one frame long video (thanks mkanel)

> fixed read from avsfilters.txt feature (thanks mkanel)

> fixed minor bug with Replace and Find Next (thanks mkanel)

> cleaned up calltip and argument highlight code to be more robust

One other thing to note is that I added a section on the website about using arbitrary lists with user sliders, you can read about it here (http://www.avisynth.org/qwerpoi/UserSliders.html#sliders-for-non-numbers). Basically it goes over how to use AviSynth scripting to do stuff like make a slider which switches between a list of strings. This is the example script from the website:
AVISource("C:\test.avi")
Histogram(Select([<"HistogramMode", 0, 2, 0>], "classic", "levels", "color"))
This script has a user slider which goes between 0, 1, and 2, and uses AviSynth's Select function to map those values to the strings "classic", "levels", and "color" (which are several possible values for the mode argument for Histogram). Again, you can read about it in a little more detail at the webpage (http://www.avisynth.org/qwerpoi/UserSliders.html#sliders-for-non-numbers).

And for Team AvsP Translators :D , be aware that there are about 5 new messages to translate, and zero "no longer used" messages.

[krisq]

w00t! Amazing, thanks :D

[Henrikx]

Update German translation to AvsP 1.1.6

[niiyan]

This feature is already there, the text box on the video controls at the bottom of the program works almost exactly like VirtualDub's "Jump to frame" window. Just type in a frame or time and hit enter.

I didn't notice that feature. It has been written in your online documents, but I haven't read it yet... I'm sorry. Next time, I will read your docs before I ask you.

And here is my apology :)
http://niiyan.net/?AvsP (update Japanese translation)

[qwerpoi]

w00t! Amazing, thanks :D
No problem. Actualy, I'm finding that Shift-Tab shortcut to be pretty handy myself, so thanks for bringing it up. I'll update the website to mention it when I get the chance.

Update German translation to AvsP 1.1.6
Cool, fast as always!

I didn't notice that feature. It has been written in your online documents, but I haven't read it yet... I'm sorry. Next time, I will read your docs before I ask you.

And here is my apology :)
http://niiyan.net/?AvsP (update Japanese translation)
Don't worry about it, I'm always happy to answer questions (if for no other reason than a free bump for my thread :) ). The online docs are not 100% complete, so any question is valid. And thanks for the speedy translation!

[krisq]

another idea: aspect ratio information on the status bar would be handy :)

[Champs]

@qwerpoi
hi, first of all thank you for this awesome Avs script editor/previewer! So awesome that I have almost completely stopped using VDubMod for my editing/previewing task.

A few feature requests or something of that sort...

1)
Regarding the "Ctrl+G jump-to-frame" feature request made by niiyan, I have been using the box at the bottom, but my request would be to have a shortcut key(s) to shift focus (cursor/prompt) into the box. IMHO what's nice about "Ctrl+G" feature of VDub/AviUtl/MPC is that the cursor is already in the box so no need to move and click a mouse to set a prompt there. If you could assign "Ctrl+G" to such a task that'd be great as I'm so used to it, but since you just added the Shift-Tab shortcut to switch focus b/w text editor and video pane, maybe a similar key combo would be aesthetically preferred by you, I don't know...in any case having a shortcut key will be very helpful.

2)
Speaking of Shift-Tab, I have been using Ctrl+Tab to switch tabs and this is a nice feature, but also find it very difficult to press (I've been trying to use my left pinky and wedding finger), I may be the only one w/ this difficulty, but may I possibly ask for a change to another key-combo that's easier to press?
(I may find a similar difficulty w/ Shift-Tab but this combo's much easier)

3)
When I try to replace all occurences of a single word/phrase by another using Ctrl+H, I can do so w/o problems, but some sort of an error message always pops up. I don't think it's suposed to.

4)
If I have a script like:

PLUGIN_PATH = String("C:\Program Files\AviSynth 2.5.6\otherPlugins")
Loadplugin(PLUGIN_PATH + "\degrainmedian.dll")
Loadplugin(PLUGIN_PATH + "\vaguedenoiser.dll")
...

then the coloring scheme works fine, but if I change this to

PLUGIN_PATH = String("C:\Program Files\AviSynth 2.5.6\otherPlugins\")
Loadplugin(PLUGIN_PATH + "degrainmedian.dll")
Loadplugin(PLUGIN_PATH + "vaguedenoiser.dll")
...

then all the function calls (e.g. Loadplugin, Import, Mpeg2source etc) and comment lines are colored wrongly (purple by default setting). As shown above, I'm not having a problem, and I don't know if it can even be called a bug, but I just wanted to report it to you, as it may not be an intended outcome.

Regards.