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

Alain2

25th October 2006, 13:00

* store last program size and position (suggested by Alain2)
That's great! And the video drag a la acrobat is really a nice feature !

About the on the-fly-resize, I think having a dockable window is not that important for me (but probably is for people with 2 monitors like Foxyshadis). I think a good alternative using your layout would be to have a toogle option that, if activated, would make avsp resize the frame sent by avisynth to the height of the preview video slider (adding automatically the horizontal video slider when it's becoming too wide). This could be done with a resize algo to be chosen by the user ; no colorspace convertion required I think if it is implemented with something like
BicubicResize(m4(width*float(previewHeight)/height),m4(previewHeight),0,.5), where previewHeight is the on-the-fly height of the video window (and m4 Didée's Function m4(float x){ Return( x < 16 ? 16 : int( Round( x / 4.0 )*4 ) ) })

btw would it be possible to make video separator a bit widder for easier grip of it (maybe not as big as acrobat ones, but more then 3 pixels height if possible ; maybe make that an option ?)

Neo Fagin

25th October 2006, 19:48

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.
I have this same issue with 1.3.1, and several previous versions. It USED to work with 1.2.1 and then just stopped working one day for some reason. avisynth 2.56, even a one-line script like dgdecode_mpeg2source("f:\video.d2v") which should display just the original video in the preview window, just displays a blank. The window does resize to the width/height of the video but no video is actually displayed. It's doing this on three different systems I've got including one with a fresh XP SP2 and avisynth install so it's driving me nuts, it's got to be something ridiculously simple I'm missing or doing wrong, but the same scripts open fine in virtualdub or MeGUI.

Fizick

25th October 2006, 20:10

today I updated Russian translation to v1.3.0.
(no new messages so translators don't need to redo their 1.3.0 translations).
Thanks, I believe, you at last brake the development :)

qwerpoi

26th October 2006, 02:39

About the on the-fly-resize, I think having a dockable window is not that important for me (but probably is for people with 2 monitors like Foxyshadis). I think a good alternative using your layout would be to have a toogle option that, if activated, would make avsp resize the frame sent by avisynth to the height of the preview video slider (adding automatically the horizontal video slider when it's becoming too wide). This could be done with a resize algo to be chosen by the user ; no colorspace convertion required I think if it is implemented with something like
BicubicResize(m4(width*float(previewHeight)/height),m4(previewHeight),0,.5), where previewHeight is the on-the-fly height of the video window (and m4 Didée's Function m4(float x){ Return( x < 16 ? 16 : int( Round( x / 4.0 )*4 ) ) })
Interesting ideas, I'll think about the best way to do this for an upcoming release (probably not the next one, though). For those people who want a separate video window, I have a question. Do you expect the video window to just have the video frame and the slider sidebar or do you need it to have the same video controls on the bottom and the tabs to switch them on the top? Clearly the first choice is easier for me to implement, the second way is a bit clunkier. But I don't want to put something together that won't be useful, so let me know what you need.

btw would it be possible to make video separator a bit widder for easier grip of it (maybe not as big as acrobat ones, but more then 3 pixels height if possible ; maybe make that an option ?)
Hah, that's a good point, I'll try and do something about it for the next release.

I have this same issue with 1.3.1, and several previous versions. It USED to work with 1.2.1 and then just stopped working one day for some reason. avisynth 2.56, even a one-line script like dgdecode_mpeg2source("f:\video.d2v") which should display just the original video in the preview window, just displays a blank. The window does resize to the width/height of the video but no video is actually displayed. It's doing this on three different systems I've got including one with a fresh XP SP2 and avisynth install so it's driving me nuts, it's got to be something ridiculously simple I'm missing or doing wrong, but the same scripts open fine in virtualdub or MeGUI.
Okay, the fact that the window resizes to the appropriate size implies that the avs script is being loaded. If not even the simplest of scripts display anything (try a script like "Version()", or try doing a preview of no text at all), there may be a refresh issue (I'm stretching, I know). Try posting a screenshot of the entire program so I can see the script and the video preview, and also make sure you don't overlook any error messages (they might pop up in a separate window).

today I updated Russian translation to v1.3.0.
Thanks for the update!

Thanks, I believe, you at last brake the development :)
Yeah, I would have put in more stuff, but if I keep releasing new versions every day I think all of the translators would revolt against me :) . And just so you know, I'm going to prepare my source files for release (it's a bit messy right now), not immediately but probably in the next big update.

foxyshadis

26th October 2006, 03:41

Do you expect the video window to just have the video frame and the slider sidebar or do you need it to have the same video controls on the bottom and the tabs to switch them on the top? Clearly the first choice is easier for me to implement, the second way is a bit clunkier. But I don't want to put something together that won't be useful, so let me know what you need.

The frame # might be nice, but I rarely use the buttons except to show and close it. The slider's the biggie, and the stuff in the context menu.

Wilbert

26th October 2006, 21:58

I approved two attachments (translations). Sorry that i missed them.

chros

27th October 2006, 08:39

Did you think about that it would be a perfect avisynth creator for MeGUI ? :) (Like Behappy in the audio conversion part.)

It has almost everything that the users missed in the current one.
Of course there's things to do: eg. command line interfaces to load a d2v file (I don't know if it's present), DAR calculation, IVTC recognison (analyze) ...

qwerpoi

27th October 2006, 09:07

It looks like I'm going to be a bit busy for a couple of days, so instead of releasing a bugfix release immediately I'll work on enhancing the window layout stuff (primarily the separate video preview), and release that sometime next week. Hope you guys can live with those two mouse-click bugs krisq pointed out until then :) .

