New AviSynth tool - AvsP v1.4.0 (6/5/07) [Archive] - Page 5

qwerpoi

27th September 2006, 20:42

another idea: aspect ratio information on the status bar would be handy :)
I should be able to do it, but it would be a little tricky. In other words it's trivial to show the decimal width divided by height, but I assume that people would want to see 16:9 or 4:3 when appropriate. I'm not much of an aspect ratio guru, so (a) I don't know all the "key" aspect ratios, and (b) I don't know how much tolerance is acceptable (ie, does 1.35 still count as 4:3). If someone can point out a link, great, otherwise I'll try and implement it showing the width/height decimal only.

Edit: Looks like doom9's aspect ratio page had all the info I needed. I implemented the feature, great stuff, especially handy with the crop editor! I'll try to get the new release out in a couple of days.

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.
Hah, I was thinking the same thing. I'll use Ctrl-G since everyone who uses AviSynth is used to vdub. It'll be in the next release.

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)
Hmm, Ctrl-Tab and Ctrl-Shift-Tab are the standard shortcuts for tabbed programs (Firefox, um, K-Meleon, uh, I can't think of any other examples at the moment :) ). If you want to suggest another set of shortcuts (you'll have to peruse through the menus to see what's already being used), or if you can find other programs which use different shortcuts, I'm willing to listen. By the way, if the video preview is visible, there are a couple of more keyboard shortcuts available, read more here (http://www.avisynth.org/qwerpoi/Video.html#comparing-multiple-scripts).

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.
If you can see the error message (most of the time it will pop up in a separate window), paste the exact message here, I'll get on it.

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.
The short answer is don't end any string with a backslash, and it will highlight correctly. The long answer is that I didn't write the code to colorize the text, I borrowed code that was written to colorize a different progamming language (Octave), so you'll end up seeing weird issues like this. I guess this will have to be bumped up on my to-do list :scared: .

I have a runtime issue with 1.1.6. I unzip a fresh copy.
Avsp is installed in: C:\Program Files (x86)\AvsP
Avisynth is in: C:\Program Files\AviSynth 2.5.7RC1
I click Options -> Settings...
I click the OK button.
I get an error popup:
I can't see the attachment yet (it's pending approval), when I can I'll get on it.

Edit: I think I know what the problem is, it's a stupid mistake on my part. The problem is with the "AviSynth help file/url:" entry in the "General" tab, replace %avisynthdir% in that text box with your actual AviSynth directory (in your case, C:\Program Files\AviSynth 2.5.7RC1). You should be able to hit OK from now on with no problems. I'll get that fixed by the next release.

nibbles

27th September 2006, 21:06

Yes that was this issue. Thanks for checking into it. Also I wanted to mention
that the preview pane is working better for me in 1.1.6.

Fizick

27th September 2006, 21:37

I can not save to avi with avs2avi in localized Russian version 1.1.6.
english version works fine.

qwerpoi

28th September 2006, 00:29

Also I wanted to mention
that the preview pane is working better for me in 1.1.6.
Whew! Thanks for letting me know. I'm sure that there still are some issues, but I'll be happy so long as the preview window behaves as expected under reasonable conditions.

I can not save to avi with avs2avi in localized Russian version 1.1.6.
english version works fine.
Aah, the problem is caused by the fact that I failed to translate one of the messages, I'll fix right away. I also noticed that there's quite a few messages in the avs2avi that I didn't make translatable, so that will be in the new release as well.

Seed

28th September 2006, 06:31

If you want to suggest another set of shortcuts (you'll have to peruse through the menus to see what's already being used), or if you can find other programs which use different shortcuts, I'm willing to listen.

I'm not Champs, but just a suggestion. Maxthon browser (a popular tabbed browser based on IE engine) uses F2 for switching tabs from right-to-left direction and F3 for left-to-right direction.

BTW, a very useful program, and thanks for all the effort.

qwerpoi

28th September 2006, 07:43

I'm not Champs, but just a suggestion. Maxthon browser (a popular tabbed browser based on IE engine) uses F2 for switching tabs from right-to-left direction and F3 for left-to-right direction.

BTW, a very useful program, and thanks for all the effort.
Ah, Maxthon, I used to use that program (back in the day when it was called MyIE2). I eventually switched to Firefox and then to K-Meleon (sort of a lightweight version of Firefox), but in many ways it sometimes feels like Maxthon does it better.

Anyway, back on topic, using F2 and F3 for tab switching sounds reasonable, but I've already reserved F1 through F4 for the first four macros. I did this because theoretically you would write a macro that you couldn't live without, or a macro that requires a lot of activation (the insanely complex "Manual Telecide" macro for example), and you would want to be able to access it as fast as possible. This already screws with the standard F3 shortcut for "Find next" which you'll find on nearly every program (although I guess not on Maxthon or ie), which I changed to Ctrl-Shift-F, which is kind of ugly.

So. I'm willing to change things around, let's say macros get Ctrl-F1 through Ctrl-F4, then F2 can be used to switch to the previous tab, F3 would switch to the next. I could leave the Ctrl-Tab and Ctrl-Shift-Tab shortcuts alone so as not to upset the Firefox/Foobar/every tabbed program in existence :) crowd. But I'm not going to change anything until more people chime in, either with approval or other possible shortcuts. Until then, you'll just have to live with the standard shortcuts, or spend more time with your mouse (shudder).

Henrikx

28th September 2006, 08:26

Aah, the problem is caused by the fact that I failed to translate one of the messages...I copied from the beginning the 6 new entries from 1.1.6 to 1.1.5. German Version works fine.

krisq

28th September 2006, 10:12

I should be able to do it, but it would be a little tricky. In other words it's trivial to show the decimal width divided by height, but I assume that people would want to see 16:9 or 4:3 when appropriate. I'm not much of an aspect ratio guru, so (a) I don't know all the "key" aspect ratios, and (b) I don't know how much tolerance is acceptable (ie, does 1.35 still count as 4:3). If someone can point out a link, great, otherwise I'll try and implement it showing the width/height decimal only.

Edit: Looks like doom9's aspect ratio page had all the info I needed. I implemented the feature, great stuff, especially handy with the crop editor! I'll try to get the new release out in a couple of days.