Did you think about that it would be a perfect avisynth creator for MeGUI ? :) (Like Behappy in the audio conversion part.)

It has almost everything that the users missed in the current one.
Of course there's things to do: eg. command line interfaces to load a d2v file (I don't know if it's present), DAR calculation, IVTC recognison (analyze) ...
Actually I've never used MeGUI (is that a crime for doom9 forum members? :) ), mostly because I never had the need, and also I have an irrational dislike for the .net framework. I'm certainly willing to listen to any specific requests regarding this, but you'll have to walk me through a bit as to what would be needed, since I'm clueless as to what a good MeGUI "avisynth creator" would be.

foxyshadis

27th October 2006, 10:09

A couple minor things: ImageSource is not included in the definitions. Also, would it be possible to close the parentheses when adding a new function, and insert the cursor between them? Also, name autocomplete fails right after an =, though putting a space after will let it work. Lastly, would it be possible to sort the pop-up list by frequency of use, or at least last use, which is nearly as good? And is it possible to autocomplete function arguments? (Actually, come to think of it, the idea a few pages ago about clicking on them is better.)

Could deselected toggles have their text be greyed out (ie, given the comment color)? Oh, and HDTV cries out for a minimum text area size of at least 2-3 lines, when you pop it open.

I still like the idea of being able to save marked up scripts, along with normal ones; though useful for posterity, my primary motivation is that I write filters and work on the looney fringe of current ones, and that means lots of avisynth & avsp crashes. Alternately, a quick-save session state. In the meantime I've taken to making a few script changes, closing & reopening avsp, and then opening the video, so I don't lose it all. :p

I'm surprised, I haven't used Editplus at all for avisynth lately. There's just nothing it could offer me that avsp doesn't do mch better. Now I just have to get some template macros done and I'm good.

qwerpoi

27th October 2006, 10:41

A couple minor things: ImageSource is not included in the definitions.
I'm assuming ImageSource is a newer built-in filter (I guess it's time I updated my AviSynth version, I'm guilty of being a longtime 2.5.4 user). I'll try and update my default definitions, although eventually the whole process will be replaced by auto-detection schemes.