Actually, width/height decimal was extacly what I've had on my mind but hey, if you did it the better way... I won't argue with ya :D
Cheers.

[EDIT]
I think checkboxes for section toggling should be hierarchicly in the same place as in the script.

AVISource("c:\Download\movie.avi")
ConvertToYUY2()

HDRAgc (coef_gain=[<"HDR Gain", 0.0, 3.0, 1.0>], coef_sat=[<"HDR Saturation", 0.0, 3.0, 1.0>])

LanczosResize([<"Lanczos Width % 16", 352, 720, 640>],[<"Lanczos Height % 16", 352, 720, 480>])

In this case instead of:

Toggle HDR
Toggle Lanczos
4 x sliders

I would expect something like this:

Toggle HDR
2 x sliders
Toggle Lanczos
2 x sliders

qwerpoi

28th September 2006, 19:47

...I copied from the beginning the 6 new entries from 1.1.6 to 1.1.5. German Version works fine.
The dialog box shows up, but nothing happens when you hit the "Run" button if you translate the label to something else. It's a small mistake on my part, the code is supposed to check the translated label instead of "Run".

I think checkboxes for section toggling should be hierarchicly in the same place as in the script.

AVISource("c:\Download\movie.avi")
ConvertToYUY2()

HDRAgc (coef_gain=[<"HDR Gain", 0.0, 3.0, 1.0>], coef_sat=[<"HDR Saturation", 0.0, 3.0, 1.0>])

LanczosResize([<"Lanczos Width % 16", 352, 720, 640>],[<"Lanczos Height % 16", 352, 720, 480>])

In this case instead of:

Toggle HDR
Toggle Lanczos
4 x sliders

I would expect something like this:

Toggle HDR
2 x sliders
Toggle Lanczos
2 x sliders
Yeowch, that would be pretty difficult for various reasons, the primary one being that I would have to rewrite my layout code, which I just got to a nearly stable state. I'd follow up on your request if it were easy, but since it's not, and since I prefer using multiple tabs over toggle sections, I'm going to leave things as is, at least for now. Well, if other people feel the same way as you, I might do something about it then.

PS - I gave myself an avatar to help distinguish my posts in this thread. 5 style points to the first person who can tell me where it's from :D

krisq

28th September 2006, 20:18

No problem, I thought it was a simple thing to do :D I'll start to get use to it then :)

Zarxrax

28th September 2006, 21:02

Wow, I just tried AvsP and I absolutely love it! I've never even considered using anything besides notepad, but this has definately become my default avs editor!

I've got a couple suggestions for it.
1. Custom keyboard shortcuts. Some of the keyboard shortcuts seem strange to me, or some features I might use may not have a shortcut, so it would be nice if they were customizable.
2. Add an option to update the preview each time you change a line and then move focus to a different line. As you make changes to the script, it will automatically update the preview, so you dont have to keep pressing f5 to see the change.
3. Try to catch script errors in AvsP. If there is an error in the syntax, highlight the line, and maybe have a popup that tells the exact error. Instead of showing the error in the video preview, it can just show you right in the text editor. This feature would go a long ways towards making idea #2 actually usable. It would also be extremely nice to get some realtime feedback as you are typing. For instance, if I forget a comma somewhere, it would be nice if this could be highlighted immediately as im typing.
4. On the popup that shows the filter parameters, it would be nice if you could just click on certain parameters to add them to your script (and also let this be done via keyboard shortcuts).
For example, if I type the tweak command, the popup will show all the various parameters such as hue, sat, bright, etc. If you were to click on "sat" it would insert "sat=" into your script. As for the help function that it currently goes to when you click, I suppose that could be moved to the right-click (whch currently seems to give an error message!).
5. Double-click a tab to duplicate it. This will make comparing two scripts much quicker, as it would save you the trouble of making a new tab, going back to the original tab, copying, going back to the new tab, paste...

That's all the suggestions I've got for now. Thanks so much for this wonderful program!

qwerpoi

28th September 2006, 22:05

Wow, I just tried AvsP and I absolutely love it! I've never even considered using anything besides notepad, but this has definately become my default avs editor!
Excellent! My goal is to get all the die-hard notepad/virtualdub people to use AvsP, nice to see I'm on the right track.

1. Custom keyboard shortcuts. Some of the keyboard shortcuts seem strange to me, or some features I might use may not have a shortcut, so it would be nice if they were customizable.
A very good request, a fairly difficult request, for me at least. It's definitely on my to-do list - in the meantime, let me know which shortcuts are strange or which features require shortcuts and I'll try to accommodate.

2. Add an option to update the preview each time you change a line and then move focus to a different line. As you make changes to the script, it will automatically update the preview, so you dont have to keep pressing f5 to see the change.
Hmm, not sure how many people will use this, I imagine you'll get a lot of errors as you build your script line by line. But I'll try and make it an option.

3. Try to catch script errors in AvsP. If there is an error in the syntax, highlight the line, and maybe have a popup that tells the exact error. Instead of showing the error in the video preview, it can just show you right in the text editor. This feature would go a long ways towards making idea #2 actually usable. It would also be extremely nice to get some realtime feedback as you are typing. For instance, if I forget a comma somewhere, it would be nice if this could be highlighted immediately as im typing.
Ah, catching errors like vdubmod does is impossible for AvsP at the moment. AvsP is written in Python, not c++, so it actually doesn't communicate with AviSynth at all, it just makes .avs scripts. Obviously that's not to say that it's impossible, but it would require writing an AviSynth wrapper dll that's callable by Python's ctypes (something I've played around with a bit with little success). Future versions of AvsP (AvsP 3.0? :) ) really should have this level of communication available, but currently it works in a simplified fashion.

4. On the popup that shows the filter parameters, it would be nice if you could just click on certain parameters to add them to your script (and also let this be done via keyboard shortcuts).
For example, if I type the tweak command, the popup will show all the various parameters such as hue, sat, bright, etc. If you were to click on "sat" it would insert "sat=" into your script. As for the help function that it currently goes to when you click, I suppose that could be moved to the right-click (whch currently seems to give an error message!).
Huh. An interesting idea, but I don't think the editing component I'm using (scintilla) has a way to detect which argument you clicked on. I'll look into it a bit further. Also thanks letting me know about that right-click error, I'll fix it right away!

5. Double-click a tab to duplicate it. This will make comparing two scripts much quicker, as it would save you the trouble of making a new tab, going back to the original tab, copying, going back to the new tab, paste...
Now this I can do, a great suggestion. Keep in mind there are a couple of shortcuts already, adding a new tab already copies any selected text from the current tab (making it possible to duplicate a script with keyboard shortcuts entirely, Ctrl-A then Ctrl-N), also you can drag-and-drop text in the tab area to create a new tab with that text. But your suggestion is even faster, so it'll be in the next release. Thanks for all the feedback.

Zarxrax

28th September 2006, 23:10

Ah, I didn't know about the Ctrl+A, Ctrl+N trick.

As for the syntax checking, it should be possible to do a lot of it without reading errors directly from avisynth. Since I would assume AvsP is quite aware of what constitutes proper syntax, it should be possible to determine when you type something that blatantly violates the syntax. If you have ever used Microsoft Visual Studio, this is the kind of thing I am talking about--whenever you type something wrong, it will underline it with a squiggly line. Of course, I'm not sure how much work something like that would be. Maybe it's not feasible.

doxville

30th September 2006, 23:39

First of all: A big THANKS for the great tool!!
Excellent! My goal is to get all the die-hard notepad/virtualdub people to use AvsP, nice to see I'm on the right track.I am already very close to switch over to AvsP completely because of its great features, BUT...
I miss something like VDubMod's 'Cut' and 'Insert Frameset As Trims' function. With VDubMod, I find it very simple to cut out the commercial breaks out of TV-captures, and after that, with a simple click, you get the appropriate 'trim(...) ++ trim(...) ++ trim(...)' line for the script.
Would it be possible (or is it already planned) to implant this feature? This would also mean, the preview-function would have to be changed a little, so that the preview picture would be updated much more often than at the moment (not just at the position where you stop the slider, but all the way while you scroll the slider), to make it easier to find the right part of the movie.

Still, great, great tool, please keep up the excellent work!! :thanks:

foxyshadis

1st October 2006, 04:44

Well, avsfilmcutter does that very well - that's its main purpose in life. It'd be neat is avsp got it, but at least there's a tool around now.

qwerpoi

1st October 2006, 06:20

Sorry about not getting the new release out yet, I'm currently working on making keyboard shortcuts customizable, which should make some of you out there very happy. It'll probably be out sometime soon after the weekend.

As for the syntax checking, it should be possible to do a lot of it without reading errors directly from avisynth. Since I would assume AvsP is quite aware of what constitutes proper syntax, it should be possible to determine when you type something that blatantly violates the syntax. If you have ever used Microsoft Visual Studio, this is the kind of thing I am talking about--whenever you type something wrong, it will underline it with a squiggly line. Of course, I'm not sure how much work something like that would be. Maybe it's not feasible.
I'm not sure how much work it is either, but I'm guessing it's difficult. I think Microsoft Visual Studio can pull this stuff off with the C++ language because it's statically typed (ie, you must declare "int x" before saying "x=5", etc). The AviSynth language does not have this strict structure, which makes it more difficult to determine "on-the-fly" syntax errors. So my gut feeling is that to pull this off with the AviSynth language would be a lot of work with a lot of heuristics. Of course I could be wrong, anybody with any thoughts on the subject are welcome to bring it up.
I miss something like VDubMod's 'Cut' and 'Insert Frameset As Trims' function. With VDubMod, I find it very simple to cut out the commercial breaks out of TV-captures, and after that, with a simple click, you get the appropriate 'trim(...) ++ trim(...) ++ trim(...)' line for the script.
Would it be possible (or is it already planned) to implant this feature? This would also mean, the preview-function would have to be changed a little, so that the preview picture would be updated much more often than at the moment (not just at the position where you stop the slider, but all the way while you scroll the slider), to make it easier to find the right part of the movie.
Interesting request, I've never used vdubmod's script editor that much. I'll see what I can do, although the way I end up implementing it might be a bit different than vdubmod's method. As far as updating the picture while dragging, I'll try to make that an option. I find updating on release instead is more graceful (ever hear the crunching noise when you're dragging around in a large video in vdub?), and you can always use the keyboard shortcuts to fine tune positions (up/down skips by a second, pgup/pgdn skips by a minute), but in the end it's user preference.

Ebobtron

1st October 2006, 09:29

Well, avsfilmcutter does that very well - that's its main purpose in life. It'd be neat is avsp got it, but at least there's a tool around now.

Thanks foxy, wasn't sure anyone around here liked it.

I have AvsP v1.1.6 programmed in a tool button on my version of FilmCutter, open a script or name a new one and click the AvsP icon. When AvsP is done with the script just close and you are back, edited script loaded.

sorry qwerpoi, haven’t clicked it to much. But when I do the video preview jumps off the bottom of my screen. Mine is only 480 p high.

I am sure you are aware of it. But I must applaud your work on the filter parameter dialog box (and the rest of your work), coding all of that must have been a pain.

If I enhance avsFilmCutter's command line switches to include play. I could click AvsP from FilmCutter and then assign FilmCutter as the external player from your program.

Would that violate the looping rules? :)

I need some time off. ;)

Ebt

edman

1st October 2006, 14:01

Hi,
how do i make it show a preview of my source?
If i load the Plugins and the source it just shows me a big greyed out window. I can move the slider and AvsP counts the frames but no picture appears. When i try to zoom in the preview window just becomes black. Loading the Script in VD works fine. I'm using v.1.1.6.
Here's the script:

LoadPlugin("d:\encode\dgmpgdec148\DGDecode.dll")
LoadPlugin("d:\encode\dgmpgdec148\mpasource_25_dll_20031214\mpasource.dll")
MPEG2Source("d:\encode\alpha.d2v",cpu=3)
MPASource("d:\encode\alpha - DELAY -8ms.mpa")
AudioDub(video,audio)

thx

Ebobtron

1st October 2006, 14:19

edman

1st October 2006, 14:34