Also, would it be possible to close the parentheses when adding a new function, and insert the cursor between them?
Already one step ahead of you - go to "Options -> Program settings..." in the "Text 1" tab, change the "Autoparentheses level" to 2. I realize that the number of options in AvsP is getting heinous, I think the best solution would be to make an faq and package it with the download (another thing to add to my giant to-do list :) ).

Also, name autocomplete fails right after an =, though putting a space after will let it work. Lastly, would it be possible to sort the pop-up list by frequency of use, or at least last use, which is nearly as good? And is it possible to autocomplete function arguments? (Actually, come to think of it, the idea a few pages ago about clicking on them is better.)
For autocompleting after an =, you can use the manual "Autocomplete" option in the right-click menu (default shortcut Ctrl+Space), I'll work on fixing that to show up automatically. I'll think about the sorted lists and autocompleted arguments, it might be a little tricky to do certain things since I didn't write all the code, I'm using the framework provided by the Scintilla editing component.

Could deselected toggles have their text be greyed out (ie, given the comment color)? Oh, and HDTV cries out for a minimum text area size of at least 2-3 lines, when you pop it open.
I'll work on the deselected toggle color (might be tricky), and perhaps I'll make the minimum text size a user configurable option. My original thinking was that for hd content you want as much as the screen visible as possible, making it essentially the same as a separate window for the video (unless you're using a multi-monitor setup of course). If you have to see both text and video at the same time you can always drag the window down a bit and AvsP will respect that position from that point on.

I still like the idea of being able to save marked up scripts, along with normal ones; though useful for posterity, my primary motivation is that I write filters and work on the looney fringe of current ones, and that means lots of avisynth & avsp crashes. Alternately, a quick-save session state. In the meantime I've taken to making a few script changes, closing & reopening avsp, and then opening the video, so I don't lose it all. :p
Hmm, I'll see what you mean, closing and reopening AvsP does not sound like a fun way to handle the situation :) . I'll see what I can do.

I'm surprised, I haven't used Editplus at all for avisynth lately. There's just nothing it could offer me that avsp doesn't do mch better. Now I just have to get some template macros done and I'm good.
Sounds like good news to me! I never intended on AvsP to compete with robust text editors, but it seems like it's getting there - I'm glad you think so too.

Whew! That was a long post!

Alain2

27th October 2006, 13:01

I'm assuming ImageSource is a newer built-in filter (I guess it's time I updated my AviSynth version, I'm guilty of being a longtime 2.5.4 user). I'll try and update my default definitions, although eventually the whole process will be replaced by auto-detection schemes.
Maybe there is a need to think about how to add / modify things but don't mess with the user addition / modification to the list ? Maybe a good way would be a macro that would lookup in the dictionnary list if the wanted addition / modification already exists, if not prompt the user to add it, if already exists, show the user settings and the proposed modification to it and let the user choose which ones to modify ?

Already one step ahead of you - go to "Options -> Program settings..." in the "Text 1" tab, change the "Autoparentheses level" to 2.
! Never realised what that option was for (didn't try though ^^) Maybe labelling 0 1 2 as: None " "; Open "("; Close "()" would help understand quickly that option

krisq

27th October 2006, 21:38

Do you expect the video window to just have the video frame and the slider sidebar or do you need it to have the same video controls on the bottom and the tabs to switch them on the top? Clearly the first choice is easier for me to implement, the second way is a bit clunkier. But I don't want to put something together that won't be useful, so let me know what you need.

Actually, I don't know if this is a good idea but I think all the controls for undocked preview should be under the script window. This way if someone is using two monitors (on first script editor with sliders, on second the preview) you wouldn't have to move the mouse across monitors. And undocked window should have 'always on top' switch :).

check

29th October 2006, 13:47

I still like the idea of being able to save marked up scripts, along with normal ones; though useful for posterity, my primary motivation is that I write filters and work on the looney fringe of current ones, and that means lots of avisynth & avsp crashes. Alternately, a quick-save session state. In the meantime I've taken to making a few script changes, closing & reopening avsp, and then opening the video, so I don't lose it all. :p

After losing half an hour of work just now after a mistake with warpsharp values (D:), I heartily request this function!

qwerpoi

29th October 2006, 22:27

Maybe there is a need to think about how to add / modify things but don't mess with the user addition / modification to the list ? Maybe a good way would be a macro that would lookup in the dictionnary list if the wanted addition / modification already exists, if not prompt the user to add it, if already exists, show the user settings and the proposed modification to it and let the user choose which ones to modify ?
If you're referring to adding new "standard" filter definitions on an AvsP version by version basis, then your proposed method sounds pretty good, I'll put that together when I get the chance. To me it's not that big of a deal, though, since it's so easy to add new filter definitions from the menu, the standard definitions provided with AvsP are more or less just a baseline to get you started. What may become more critical in the future is determining a way to use AviSynth plugin auto-detection mechanisms while at the same time keeping all your personal definition customizations, this may require some reworking of the current format.

! Never realised what that option was for (didn't try though ^^) Maybe labelling 0 1 2 as: None " "; Open "("; Close "()" would help understand quickly that option
You're right, it wasn't labeled very well :) . I'll change the labels in the next release.

Actually, I don't know if this is a good idea but I think all the controls for undocked preview should be under the script window. This way if someone is using two monitors (on first script editor with sliders, on second the preview) you wouldn't have to move the mouse across monitors. And undocked window should have 'always on top' switch :).
That's what I wanted to know, you're basically confirming what I had initially guessed, that the controls need to be in both places to work well. A bit of a pain for me to make sure that the frame number and slider stay in sync, but should be doable (although it might look kind of silly to have two sets of controls on a non-multi-monitor setup).

After losing half an hour of work just now after a mistake with warpsharp values (D:), I heartily request this function!
Sorry for the bizarre request, but could someone give me a "safe" way to crash AviSynth with a script, such that it closes AvsP abruptly? I want to see if I can capture such an event and save the last session in a stable manner. When I say "safe", I mean a way to crash AviSynth besides doing something that simply eats up all the ram, since the crash may not be consistent then.

foxyshadis

29th October 2006, 23:23

check

30th October 2006, 00:53

awarpsharp(192,8) or similar large values will do the trick ;) That said, it might just be trying to allocate a bajillion megabytes of memory..

qwerpoi

30th October 2006, 06:34

There's a bunch of ways, but the quickest is a bad codec/plugin. If you install LZOCodec (http://usuarios.lycos.es/lzocodec/LZOCodec_v0_4.zip) and try to open this video captured in it (http://foxyshadis.slightlydark.com/random/STR2311_cut.avi) with avisource, it'll crash. Or I could whip up a plugin really quick that does nothing but read a null pointer. =p

awarpsharp(192,8) or similar large values will do the trick ;) That said, it might just be trying to allocate a bajillion megabytes of memory..

Thanks for helping me crash AviSynth, guys :) . I tried the awarpsharp script, but it didn't hard crash AviSynth, instead it gives me an AviSynth error video, I might be using a different version than yours, check. So I ended up installing LZOCodec (which I was hesitant to do considering the first message on the website is "WHAT F_CKING SH_T IS THIS?" :) ). I couldn't find a consistent way to catch the crash, so what I'll end up doing (unless you have a more preferrable alternative) is make an option to quickly save the current session, as well as add a "paranoia mode" which will save the current session every time the moment before the video preview is refreshed (ie, every time a new avisynth script is loaded for the video preview).

krisq

30th October 2006, 12:03

That's what I wanted to know, you're basically confirming what I had initially guessed, that the controls need to be in both places to work well. A bit of a pain for me to make sure that the frame number and slider stay in sync, but should be doable (although it might look kind of silly to have two sets of controls on a non-multi-monitor setup).