the script you show is not going to work at all it does work, i get no errors opening it in vd or mplayer.
try
video = MPEG2Source("d:\encode\alpha.d2v",cpu=3)
audio = MPASource("d:\encode\alpha - DELAY -8ms.mpa")
AudioDub(video,audio)

Same result, no difference at all

foxyshadis

1st October 2006, 15:45

Well, you anonymized the script or something, if you got no errors, because you removed a few required variable definitions from what you posted.

Anyway, no idea, since audiodub works fine here. But if you can replicate it with a few seconds of the video, it'd be useful to post it, or if you find out that it only happens to things of a certain length.

Back to avsP. The preview's gotten pretty nice, and I certainly have no problem with following its message to the offending line. You'll need a C++ hook to get any deeper. Three minor feature requests: Tab inserts actual tab option; tabstop length; and use .avst as templates. Bug fix: .avsi should not be a template. (When opening an avsi, working, and saving, it will save to an avs of the same name. Buggy behavior, but it'd be great to do the same thing for a "template".) Oh yeah, editplus has the neat feature of automatically saving your session when you close and reloading everything when you close. It's very handy, I hardly ever use manual sessions because of it, and it might be the #1 reason I use editplus.

Since you have binary config files, maybe a place in the options where you can open up a list of everything and its configuration would be nice, sort of like mozilla's about:config. That way you don't have to give gui space to every option.

nibbles

1st October 2006, 19:11

I like the idea of about:config, though I find Azureus preferences
easier to work with because it has decent groupings. The
tabbed options settings that AvsP uses now work well I figure.

I don't need syntax checking as I type. I would rather
concentrate than be distracted with things coming at me.
I also think the line has to be drawn somewhere at writing code
vs dropping objects from your toolbox onto the script window.
I'm not sure where to draw that line or what the future plans
for AvsP are, but it seems to be mostly text now. I think you
open a Pandora's box when you go down the road of syntax
checking or object centered creation. Every time a filter or
some piece of code is changed, the author somehow has to
keep track of those and code for them.

The idea of in/out markers that yield trim() commands is fantastic!

Requests:
How about an (x,y) readout of where the mouse is?
How about a way to bookmark a line in your script?
Then you could Ctrl+. or Ctrl+, your way to each marker.
Maybe create a framework for plugins? ;)
That way, no more Ebobtron looping code, heh. :)

EDIT: How about getting AvsP listed on Avisynth website?
http://www.avisynth.org/Section+1%3A+About+AviSynth#q1.20

foxyshadis

1st October 2006, 21:20

Oh, here's one that I have no idea how complex would be to implement: a syntax like

LimitedSharpen()
[Sharpen else]
Sharpen()

As a way to compare two options without needing two groups, just a check on and off. Not too important, it just came to mind.

Does anyone have half-finished custom syntax files I can start from? Otherwise I'll just start on everything.

tsp

1st October 2006, 22:58

qwerpoi: Very nice to see that avsp progress as fast. About the calltips could you make avsp a little more intelligent about detecting when the first argument is defined with filters that has a clip as the first argument. Like this script:

blackness()
info()

the calltip for blackness bolds the second argument (length) instead of the first argument (clip1) because blackness is on the first line the first argument should be in bold instead.
The first argument should be used instead of the second for filters that takes a clip as the first argument when:
1)it's the first filter on a line (detect if the filter is before a . )
and
a)it's on the first line in the script
or
b) a } is on the line before
or
c) a variable is assigned on the line before (detect if the first non alfanumeric character is a = )
empty lines does not count

and I'm soon done with the dll to get the filter arguments (currently I can get the autoloaded plugin arguments for all version of avisynth 2.5 and import them into python using ctypes)

foxyshadis

1st October 2006, 23:09

Whoa, I just noticed a huge VM leak. Not a real memory leak, but after a few hundred taps on the toggles the access violations start, and pretty soon after that it hits 2GB and everything goes... weird, man. Haven't closed it yet just because I'm trying to get it to crash on its own. :p I suppose I could use /3GB in the meantime.

and I'm soon done with the dll to get the filter arguments (currently I can get the autoloaded plugin arguments for all version of avisynth 2.5 and import them into python using ctypes)
Does this include .avsi, or just dlls? Thanks for it!

edman

1st October 2006, 23:52

video = MPEG2Source("d:\encode\alpha.d2v",cpu=3)
audio = MPASource("d:\encode\alpha - DELAY -8ms.mpa")
AudioDub(video,audio)

This works
[CODE]
video = DirectShowSource("d:\encode\alpha.mpv")

qwerpoi

1st October 2006, 23:53

Three minor feature requests: Tab inserts actual tab option; tabstop length; and use .avst as templates. Bug fix: .avsi should not be a template. (When opening an avsi, working, and saving, it will save to an avs of the same name. Buggy behavior, but it'd be great to do the same thing for a "template".) Oh yeah, editplus has the neat feature of automatically saving your session when you close and reloading everything when you close. It's very handy, I hardly ever use manual sessions because of it, and it might be the #1 reason I use editplus.
I'll try and get the tab options, the avsi bugfix, and the save session on exit feature in the upcoming release.

Edit: I forgot about the template request. I'm not sure what you mean by using .avst templates, got confused when you said templates should be like the avsi bug. Could be I'm not thinking straight, so please elaborate, thanks.

Since you have binary config files, maybe a place in the options where you can open up a list of everything and its configuration would be nice, sort of like mozilla's about:config. That way you don't have to give gui space to every option.
My gut feeling is that the about:config interface is a bit daunting for beginners (I would even go so far as to say an ini file is daunting for beginners). If at all possible I'd like to keep the options configurable by dialogs, which offers explanations and validation. It's trivial for me to add a new option, since I wrote a small framework to automatically construct the options dialog box given a list data structure. But of course it sucks when the number of options gets so large that dozens of tabs are required, so it's still something to think about.

Requests:
How about an (x,y) readout of where the mouse is?
How about a way to bookmark a line in your script?
Then you could Ctrl+. or Ctrl+, your way to each marker.
Maybe create a framework for plugins? ;)
That way, no more Ebobtron looping code, heh. :)
The mouse xy position I could do, although I'm not sure how useful it is in AviSynth. I'm not sure it will be in the upcoming release (my status bar message is getting stuffed :) ).