It won't be silly, it'll be very practical :)

check

30th October 2006, 14:09

paranoia mode sounds great, I always forget to save anyway :)

krisq

30th October 2006, 14:27

Can you add an option/shortcut to refresh preview without switching focus to it?

[/EDIT]
Also, I miss a little more sophisticated search in 'Avisynth function definition...'.
My wish is to quickly input few letters for more correct result, just like in explorer or any other file manager.
Example: I want to find filter 'ffdshow', if I press 'F' it will take me to 'FadeIn' filter. But if I enter 'FF' it should take me to 'ffdshow'.
I think with many configured user filters this can come very useful.

foxyshadis

1st November 2006, 16:20

Here's something I was wondering about, but wasn't sure of the feasibility. Would it be possible to run avisynth in a separate thread - I assume it's something like that anyway - or even process, and at the top of the thread catch every exception that makes it up, and take action by destroying and recreating the entire thread/process.

The bad part about a process is that it'd need IPC, the good part is the absolute insulation and the ability to directly catch all avisynth errors(if it's written in C++). Still might not be worth it.

qwerpoi

1st November 2006, 19:22

Can you add an option/shortcut to refresh preview without switching focus to it?
Sure thing, I'll add an option to not focus the preview when using the F5 refresh.

Also, I miss a little more sophisticated search in 'Avisynth function definition...'.
My wish is to quickly input few letters for more correct result, just like in explorer or any other file manager.
Example: I want to find filter 'ffdshow', if I press 'F' it will take me to 'FadeIn' filter. But if I enter 'FF' it should take me to 'ffdshow'.
I think with many configured user filters this can come very useful.
Actually this already works, you just hit a strange exception case. The way the mechanism works is that if you keep hitting 'F' you will cycle through all the filters that start with 'F'; otherwise, it works as you expect. So if you wanted to find the filter 'FlipHorizontal', you could enter 'FL' and get there right away.

Here's something I was wondering about, but wasn't sure of the feasibility. Would it be possible to run avisynth in a separate thread - I assume it's something like that anyway - or even process, and at the top of the thread catch every exception that makes it up, and take action by destroying and recreating the entire thread/process.

The bad part about a process is that it'd need IPC, the good part is the absolute insulation and the ability to directly catch all avisynth errors(if it's written in C++). Still might not be worth it.
Sounds like a good idea, I'll look into how difficult it would be. For now the paranoia mode seems to work well in resolving any crash issues, but certainly it makes more sense to separate the processes if possible.

krisq

1st November 2006, 19:35

Actually this already works, you just hit a strange exception case. The way the mechanism works is that if you keep hitting 'F' you will cycle through all the filters that start with 'F'; otherwise, it works as you expect. So if you wanted to find the filter 'FlipHorizontal', you could enter 'FL' and get there right away.

Damn, you're right. It is strange exception beacause it doesn't work for twice 'F' as I expected to. That's what've misled me...:o

qwerpoi

1st November 2006, 20:43

Question for multi-monitor users. Does AvsP appropriately remember the program's position when it starts up, or does it always start up on the primary monitor? I guess it depends on how your multi-monitor desktop is setup, to either use a single large desktop across monitors or separate desktop units. The reason I need to know is because I want to make sure the separate external preview window shows up on the correct monitor, I may need to dig into more details to get it to work properly.

krisq

1st November 2006, 21:25

I've got one large desktop and avsp is always starting on primary display for me.

qwerpoi

1st November 2006, 21:36

I've got one large desktop and avsp is always starting on primary display for me.
Just to clarify, you're saying that when you move AvsP to the secondary monitor and close it, the next time it incorrectly starts up on the primary monitor? Another question - does the maximized setting get remembered correctly? I'm not sure how it's supposed to work, for a single large desktop it seems like a maximized program would take up all monitors, but that sounds strange. Regardless, does AvsP show up maximized properly on startup, or does it only maximize on the primary monitor?