Bookmarking script lines is a good idea, it would be a bit of work for me (adding new margin and marker code). I'll take a look into it.

As far as plugins go, my original intent was for people to be able to write python/wxpython scripts which would get imported from the "Tools" subdirectory (doesn't currently exist). That's why there's a "Tools" menu in AvsP with nearly nothing in it. I'll probably put this together in the future, but I'm not sure how many people would use it. Keep in mind that AvsP has a very complete macro language (http://www.avisynth.org/qwerpoi/Macros.html), which will probably suit many purposes in the meantime.

EDIT: How about getting AvsP listed on Avisynth website?
Yeah, and how does one get a mention on doom9's main page? I figure I haven't really "made it" until AvsP is up there :)

Oh, here's one that I have no idea how complex would be to implement: a syntax like

LimitedSharpen()
[Sharpen else]
Sharpen()

As a way to compare two options without needing two groups, just a check on and off.
Off the top of my head it seems difficult, but I'll think about it some more.

qwerpoi: Very nice to see that avsp progress as fast. About the calltips could you make avsp a little more intelligent about detecting when the first argument is defined with filters that has a clip as the first argument. Like this script:

blackness()
info()

the calltip for blackness bolds the second argument (length) instead of the first argument (clip1) because blackness is on the first line the first argument should be in bold instead.
The first argument should be used instead of the second for filters that takes a clip as the first argument when:
1)it's the first filter on a line (detect if the filter is before a . )
and
a)it's on the first line in the script
or
b) a } is on the line before
or
c) a variable is assigned on the line before (detect if the first non alfanumeric character is a = )
empty lines does not count
I'll try and do this for the upcoming release.

and I'm soon done with the dll to get the filter arguments (currently I can get the autoloaded plugin arguments for all version of avisynth 2.5 and import them into python using ctypes)
Great news! Thanks for testing it out with python!

Whoa, I just noticed a huge VM leak. Not a real memory leak, but after a few hundred taps on the toggles the access violations start, and pretty soon after that it hits 2GB and everything goes... weird, man. Haven't closed it yet just because I'm trying to get it to crash on its own. :p I suppose I could use /3GB in the meantime.
Yeah, it could be my fault :( , I don't know how bulletproof my avi code is. Since python has no direct way to read AVI frames, I wrote a class using python's ctypes to call up AVIFile functions from avifil32.dll. Now I'm no AVIFile guru, I just read the couple of tutorials available on the net to get it working. I guess the best thing to do is to release my source (sigh), hopefully some developer types can take a look at it and make sure there's no serious problems. I'm not sure I'll release the sources in the upcoming release, so if anyone wants to take a look at my avi code right away (it's less than 300 lines), pm me.

foxyshadis

2nd October 2006, 03:34

I just made up "avst" for templates, but I just realized all you need to do is set it to read-only, so the program can pop up a box asking where to save it instead. (Right now it's just an error.)

The other ones aren't really important, it's pretty cool how it is now, for sure.

Fizick

2nd October 2006, 04:54

qwerpoi

2nd October 2006, 09:24

New version 1.2.0, download it here (http://www.avisynth.org/qwerpoi/Download.html). This is possibly the biggest changelog yet:

* customizable keyboard shortcuts (suggested by Zarxrax)

* aspect ratio info on status bar in video mode (suggested by krisq)

* added option for constant video update when dragging (suggested by doxville)

* added option for line-by-line video preview update (suggested by Zarxrax)

* center window when it goes off the screen (suggested by Ebobtron)

* added ability to mark and add trim selections (suggested by doxville)

* make shortcut Ctrl-G highlight frame text ctrl (suggested by Champs)

* copy a script by double-clicking the tab (suggested by Zarxrax)

* added options for using text tabs, tab length (suggested by foxyshadis)

* auto save session on exit, load on startup if no args (suggested by foxyshadis)

* minor improvements to calltip argument highlight code (suggested by tsp)

* minor improvements to avs2avi frontend

> fixed bug in "Options -> Settings" dialog (thanks nibbles)

> fixed bug with avs2avi frontend and translation (thanks Fizick)

> fixed error when right-clicking a popup tooltip (thanks Zarxrax)

> fixed bug saving .avsi file with .avs extension (thanks foxyshadis)

The biggest change is that you can customize all the keyboard shortcuts with a very easy to use dialog box, just click on "Options -> Configure shortcuts...". Because of this option, I changed some of the shortcuts around to be more "standard", and the first 4 macros no longer get the keyboard shortcuts F1 through F4 (you can always add the shortcuts yourself, though).

Another change which requires a bit of discussion is the ability to add a Trim sequence based off of video frame bookmarks. This is essentially a feature to satisfy people used to vdubmod's script editor. By clicking "Edit -> Insert bookmark Trims" (keyboard shortcut Ctrl-I), AvsP will insert a sequence of Trim commands into your script based on the bookmarks you have set. It goes through each pair of bookmarks, treating each pair as a section of the video to remove. So if you bookmarks are "1000, 2000, 4000, 5000", then the Trim sequence would look something like this:
Trim(0, 999) ++ Trim(2000, 3999) ++ Trim(5000, 23493)
This is equivalent to cutting out frames 1000 to 1999 and frames 4000 to 4999 (of course AviSynth does not have a Cut() function, hence the sequence of Trim commands).

There is an option for line-by-line video updating, it's off by default, you can turn it on in "Options -> Program settings..." under the "Video" tab. When this option is turned on, every time the text cursor moves to a different line the video preview is updated automatically. Of course this will lead to a lot of AviSynth error videos when writing complex scripts, but it may be a handy time saver when doing relatively simple scripting (which is arguably most of the time).

Anyway, the next thing I need to work on is getting the online documentation caught up with the program, it's gotten a fair bit out of date. As always, let me know of any problems you encounter with the new version.

Note to translators: There were a LOT of changed messages, so updating the translation might be more difficult this time. I've sent each of you a pm with some info.

foxyshadis

2nd October 2006, 09:58

I'm in awe. It works so well and smoothly, like magic. And only a few weeks ago it was new! It's always nice to see promising software fulfilled. :D

check

2nd October 2006, 10:22

I started using this yesterday, I'm a convert too - and it even supports macros in the only scripting language I've spent more than a week learning! (not that I can use it :P)

How hard would it be to include a 'recent avs files' file menu item? Very useful for me, as I keep all my different project all over the place depending on what drive has the most gigs free ;). The ability for it to auto session save when you quit and have that ready to load would be similarly excellent.

qwerpoi

2nd October 2006, 11:10

I'm in awe. It works so well and smoothly, like magic. And only a few weeks ago it was new! It's always nice to see promising software fulfilled. :D
Thanks :). I'm really pleased by the response the program's gotten (I can brag that the program's been released for less than a month and already it's been translated in three different languages), but I really can't take all the credit - big props go to the AviSynth developers and doom9's forum (and of course the diligent translators niiyan, Fizick, and Henrikx). And keep in mind that although I released the program about a month ago, I've been developing it for personal use for more than 2 years, I rewrote the whole thing from scratch about three times, using several gui frameworks until I was happy (I'm a bit of a perfectionist when it comes to certain things :p ).

I started using this yesterday, I'm a convert too - and it even supports macros in the only scripting language I've spent more than a week learning! (not that I can use it :P)
Well, when you get comfortable with Python, take a detailed look at the macros that come with the program - the "Manual Telecide" macro is pretty insane! It's basically my proof of concept of what kind of detail and interaction you can achieve with the macros. I've never used YATTA, but I imagine the core functionality (building the Telecide override file with a gui) is the same.

Edit: Well, after doing some quick reading about YATTA, I guess the "Manual Telecide" macro is nothing like it :( . It seems YATTA is geared for finding appropriate thresholds through gui feedback, the "Manual Telecide" macro simply gives you a way to build a Telecide override file visually using multiple tabs and keyboard shortcuts instead of juggling programs/copy and pasting frame numbers/reloading scripts. Sorry if I was being misleading.

How hard would it be to include a 'recent avs files' file menu item? Very useful for me, as I keep all my different project all over the place depending on what drive has the most gigs free ;).
Good suggestion, didn't think about that - I'll try and get it in the next release.

The ability for it to auto session save when you quit and have that ready to load would be similarly excellent.
This is somewhat implemented in version 1.2.0. When you close the program, AvsP will still prompt you to save each script, then it saves the session. The next time you run the program this session is automatically loaded IF it gets no command line arguments (ie, double-click the exe or a shortcut, instead of double-clicking an avs file). This is more or less the way Notepad++ handles it, I can modify the behavior if anyone has different ideas or existing examples of how it's done.

krisq

2nd October 2006, 12:58

what an excellent update :D. :thanks:

Henrikx

2nd October 2006, 14:35

Update .....;)
German translation AvsP 1.2.0

Zarxrax

2nd October 2006, 18:31

Wow! It just gets better and better! Thanks for the huge updates!

communist

2nd October 2006, 19:53

Big thanks - what a beatiful program :)

Oh if possible could you add sub 100% zoom factors (25 / 50 / 75%)?
Having to specify pixels gives you evil scrollbars ;)
(Though in some cases scrollbars are quite useful - if you're tweaking a specific region only)

And 2nd suggestion could you add a shortcut or other way for moving lines up or down (in order to test filter order)? With Ctrl+Shift+ Up or down or something like this?

qwerpoi

2nd October 2006, 23:34

what an excellent update :D. :thanks:
b^_^d You're welcome!

Wow! It just gets better and better! Thanks for the huge updates!
b^_^d You're welcome!

Update .....;)
German translation AvsP 1.2.0
Awesome! The Japanese and Russian translations have been updated as well, you can get them from the AvsP download page. You guys are fast, less than 24 hour turnaround time!

Big thanks - what a beatiful program :)

Oh if possible could you add sub 100% zoom factors (25 / 50 / 75%)?
Having to specify pixels gives you evil scrollbars ;)
(Though in some cases scrollbars are quite useful - if you're tweaking a specific region only)
Sub zoom factors should be doable, but might look hideous. I'm not sure what you mean when you say "having to specify pixels gives you evil scrollbars". Not the evil part, I agree, scrollbars are fugly :), but the specifying pixels part - what are you referring to? Keep in mind that if your desktop is big enough you can change the max size of the video preview in Options -> Program settings... in the Video tab, change the max width and height to as big as you can.

And 2nd suggestion could you add a shortcut or other way for moving lines up or down (in order to test filter order)? With Ctrl+Shift+ Up or down or something like this?
Hmm, interesting idea, I'll give it some thought. For the moment you can highlight an entire line by clicking once on the margin, then drag-and-drop it wherever you want. But as you point out, there's no quick way with a keyboard shortcut, so it may be worth adding (since the AviSynth language works very much on a line-by-line basis).

Alain2

3rd October 2006, 01:05

Interesting editor! I am still using my notepad++ and vdub for previewing because I am too used to it, but I may switch to AvsP sometime soon ^^

Here are a few points / requests you may want to consider :) :

- Adding another toolbar below the File/Edit/etc menu. And in this add a toggle button that when activated will prevent any update of the video window. That way if I make a mistake / wrong shortcut / whatever, if it has to do with the video window it won't hang for a few seconds to apply the script (my avs are "mf" slow usually ^^ )

- I read you don't like the idea of a resizeable window because it's not really representative as the algorithm that rescale won't be the one chosen in avisynth, but it would be nice if we could drag the video window and have the video resized with it (like in vdub), with a fixed 1:1 ratio. This is helping me a lot to see properly what I am doing.. and having a choice of only 100% or 200% is not convenient for me

- The tooltip for the functions used is a nice and useful idea, but I don't like that it cover the text under in the following script lines.. For instance, can you add another toolbar that would contain a copy of the currently edited line (like in excel for instance), but instead of the parameters in brackets for the recognized functions, put what you have in your tooltip (all the parameters names, highlighting the one where the cursor is currently focused on) ?