krisq

1st November 2006, 21:57

Just to clarify, you're saying that when you move AvsP to the secondary monitor and close it, the next time it incorrectly starts up on the primary monitor?
Exactly.

Another question - does the maximized setting get remembered correctly? I'm not sure how it's supposed to work, for a single large desktop it seems like a maximized program would take up all monitors, but that sounds strange. Regardless, does AvsP show up maximized properly on startup, or does it only maximize on the primary monitor

It's maximizing properly, only on the primary display. One thing though and I think it's a bug. Maximize state is remembered correctly between sessions but if I 'unmaximize', it's returning to the size of the desktop and not the size before maximizing.

ChrisW77

2nd November 2006, 16:03

great program, very useful.

But, is there any way of making the user slider move using values of 2 ?
For example, ChromaShift(C=-2), and I need to adjust to -4/-6/-8, as you can only use even numbers, would be soo handy to see in a real-time window, as opposed to opening and closing vdub and notepad.

foxyshadis

2nd November 2006, 18:26

Can you add a *2 after the slider text?

qwerpoi

2nd November 2006, 20:08

It's maximizing properly, only on the primary display. One thing though and I think it's a bug. Maximize state is remembered correctly between sessions but if I 'unmaximize', it's returning to the size of the desktop and not the size before maximizing.
Yep, I knew about this bug before releasing v1.3.1, thanks for bringing it up, though. Basically you wouldn't believe the issues you run into when trying to layout windows when the windows don't yet exist, a lot of weirdness ensues. But I managed to get it working, so it will be fixed for the next release (coming very soon...)

great program, very useful.

But, is there any way of making the user slider move using values of 2 ?
For example, ChromaShift(C=-2), and I need to adjust to -4/-6/-8, as you can only use even numbers, would be soo handy to see in a real-time window, as opposed to opening and closing vdub and notepad.

Can you add a *2 after the slider text?
Actually it's a % 2, so your slider should look like [<"c % 2", -8, -4, -6>] - you can read more about it here (http://www.avisynth.org/qwerpoi/UserSliders.html#basic-usage) (at the end of the "Basic usage" section). I am aware that on a technical level that's not the best way to name it, foxyshadis' notation is more accurate - what can I say, I'm not a technical guy :) .

foxyshadis

2nd November 2006, 21:33

Oh, I just meant doubling everything is one way to make it always even :p (like [<"c", -8, -4, -6>]*2) but modulo is definitely better, especially when it's built right in. Neato, I missed that feature entirely.

qwerpoi

2nd November 2006, 23:50

New version 1.3.2, download from here (http://www.avisynth.org/qwerpoi/Download.html) or use a mirror from the first post. Here's the changelog:

* added option to make video preview a separate window

* added option to quickly backup the current session (suggested by foxyshadis)

* added "paranoia mode" to backup the current session whenever video is refreshed

* increased size of window dividers to make easier to click (suggested by Alain2)

* change autoparentheses levels option labels to be clearer (suggested by Alain2)

* added option to set minimum text window size (suggested by foxyshadis)

* added option to not focus video window when refreshing (suggested by krisq)

* added ability to clear a shortcut in the shortcut editor

* minor improvements to line-by-line update mode

* improved to multi-monitor support

> fixed bug with dragging crop edges (thanks krisq)

> fixed left-click to focus video window (thanks krisq)

> fixed autocomplete before operator (thanks foxyshadis)

> fixed bug with remembering program size when maximized (thanks krisq)
Biggest change here is the ability to make the video preview a separate window (under "Options -> Program settings..." in the "Video" tab, requires a program restart to take effect). The main window and the separate video window have an identical set of video controls at the bottom of each window. The video controls on the main window work a little different than normal, they do not focus the video window after the first time. It's a little hard to understand what this implies, so I'll just say try maximizing the separate video window in the background with the main window in the foreground as an interesting way to work with AvsP. Also as a reminder, be sure to use the keyboard shortcut Shift+Tab as a quick way to switch between the two windows.

Another important change is added options to back up the current session. These options are useful if you use filters that tend to hard-crash Avisynth, which in turn closes AvsP abruptly, causing you to lose all your unsaved script changes. You can either backup the current session with the menu command "File -> Backup current session" (default shortcut Alt-B), or use "paranoia mode", which backups the current session every time a new script is previewed (activate under "Options -> Enable paranoia mode"). The session is backed up into the file "_last_session_.ses" in the program directory. This file is automatically loaded when you start up AvsP with no command line arguments - in other words, it won't autoload if you have .avs files associated with AvsP and you double-click an avs file. You can force AvsP to load the last session no matter what in "Options -> Program settings..." under the "Misc" tab.

Another change is improved multi-monitor support - this means if you start AvsP in a secondary monitor and close it, it should open in the appropriate monitor, instead of always opening in the primary monitor, etc. However, I don't have a multi-monitor setup, so I don't know if it works as smoothly as I think (or if it even works at all). So any multi-monitor users out there be sure to report any strange behavior and I'll try and fix it.

One other bit of news - I released the source for AvsP, it's under the GPL license. I have no real reasons for doing this, I just thought it was only fair since Avisynth is under the GPL license, and without Avisynth there would be no AvsP. The source is included in the zip file, in the "src" directory. You can read the "notes.txt" if you're interested in running or compiling the program. Any questions regarding problems with the source should be in a separate thread or by pm - again, keep in mind I'm not really interested in supporting these types of issues, nor do I believe the source is in a maintainable or even readable form, I'm just releasing it for posterity's sake.

krisq

3rd November 2006, 00:26

Very impressive work qwerpoi :D. I will check it tomorrow on dual monitor setup. :thanks:
Is it possilble for you to give a choice where panel with sliders should be (script window or video window)?

ChrisW77

3rd November 2006, 01:36

Oh, I just meant doubling everything is one way to make it always even (like [<"c", -8, -4, -6>]*2) but modulo is definitely better, especially when it's built right in. Neato, I missed that feature entirely.

Yep, that way works best for me, many thanks. :)

Oh, and thanks for the new version, works a treat.

Alain2

3rd November 2006, 02:05

FR translation updated

Very nice work again! The separate video window works well, the refresh not focusing on the video is a very good idea :)

Thank you for your hard work qwerpoi, it really pays off I think! Hope you'll have some time to dig through the rest your todolist ^^

btw I don't have 2 monitors, so no comments on this from me

Fizick

3rd November 2006, 13:01

qwerpoi,
I will test new version.
Thanks for your decision to release a source unde GPL.
In my opinion, we now can declare your editor at least as semi-official AviSynth editor :)
I shall update Avisynth documentation to add the info (link).

Henrikx

3rd November 2006, 14:08

@qwerpoi
German translation updated

Question
Points (behind Instructions (Example :save as...) = an action is not immediately executed ..Is this also so at AvsP ?

krisq

3rd November 2006, 17:56

BTW I think you should add a link to the AvsP page in the 'about' box. :)

chros

3rd November 2006, 18:20

Bug?
I have copied the exe to the previous version's dir 1.3.1 (where were already the *.dat files) and the slider row + status row was very big and unresizable ...
Solution: delete all the *.dat files

Can you add an "associate with *.avs extension" switch in the Options? :)
I'm certainly willing to listen to any specific requests regarding this, but you'll have to walk me through a bit as to what would be needed, since I'm clueless as to what a good MeGUI "avisynth creator" would be.
OK. In the weekend I'll try to summarize the needed things ...
Thanks

qwerpoi

3rd November 2006, 19:57