- I love the fact you can link a function to its help file! I know I can call the help for functions recognized when the tooltip is shown by clicking in it, but is there a shortcut (like F1) that could do the same ? I didn't find it.. Same for the general Avisynth Help menu (so maybe Shift F1 for this one ? or vice versa)

- Add an optional mod factor (like 2) for the crop editor

- Add a wrap text option ? And in that case, a current line highlight option as well (well this is the n++ habits that come in ^^ )

- Would be nice if you could expand a bit the syntax coloration, like in n++ again ^^ maybe even in xml, and even compatible with the xml format of n++ ! (oh well I had to try ^^ )

Long post, but your editor is really a neat thing, thank you very much for all the efforts you put in it so far !

doxville

3rd October 2006, 11:25

Great and fast update!! Do you ever sleep...? :)

The new preview-while-dragging works great and so does the trim-editor! Good job! Now I found it would be handy, if there was an option (maybe to activate in a sub-menu) to show the bookmarked sections on the timeline-slider, to have a quick overview, which sections are IN and which are OUT, before you choose to insert the 'trim'-line. Something like in the screenshot I attached.
Thanx in advance, I hope it's not too complicated to integrate. :D

qwerpoi

3rd October 2006, 17:49

- Adding another toolbar below the File/Edit/etc menu. And in this add a toggle button that when activated will prevent any update of the video window. That way if I make a mistake / wrong shortcut / whatever, if it has to do with the video window it won't hang for a few seconds to apply the script (my avs are "mf" slow usually ^^ )
mf slow, that's hilarious :D (I wonder how many people here get the reference?) Anyway, I never thought about that, so I'll try and add an option to "lock" the video preview. As far as a toolbar is concerned, ugh, in general I hate toolbars. They're usually an eyesore filled with buttons you mostly never use. But it's a good place to place a toggle switch like you point out, so it's something for me to consider.

- I read you don't like the idea of a resizeable window because it's not really representative as the algorithm that rescale won't be the one chosen in avisynth, but it would be nice if we could drag the video window and have the video resized with it (like in vdub), with a fixed 1:1 ratio. This is helping me a lot to see properly what I am doing.. and having a choice of only 100% or 200% is not convenient for me
Well, let's get to the heart of the matter - if it were easy to implement a good-looking scaling resize, I might do it, but it's pretty difficult. For the longest time virtualdub had fixed zooms like AvsP, I believe the new resizable video window works by using directx, which is more work than I'm willing to get into, at least for now.

- The tooltip for the functions used is a nice and useful idea, but I don't like that it cover the text under in the following script lines.. For instance, can you add another toolbar that would contain a copy of the currently edited line (like in excel for instance), but instead of the parameters in brackets for the recognized functions, put what you have in your tooltip (all the parameters names, highlighting the one where the cursor is currently focused on) ?
Ugh, in general I hate toolbars, they're usually...wait, I already said that :o . Well, I'm not sure I agree with your complaint about tooltips covering other lines - the way AvsP does it is the same way every programming editor does it! What may be your problem is that AvsP shows tooltips gratuitously compared to other editors - other editors usually show tooltips only upon autocompletion, AvsP shows tooltips whenever your cursor is inside a filter's arguments. I'll add an option to change this behavior to be more similar to other editors, hopefully that will solve your issue.

- I love the fact you can link a function to its help file! I know I can call the help for functions recognized when the tooltip is shown by clicking in it, but is there a shortcut (like F1) that could do the same ? I didn't find it.. Same for the general Avisynth Help menu (so maybe Shift F1 for this one ? or vice versa)
There's currently no shortcut equivalent to clicking the tooltip, but it's a good idea, I'll add that feature for the next release. For the general AviSynth help, that feature is in the menu command Help -> AviSynth help - just add the keyboard shortcut of your choice (Options -> Configure shortcuts...).

- Add an optional mod factor (like 2) for the crop editor
Why? The status bar tells you what your mod is, and there are various ways to fine tune the crop values. The reason I'm hesitant to implement your idea is that it can lead to complications - for example, cropping 9 pixels from the left and 7 pixels from the right could be a valid crop, but would be difficult to do if the values were locked to even numbers.

- Add a wrap text option ? And in that case, a current line highlight option as well (well this is the n++ habits that come in ^^ )
It's easy for me to add these features, so I'll do it. Out of curiousity, do you really wrap text when writing AviSynth scripts?

- Would be nice if you could expand a bit the syntax coloration, like in n++ again ^^ maybe even in xml, and even compatible with the xml format of n++ ! (oh well I had to try ^^ )
Umm, no :devil: . Seriously, I can't imagine needing a super-configurable syntax highlighting format, since AvsP is only used with one language, AviSynth. You can change the fonts and colors from Options -> Program settings... in the Font tab, if there's something further you want to be able to configure, let me know.

Great and fast update!! Do you ever sleep...? :)
Of course I sleep; what a silly question. Of course, when I sleep, I only dream of new AvsP features and electric sheep. :p

The new preview-while-dragging works great and so does the trim-editor! Good job! Now I found it would be handy, if there was an option (maybe to activate in a sub-menu) to show the bookmarked sections on the timeline-slider, to have a quick overview, which sections are IN and which are OUT, before you choose to insert the 'trim'-line. Something like in the screenshot I attached.
Thanx in advance, I hope it's not too complicated to integrate. :D
Haha, that screenshot is making me hungry! Anyway, that's a good idea, but unfortunately impossible with the slider control, which only allows for a single selection. It's possible if I implement my own slider control from scratch, which is a lot of work (I might do it sometime in the future, just not right now).

krieger2005

3rd October 2006, 19:08

Well, let's get to the heart of the matter - if it were easy to implement a good-looking scaling resize, I might do it, but it's pretty difficult. For the longest time virtualdub had fixed zooms like AvsP, I believe the new resizable video window works by using directx, which is more work than I'm willing to get into, at least for now.

When i understand the workflow of your Program right (with interpretation of sliders and so on) you create an own "avs-file", which you modify when a slider was moved. why do you not use an internal avisynth-scale-function. Then you can add at the end of the script something like:
ConvertToRGB24().LanczosResize(<desired_restX>, <dest_Y>)
ConvertToRGB24 is used just because it can scale then by Pixel.

foxyshadis