Is it possilble for you to give a choice where panel with sliders should be (script window or video window)?
Ouch, it's possible but causes me pain to think about :( . I do understand where you're coming from, with the separate video window the sliders can sometimes make more sense on the script window. But as far as I can tell there's no simple way to do this, I'd have to write two sets of code (which is already what I had to do to support a separate video window). So it's an option that should be there, but I'm not sure when I'll get around to it :) .

Yep, that way works best for me, many thanks. :)

Oh, and thanks for the new version, works a treat.
Thanks, glad to hear it!

FR translation updated

Very nice work again! The separate video window works well, the refresh not focusing on the video is a very good idea :)

Thank you for your hard work qwerpoi, it really pays off I think! Hope you'll have some time to dig through the rest your todolist ^^

btw I don't have 2 monitors, so no comments on this from me
Thanks for the translation update! And don't worry, I haven't forgotten about my todo list (quite a few suggestions have your name on it :) ), I'll have to see about the time.

qwerpoi,
I will test new version.
Thanks for your decision to release a source unde GPL.
In my opinion, we now can declare your editor at least as semi-official AviSynth editor :)
I shall update Avisynth documentation to add the info (link).
Many thanks! By the way, if it's easier to host AvsP on sourceforge for bandwith reasons, let me know (I always felt guilty about the big download).

@qwerpoi
German translation updated

Question
Points (behind Instructions (Example :save as...) = an action is not immediately executed ..Is this also so at AvsP ?
Thanks for the updated translation! As far as your question goes, three periods (referred to as "ellipses") usually indicates an option which opens a separate dialog box. I tried to follow this convention with AvsP, but I may have missed some, so if you find any mistakes, let me know.

BTW I think you should add a link to the AvsP page in the 'about' box. :)
Good idea! It's not a very impressive 'about' box at the moment :) .

Bug?
I have copied the exe to the previous version's dir 1.3.1 (where were already the *.dat files) and the slider row + status row was very big and unresizable ...
Solution: delete all the *.dat files
You are indeed correct, I know about that bug, it's basically a byproduct of programatically sizing windows which don't yet exist coupled with positions from the old options.dat which may not make sense for the new version. I'm still trying to bulletproof the layout code to prevent this type of occurence, but in the meantime, you *should* be able to solve the problem simply by closing and reopening AvsP. If this doesn't work, you can do as chros suggests, you only need to delete the options.dat file, though.

Veiga

4th November 2006, 06:00

qwerpoi,

Portugues_Br translation update

very good work again.

foxyshadis

4th November 2006, 07:04

You could always start a new project on sourceforge for this. I think it would be really cool, and an svn would make it easy to make patches and stay in sync. ;) btw, I didn't have any problems recompiling following your directions, though I haven't made any changes yet.

qwerpoi

4th November 2006, 08:03

qwerpoi,

Portugues_Br translation update

very good work again.
Thanks for the update!

You could always start a new project on sourceforge for this. I think it would be really cool, and an svn would make it easy to make patches and stay in sync. ;) btw, I didn't have any problems recompiling following your directions, though I haven't made any changes yet.
As it stands, I know absolutely nothing about how to start or maintain a project on sourceforge, svn, repositories, any of that stuff, and I'm not sure I want to take the time to learn :) . I guess it would be worthwhile if enough programmers are willing to chip in with development, not sure how many python/wxpython guys there are around here, and some may consider the code to be hard to manage (not enough subdivision, and some questionable programming practices overall :) ). Ultimately it's a matter of time, I develop AvsP in my spare time, I don't know how much additional effort it would be to manage it as a project. Then again, there are some pretty big ideas around here, like implementing Avisynth in python for AvsP, or adding MeGUI specific features like IVTC analysis, stuff that I can't really handle effectively by myself, so in that sense maybe this is the right way to go.

And out of curiosity, did you try compiling using python 2.4 or python 2.5? I never tested with 2.5 so I just wanted to know if there were no problems. Also, how's v1.3.2 with respect to multi-monitor stuff (ie, does AvsP properly remember monitor positions for the main and separate video window)?