3rd October 2006, 19:38

I was going to point out what krieger did first :p
mf slow, that's hilarious :D (I wonder how many people here get the reference?) Anyway, I never thought about that, so I'll try and add an option to "lock" the video preview. As far as a toolbar is concerned, ugh, in general I hate toolbars. They're usually an eyesore filled with buttons you mostly never use. But it's a good place to place a toggle switch like you point out, so it's something for me to consider.
Maybe instead of a new toolbar, just put it on the preview's existing toolbar.

nibbles

3rd October 2006, 21:15

Nice update! It's great to hear that you had time to try out
different gui frameworks. Ever use Swing?

About the mouse coordinates idea, I was thinking that people
dealing with logos and subtitles, NTSC safe areas, or chroma
shifting would benefit from the option to display the x,y position,
but they could always add a filter and a couple of sliders to do
those tasks I suppose. The combination of macros and sliders
is tremendously powerful! Thanks btw for your willingness to
adjust the F1-F4 key bindings and make the rest configurable.
I'm always finding myself trying to use Alt+f,s out of habit to
Save a file, but that's not bound, only Alt+f,e is setup for Exit.

Have a great day! :)

qwerpoi

3rd October 2006, 21:42

When i understand the workflow of your Program right (with interpretation of sliders and so on) you create an own "avs-file", which you modify when a slider was moved. why do you not use an internal avisynth-scale-function. Then you can add at the end of the script something like:
ConvertToRGB24().LanczosResize(<desired_restX>, <dest_Y>)
ConvertToRGB24 is used just because it can scale then by Pixel.
I was going to point out what krieger did first :p
Man, you guys won't give up about this resizable preview thing! :) Well, I'll see what I can do, the only reason I'm hesitant is because I'll have to do some significant overhaul to my layout code, which is a lot more hairy than you would think at first glance.

Maybe instead of a new toolbar, just put it on the preview's existing toolbar.
Yep, but I don't want to get into the habit of adding random buttons on the video toolbar. What I'll likely do is something like let you right-click the toggle button to lock, which would gray out all the controls. It's not a perfect solution, but I imagine it's not a feature everyone will use anyway (although it's certainly a nice feature to have).

Nice update! It's great to hear that you had time to try out different gui frameworks. Ever use Swing?
No, I'm more of a C/C++ kind of guy (certainly no expert, though), don't know no Java (although I'm aware it's not that different from C++). As far as I know, it's not straightforward to compile standalone executables from Swing, maybe I'm totally wrong. I looked into mfc, wtl, raw win32, wxwidgets, wxpython, venster (some more briefly than others) before settling on wxpython. Mind you I don't think wxpython is perfect, far from it, but it was the framework I found myself most productive in. Actually, I couldn't make heads or tails out of most of those other frameworks :), I'm really not a very good programmer on a technical level.

About the mouse coordinates idea, I was thinking that people
dealing with logos and subtitles, NTSC safe areas, or chroma
shifting would benefit from the option to display the x,y position,
but they could always add a filter and a couple of sliders to do
those tasks I suppose.
I'll try and implement it and see how it looks, my only concern is that there will be too much info in the status bar - to me it's less useful if it's too cluttered to visually pick out the info you want.

Alain2

3rd October 2006, 23:23

Ugh, in general I hate toolbars, they're usually...wait, I already said that :o . Well, I'm not sure I agree with your complaint about tooltips covering other lines - the way AvsP does it is the same way every programming editor does it! What may be your problem is that AvsP shows tooltips gratuitously compared to other editors - other editors usually show tooltips only upon autocompletion, AvsP shows tooltips whenever your cursor is inside a filter's arguments. I'll add an option to change this behavior to be more similar to other editors, hopefully that will solve your issue.
Ah ok maybe ^^ I don't use programming editors so I didn't know, but yes if you implement a different behaviour like showing the tooltip only when changing the content in bracket and not just anityme the cursor is there, then yes that would be ok for me :)

There's currently no shortcut equivalent to clicking the tooltip, but it's a good idea, I'll add that feature for the next release. For the general AviSynth help, that feature is in the menu command Help -> AviSynth help - just add the keyboard shortcut of your choice (Options -> Configure shortcuts...).
Oups missed this one in the keyboard shortcut dialog ^^ And thanks for adding a new shortcut in the next releases !

Why? The status bar tells you what your mod is, and there are various ways to fine tune the crop values. The reason I'm hesitant to implement your idea is that it can lead to complications - for example, cropping 9 pixels from the left and 7 pixels from the right could be a valid crop, but would be difficult to do if the values were locked to even numbers.[quote]
Hum indeed.. that was a bad request ^^

[QUOTE=qwerpoi;883081]It's easy for me to add these features, so I'll do it. Out of curiousity, do you really wrap text when writing AviSynth scripts?
Yes sometimes ^^ I work in 1600x1200 but sometimes I happen to hae long string chains (masktools expr...) that I can't break with \ in the middle.. I could make and name a string, and break it into several lines that way before using it in masktools with its name, but I don't like creating variables when it's not necessary ^^

Umm, no :devil: . Seriously, I can't imagine needing a super-configurable syntax highlighting format, since AvsP is only used with one language, AviSynth. You can change the fonts and colors from Options -> Program settings... in the Font tab, if there's something further you want to be able to configure, let me know.
Ok.. It's true it may not be very useful here. What I like to do for me in n++ is to separate the functions in coloring categories ; I use all 4 categories available in n++ like that : 1. Internal Avs functions, 2. Definition / Properties, 3. User dll functions, 4. User Avs functions. Examples of what I am talking about : 1 (http://img374.imageshack.us/img374/2155/tempjx6.jpg) 2 (http://img417.imageshack.us/img417/2014/tempzo9.jpg). Would be great if I could have several categories of functions like on my n++ for separate syntax coloring properties :)

Oh and I tried what krieger2005 suggested for resizing, works well ^^ But now, maybe... can you make the sliders in a separate window, maybe dockable to the right of the picture if we want, but that we can move away as well so that when resizing the pictures it is not interacting with the sliders position / sizes ? Well this request is not very important, I can already work well as it is at the moment when fixing correct video window dimensions limits in the options