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

[qwerpoi]

New version 1.4.0, download from the AvsP download page (http://avisynth.org/qwerpoi/Download.html) or from the mirror (http://www.savefile.com/files/784607). This version has an excellent preview of the automatic user sliders, you should definitely check it out. Here's the changelog:

* fully automatic user sliders (experimental, turned off by default)

* simplified translation update procedure (suggested by Henrikx)

* added option for single instance (suggested by krisq, foxyshadis)

* added source extension filters to "Open..." dialog (suggested by 3ngel)

* changed default filename to work with unknown extensions (suggested by Zarxrax)

* opening an already opened file prompts for reload if changes exist (suggested by Kuukunen)

* toggle scrap window now works when scrap window focused (thanks AlanHK)

* changed error message when Avisynth fails to load video (thanks lolent)

* added macro for setting bookmarks (suggested by AlanHK)

* sliders no longer generated on error clips

* improved filter calltips to work with script line breaks

* added clear all text option for scrap window

* minor improvements to window layout code

+ fixed translation import problem (thanks Henrikx)

+ fixed bug with AvsP installed in directory with unicode characters (thanks Aeolis)

+ fixed display bug when resizing the script window with separate video window (thanks Alain2)

+ fixed several unicode bugs (thanks Zarxrax)

+ fixed crash when avisynth output has no video

There's a lot of good features that made it to this version, but the most important thing in my opinion is the automatic user sliders. The reason why they're disabled by default in this version is because one, the filter database isn't 100% complete, and two, they still need some testing for 100% script compatibility. But don't let that dissuade you from trying them out, in this version the feature is already incredibly robust.

In order to turn on automatic user sliders, you need to do two things. First, go to "Options -> Program settings...", go to the new "User sliders" tab, and check the first checkbox, "Create user sliders automatically". Second, you need to import the database that I put together, which currently resides in a text file. Start AvsP, go to "File -> Import filter customizations", and select the "autoslider_database.txt" file (comes with the zip file) as a calltip-only text file. You'll see a dialog with a list of all the filters in the file, click OK. What this will do is simply update the calltip information with the info in the text file. If you don't want to overwrite a particular filter's calltip, simply uncheck the box next to the filter before hitting OK. So what now? Well, now if you type in a script like this:

BlankClip(color=$000000)
Subtitle("This is awesome!", font="Verdana", size=25, text_color=$FFFF00, halo_color=$000000)

You'll get something that looks like this:

http://img101.imageshack.us/img101/2332/avspautosliderexamplefd2.th.jpg (http://img101.imageshack.us/my.php?image=avspautosliderexamplefd2.jpg)


As you can see, gui elements were created automatically for every argument specified, without adding tags to the script in any way shape or form. Some bonus features - you can click on an argument name to select the text in the script corresponding to that argument. You can click on the label to hide all of the filter's arguments (referred to as "folding"), right-click the label for a popup menu with some more options. Anyway, It might be hard to appreciate the power of what's going on here, so I encourage you to try it for yourself.

If you're wondering how it works, basically I've put all the necessary information about each filter in AvsP's calltip information. I've come up with a simple syntax to store the information in a readable fashion (in fact, you can actually see the info in the calltip when you're typing in the script, very handy). Anyway, if you look at "autoslider_database.txt", you'll see I only created the database info for most of the core internal filters (for Avisynth v2.5.7). This database should be expanded with popular 3rd party filters, and must be kept up to date for the feature to work seamlessly. Ideally, the data would be stored on a wiki so people can contribute easily (as steptoe and others have mentioned), and AvsP would have a menu item to update the database from the web. I don't really know a lot about the details to get this done, so any help here would be appreciated.

If you want to help update the database with more filters (or make corrections to the current info), you can use a tool I built to help create the correct syntax. In the "Options -> Avisynth function definition" dialog, if you double-click the text box with the calltip info another dialog appears. Assuming the normal calltip info already exists, this dialog allows you to fill out all the relevant database info for that filter with a graphical interface (example (http://img169.imageshack.us/img169/8202/avspautosliderdialogpp5.jpg)). If the calltip already has database info, the fields will be filled accordingly. Simply enter values for any or all the fields, then click OK. You will see the calltip has been updated with the appropriate database syntax. After you're done updating the filters you want, you can save your results to a text file using the "File -> Export filter customizations..." dialog. Check the filters you want to export and click OK. When promted to save the file, make sure to save it as a "Calltip-only text file (*.txt)", not a "Filter cusomization file (*.dat)". The resulting text file will be identical in format to the autoslider_database.txt file. The filter database syntax itself is almost self-explanatory if you look at the various examples already in the database, but I'll try and have full documentation on the syntax by the next release.

The other features in this release are more or less self-explanatory. You can now run AvsP as a single-instance program, simply click "Options -> Only allow a single instance" in the menu. I fixed some more unicode bugs (again), improved the layout a bit when comparing videos, and fixed the bug which stopped AvsP from importing the translation file properly. A BIG note to translators - this version has a new method of updating the translation file. You'll notice there's no "__translation.py" - in order to update the translation file, simply place the "translation.py" from a prior version in the AvsP directory and run AvsP. It will automatically update the file with all the missing messages, you can then close AvsP and update the new messages (as always, search for "# New in v1.4.0" tags).

One final note - since several people requested it, I added a donation button to the website. Feel free to donate a couple of bucks if you'd like, but there's no pressure, I don't ever intend on making AvsP shareware or anything like that. Anyway, try out the new version and let me know if there are any new problems or suggestions.

[Henrikx]

@qwerpoi
Update German Translation 1.4.0

Simplified translation = Super + ingeniously

Heavily to found a meaningful translation for "Fold all" and "filename pickers" .

[Zarxrax]

Wow! This is absolutely amazing, I love it! Thanks for all your hard work on this great software, I really think this has revolutionized avisynth!

After some quick usage, I do have one suggestion to make it a bit easier to use the sliders.
Can you make an ability to somehow automatically fill in all of the default parameters for a function? For instance lets say I want to use the Tweak function to adjust colors. Right now, I believe if I want to get access to all of the sliders for tweak, I have to type in each of the parameters that I want a slider for. Instead, there could be a button or hotkey or something that would automatically add all of the functions in with the default values, so you can immediately start dragging sliders around.

[Terranigma]

Thanks for the update, I hope this version fixes the minor problem I had with 1.3.9 ;)
If it doesn't, i'll post how to recreate it.

[niiyan]

@qwerpoi
Thanks for the update, qwerpoi.
I have some questions and problems about the new version.

1. translation.py has the following two lines.

"Make sure you have AviSynth installed and that there are no" : u"", # New in v1.4.0
"unstable plugins or avsi files in the AviSynth plugins directory." : u"", # New in v1.4.0

These lines seem to be separated, maybe at the point where you don't intended. If I combine them as follows, it is easier for me to understand.

"Make sure you have AviSynth installed and that there are no unstable plugins or avsi files in the AviSynth plugins directory." : u"", # New in v1.4.0

So, should I translate the two lines separetely? Or combine and translate as one line?

2. When I preview Version.avs included in AviSynth Examples directory, I got the follwing error.

Traceback (most recent call last):
File "AvsP.pyo", line 5733, in OnMenuVideoRefresh
File "AvsP.pyo", line 8617, in ShowVideoFrame
File "AvsP.pyo", line 8990, in UpdateScriptAVI
File "AvsP.pyo", line 9024, in GetAutoSliderInfo
File "AvsP.pyo", line 9038, in GetFilterArgMatchedInfo
File "AvsP.pyo", line 863, in GetFilterMatchedArgs
IndexError: list index out of range

3. I wrote the following script which includes Japanese Halfwidth Katakana, etc.

BlankClip()
Subtitle("ｷﾀ━(ﾟ∀ﾟ)━!")

When I select the quoted text in Subtitle, an error occurred as follows:

Traceback (most recent call last):
File "AvsP.pyo", line 1292, in OnUpdateUI
File "AvsP.pyo", line 801, in UpdateCalltip
UnboundLocalError: local variable 'iArgPos' referenced before assignment

4. After I close AvsP.exe, AvsP is trying to connect to localhost 127.0.0.1, port 50009. I don't know what it does. Are there any problem with this?

[qwerpoi]

@qwerpoi
Update German Translation 1.4.0

Simplified translation = Super + ingeniously

Heavily to found a meaningful translation for "Fold all" and "filename pickers" .
Thanks for the speedy translation update, glad the new method works properly. And I agree, a few of the new messages are somewhat unclear since they refer to completely new features, you can always pm me if you need some clarification on a new message.

Wow! This is absolutely amazing, I love it! Thanks for all your hard work on this great software, I really think this has revolutionized avisynth!
I totally agreee :)

Can you make an ability to somehow automatically fill in all of the default parameters for a function?
Absolutely, this will definitely be in the next version. Right now I'm trying to think of the best way to get this done (clicking on the calltip, a button in the slider window itself, etc). I wanted to release this version now to get a feel for how well it works with scripts that already exist, there's quite a bit of streamlining left to do.

1. translation.py has the following two lines.

"Make sure you have AviSynth installed and that there are no" : u"", # New in v1.4.0
"unstable plugins or avsi files in the AviSynth plugins directory." : u"", # New in v1.4.0

These lines seem to be separated, maybe at the point where you don't intended. If I combine them as follows, it is easier for me to understand.

"Make sure you have AviSynth installed and that there are no unstable plugins or avsi files in the AviSynth plugins directory." : u"", # New in v1.4.0

So, should I translate the two lines separetely? Or combine and translate as one line?
The lines were separated because the message was too long, but I agree, it seems bad from a translation standpoint. For now you'll have to translate each line separately, but I'll try and join them in the next version.

2. When I preview Version.avs included in AviSynth Examples directory, I got the follwing error.

3. I wrote the following script which includes Japanese Halfwidth Katakana, etc.

BlankClip()
Subtitle("ｷﾀ━(ﾟ∀ﾟ)━!")

When I select the quoted text in Subtitle, an error occurred as follows:
I couldn't reproduce the first error, but I see what caused the second one, the parentheses in the string screwed up the calltip code. I'll upload a fix shortly (right now the Avisynth ftp is giving me problems).

4. After I close AvsP.exe, AvsP is trying to connect to localhost 127.0.0.1, port 50009. I don't know what it does. Are there any problem with this?
AvsP opens a socket for the "Only allow a single instance" option, which it uses to pass command-line parameters to the main instance. Currently the socket is used even if the option is not turned on. If there are problems closing AvsP because of this, let me know.

[khs81]

Thanks for the new release! The new translation system is awesome. Thank you very much.

I will proceed with the italian translation tomorrow, I suppose.

Bye!

[niiyan]

@qwerpoi

... but I agree, it seems bad from a translation standpoint.

That's what I wanted to say :)

For now you'll have to translate each line separately, but I'll try and join them in the next version.

I'll do that. Thanks for your effort.

I couldn't reproduce the first error, ...

I have installed AvsP under "Program Files" folder, i.e. "C:\Program Files\AvsP". I moved it to another place, e.g. "C:\AvsP, then I have no problem with previewing Version.avs.

AvsP opens a socket for the "Only allow a single instance" option, which it uses to pass command-line parameters to the main instance. Currently the socket is used even if the option is not turned on. If there are problems closing AvsP because of this, let me know.

I understand what AvsP does. I have no problem because of this.

[qwerpoi]

Okay, we'll try something new. Officially there will be a bugfix release in about a week, but if you're experiencing the bugs niiyan reported (http://forum.doom9.org/showthread.php?p=1011207#post1011207) in version 1.4.0, you can download this zip file (http://avisynth.org/qwerpoi/upload/AvsP_bugfix_v1.4.0.zip) (133 kilobytes). The zip file contains a single file named AvsP.pyo, place it in the same directory as AvsP.exe and then run the program. It should fix both bugs. These bugfixes will obviously be incorporated in the next version, just wanted to try a new method of providing temporary fixes between versions.

[Terranigma]

Thanks for the update, I hope this version fixes the minor problem I had with 1.3.9 ;)
If it doesn't, i'll post how to recreate it.

Looks like the :devil: bug is still present, now I don't know how to exactly reproduce it, but I can tell you how you might be able to encounter it. You might encounter it after opening a memory intensive script for preview (mvdegrain2 with dct1 and overlap=8 is an intensive script), Then highlight something from the script with the Left-Mouse button and choose copy. You'd get an error... or you won't. =P
Like I said, this might be a way to reproduce the :devil: bug i've been encountering. :cool:

[Veiga]

@qwerpoi

congratulation for your new version, fantastic work.

[niiyan]

@qwerpoi
Both problems were solved by the bug fixing file. Thank you!

[qwerpoi]

You might encounter it after opening a memory intensive script for preview (mvdegrain2 with dct1 and overlap=8 is an intensive script), Then highlight something from the script with the Left-Mouse button and choose copy. You'd get an error... or you won't. =P
Check out if you have an "avsp_error_log.txt" in your AvsP directory. If so, please post the error message if it has been logged to help me get an idea of what's going on.

@qwerpoi

congratulation for your new version, fantastic work.
Thanks for the translastion update, I've updated the links on the first post and download page accordingly.

@qwerpoi
Both problems were solved by the bug fixing file. Thank you!
Very cool, I'm glad the bugfix update method works smoothly.

[Terranigma]

as you wish.

[Thu Jun 07 10:11:54 2007]
Traceback (most recent call last):
File "AvsP.pyo", line 1292, in OnUpdateUI
File "AvsP.pyo", line 801, in UpdateCalltip
UnboundLocalError: local variable 'iArgPos' referenced before assignment
Traceback (most recent call last):
File "AvsP.pyo", line 1292, in OnUpdateUI
File "AvsP.pyo", line 801, in UpdateCalltip
UnboundLocalError: local variable 'iArgPos' referenced before assignment
Traceback (most recent call last):
File "AvsP.pyo", line 1292, in OnUpdateUI
File "AvsP.pyo", line 801, in UpdateCalltip
UnboundLocalError: local variable 'iArgPos' referenced before assignment
Traceback (most recent call last):
File "AvsP.pyo", line 1292, in OnUpdateUI
File "AvsP.pyo", line 801, in UpdateCalltip
UnboundLocalError: local variable 'iArgPos' referenced before assignment
Traceback (most recent call last):
File "AvsP.pyo", line 1292, in OnUpdateUI
File "AvsP.pyo", line 801, in UpdateCalltip
UnboundLocalError: local variable 'iArgPos' referenced before assignment
Traceback (most recent call last):
File "AvsP.pyo", line 1292, in OnUpdateUI
File "AvsP.pyo", line 801, in UpdateCalltip
UnboundLocalError: local variable 'iArgPos' referenced before assignment
Traceback (most recent call last):
File "AvsP.pyo", line 1292, in OnUpdateUI
File "AvsP.pyo", line 801, in UpdateCalltip
UnboundLocalError: local variable 'iArgPos' referenced before assignment
Traceback (most recent call last):
File "AvsP.pyo", line 1292, in OnUpdateUI
File "AvsP.pyo", line 801, in UpdateCalltip
UnboundLocalError: local variable 'iArgPos' referenced before assignment
Traceback (most recent call last):
File "AvsP.pyo", line 1292, in OnUpdateUI
File "AvsP.pyo", line 801, in UpdateCalltip
UnboundLocalError: local variable 'iArgPos' referenced before assignment
Traceback (most recent call last):
File "AvsP.pyo", line 1292, in OnUpdateUI
File "AvsP.pyo", line 801, in UpdateCalltip
UnboundLocalError: local variable 'iArgPos' referenced before assignment
Traceback (most recent call last):
File "AvsP.pyo", line 1292, in OnUpdateUI
File "AvsP.pyo", line 801, in UpdateCalltip
UnboundLocalError: local variable 'iArgPos' referenced before assignment
Traceback (most recent call last):
File "AvsP.pyo", line 1292, in OnUpdateUI
File "AvsP.pyo", line 801, in UpdateCalltip
UnboundLocalError: local variable 'iArgPos' referenced before assignment
Traceback (most recent call last):
File "AvsP.pyo", line 1292, in OnUpdateUI
File "AvsP.pyo", line 801, in UpdateCalltip
UnboundLocalError: local variable 'iArgPos' referenced before assignment

[Fizick]

qwerpoi,
please look to this thread:
http://forum.doom9.org/showthread.php?t=94768

[Alain2]

French translation updated :)

Traceback (most recent call last):
File "AvsP.pyo", line 1292, in OnUpdateUI
File "AvsP.pyo", line 790, in UpdateCalltip
NameError: global name 'charBefore' is not defined
Traceback (most recent call last):
File "AvsP.pyo", line 1355, in OnSetFocus
File "AvsP.pyo", line 790, in UpdateCalltip
NameError: global name 'charBefore' is not defined
Traceback (most recent call last):
File "AvsP.pyo", line 1292, in OnUpdateUI
File "AvsP.pyo", line 790, in UpdateCalltip
NameError: global name 'charBefore' is not defined

[zemog]

@qwerpoi
Thanks for the update.

[check]

Hi qwerpoi, I'm playing around with building an x264 encoding frontend that is launched from avsp. Are there any problems with directly creating new wxpy frames (aka windows) and loading them as though it was a normal python environment? I've uploaded a sample GUI model here for you to test with: http://paste.animeneko.net/389
At this stage I am planning to launch the options configurator in the AvsP environment, and then to launch a separate process that will be what interacts with x264 (so you don't need to leave AvsP open for the duration of encoding).

As you can see I'm pretty early into the coding, so all thoughts from all - even thoughts about major redesigns of the system - will be graciously accepted :)

[~bT~]

AVSp should be integrated into MeGUI :D

[qwerpoi]

as you wish.

[Thu Jun 07 10:11:54 2007]
Traceback (most recent call last):
File "AvsP.pyo", line 1292, in OnUpdateUI
File "AvsP.pyo", line 801, in UpdateCalltip
UnboundLocalError: local variable 'iArgPos' referenced before assignment
Hm, this bug was fixed with the last bugfix, it doesn't seem to be the same bug you're reporting. If you ever manage to activate the memory-intensive bug, check the log files again, see if you get any new messages. Otherwise, it may not be directly related to AvsP, I'll try and investigate the matter further.

qwerpoi,
please look to this thread:
http://forum.doom9.org/showthread.php?t=94768
Interesting discussion, it seems the [* *] syntax is favored at this point. It means I would have to change things a bit in AvsP (mainly the syntax highlighting code), I don't think it would cause any major compatibility issues. I'll look into it some more thought, though.

French translation updated :)

Traceback (most recent call last):
File "AvsP.pyo", line 1292, in OnUpdateUI
File "AvsP.pyo", line 790, in UpdateCalltip
NameError: global name 'charBefore' is not defined

Thanks for the translation update. The bug you reported occurs when you have "Frequent calltips" turned off, sorry about that. This bug will be fixed in the next version, but in the meantime you can download AvsP_bugfix2_v1.4.0.zip (http://avisynth.org/qwerpoi/upload/AvsP_bugfix2_v1.4.0.zip), which contains a single file named AvsP.pyo. Close AvsP, put AvsP.pyo in the same directory as AvsP.exe (replace any older ones if you downloaded any earlier bugfix), start up AvsP and the new bug should be fixed.

@qwerpoi
Thanks for the update.
Thanks for the translation update, I'll update the links when the attachment is approved.

Hi qwerpoi, I'm playing around with building an x264 encoding frontend that is launched from avsp. Are there any problems with directly creating new wxpy frames (aka windows) and loading them as though it was a normal python environment? I've uploaded a sample GUI model here for you to test with: http://paste.animeneko.net/389
At this stage I am planning to launch the options configurator in the AvsP environment, and then to launch a separate process that will be what interacts with x264 (so you don't need to leave AvsP open for the duration of encoding).
Interesting stuff, I'll take a closer look at it when I get some time. As far as I know there shouldn't be any problems creating new wxp frames from AvsP, but running the encoder in a separate process may have some issues, I'll look into that as well.

AVSp should be integrated into MeGUI :D
I'm certainly not opposed to the idea, but since I don't really use MeGUI myself, it would fall on someone else to actually carry through with the idea. If anyone wants to try, let me know if I can be of help :).

[Alain2]

The bug you reported occurs when you have "Frequent calltips" turned off, sorry about that. This bug will be fixed in the next version, but in the meantime you can download AvsP_bugfix2_v1.4.0.zip (http://avisynth.org/qwerpoi/upload/AvsP_bugfix2_v1.4.0.zip), which contains a single file named AvsP.pyo. Close AvsP, put AvsP.pyo in the same directory as AvsP.exe (replace any older ones if you downloaded any earlier bugfix), start up AvsP and the new bug should be fixed.
That was quick! Thx for the fix, it was unusable before and it works fine now :)

[check]

Interesting stuff, I'll take a closer look at it when I get some time. As far as I know there shouldn't be any problems creating new wxp frames from AvsP, but running the encoder in a separate process may have some issues, I'll look into that as well.Hmm, I've had a think about this new issue you brought up but I can't see where the problem is at all. Could you spend a few lines explaining?

I'm certainly not opposed to the idea, but since I don't really use MeGUI myself, it would fall on someone else to actually carry through with the idea. If anyone wants to try, let me know if I can be of help :).
It's probably somewhat difficult as meGUI runs in .NET. I guess you could run it through ironpython, but to me at least it's getting to more trouble than it's worth. There are also a whole bunch of other questions about how to integrate it into the workflow, but I'm sure those could be hammered out.

[qwerpoi]

I've uploaded a sample GUI model here for you to test with: http://paste.animeneko.net/389
At this stage I am planning to launch the options configurator in the AvsP environment, and then to launch a separate process that will be what interacts with x264 (so you don't need to leave AvsP open for the duration of encoding).
I've played around a bit with your sample, very impressive stuff (puts my avs2avi dialog to shame :)). I'm not really familiar with x264, so I can't give very specific feedback, but in general I would say you may want to take some options from the main tab and put them into a third tab (I'm not positive, but I'm guessing the average user wouldn't tweak b-frame, m.e., quant matrix options very frequently). Also, I always did like presets, back in the day I thought enc (http://jonny.leffe.dnsalias.com/enc/index.htm) did a decent job with them.

Hmm, I've had a think about this new issue you brought up but I can't see where the problem is at all. Could you spend a few lines explaining?
It was just me overthinking the matter. Basically it would be problematic if you went the route I did with the avs2avi dialog, where AvsP was communicating with the avs2avi process to update the dialog's progress bar, allow the user to cancel, etc. If you don't need that kind of graphical feedback, then there shouldn't be any issue at all.

[check]

Heh, yeah, I'm planning on producing system where the layout of subsections is customisable so others don't complain about my layout choice (which is basically to fit as much onto one page as possible). As for presets, I downloaded enc and found it's much the same as what I'm planning to create :^)

[Veiga]

Sorry qwerpoi and users that download the first translation for v.140. I make a mistake when interpretation (fold) term.
Now I thing best.

[krisq]

Asterisk on the title bar in the undocked preview window doesn't disappear when I save the script. That's, until I refresh the window of course. It's been like that since forever but since no one reported it, I will. I guess it's by design but it can be pretty misleading when script window is hidden under the preview. Cheers :)

[Zarxrax]

I just wanted to report that there still seem to be some unicode bugs in the latest version. I right-click a file and choose to open with avsp; if the filename or path contains a unicode character, avsp will fail to open it.

[RedDwarf1]

I find this editor very useful when experimenting (I am only just starting with Avisynth) with scripts.

I have been trying to change the white background on the script window and after changing every background color to a more eye friendly color that suits my eyes I still have been unable to get rid of the white.

Some people seem to love white but I hate it, even with my Monitor set to sRGB (a low color temperature) I still find it very difficult to look at.

Is there any way that I have missed to change it?

[qwerpoi]

I just wanted to report that there still seem to be some unicode bugs in the latest version. I right-click a file and choose to open with avsp; if the filename or path contains a unicode character, avsp will fail to open it.
I tried it out, couldn't reproduce the error on my laptop. Could you tell me the exact error reported by AvsP? It should be saved in the avsp_error_log.txt.

I have been trying to change the white background on the script window and after changing every background color to a more eye friendly color that suits my eyes I still have been unable to get rid of the white.
No, it seems there currently isn't a way to do it. I'll very likely release a small bugfix update soon, I'll try and add this fix to the update as well.

[RedDwarf1]

I hope so, thanks. I look forward to it as it is the only thing I dislike about it. Otherwise it is a fantastic tool which makes AVIsynth scripting so much easier.

[Zarxrax]

I tried it out, couldn't reproduce the error on my laptop. Could you tell me the exact error reported by AvsP? It should be saved in the avsp_error_log.txt.

There seems to be 2 possible outcomes that I have discovered so far.
On a pathname that contains a "ö", it will post the following in the error log:

Traceback (most recent call last):
File "run.py", line 6, in <module>
File "AvsP.pyo", line 10961, in main
File "wxp.pyo", line 249, in __init__
File "wx\_core.pyo", line 7700, in __init__
File "wx\_core.pyo", line 7352, in _BootstrapApp
File "AvsP.pyo", line 10947, in OnInit
File "AvsP.pyo", line 3662, in __init__
File "AvsP.pyo", line 3769, in ProcessArguments
File "AvsP.pyo", line 7194, in OpenFile
File "AvsP.pyo", line 7750, in InsertSource
File "AvsP.pyo", line 7783, in GetSourceString
UnicodeDecodeError: 'ascii' codec can't decode byte 0xf6 in position 27: ordinal not in range(128)

When I use japanese text in the path, there is no error message, but after rightclicking a file and choosing to open the file with avsp, avsp simply launches without opening the file.

[signal]

1) Include in the compiled project the msvcr71.dll. At the moment it doesn't start if it doesn't find.

I don't think I'm allowed to distribute msvcr71.dll, I guess I should mention the requirement somewhere (but honestly, a huge number of programs require it, so it's a non-issue for most users).

You have permission. Microsoft has made this a non-system file due to version conflicts and ask that it be distributed with the application and stored in the application directory from now on.

http://support.microsoft.com/kb/326922

When you build an application in Microsoft Visual Studio 2005 or in Microsoft Visual Studio .NET , and the application uses the C run-time libraries (CRT), distribute the appropriate CRT DLL from the following list with your application and install the DLL in your Program Files directory: ...[snip]... Do this instead of installing the DLL in the system directories. Do not assume that the DLL already exists in the system directories.

The shared CRT DLL has been distributed by Microsoft in the past as a shared system component. This may cause problems when you run applications that are linked to a different version of the CRT on computers that do not have the correct versions of the CRT DLL installed. This is commonly referred to as the "DLL Conflict" problem.

I got bit by not having it on a fresh XP install and in looking for it on another system (recently installed as well) found various flavors existing only in the program files tree, but not in the windows one. So recent apps are following this as well.

Would be great to have AvsP good to go from the start (and with the correct version of msvcr71.dll that you compiled with to go with it).

[qwerpoi]

Sorry for not getting this up sooner, here's a bugfix update which should fix a few bugs some people have pointed out recently:

http://avisynth.org/qwerpoi/upload/AvsP_bugfix3_v1.4.0.zip

Make sure you are using AvsP v1.4.0, get the AvsP.pyo from the zip file and place it in the same directory as AvsP.exe (overwrite the older AvsP.pyo if it exists). The fixes will be in effect the next time you start up AvsP. Just so you know, here are the bugs this update fixes in v1.4.0:
+ fixed calltip bug with parentheses inside string (thanks niiyan)
+ fixed calltip bug with filters with zero arguments (thanks niiyan)
+ fixed calltip bug with "Frequent calltips" turned off (thanks Alain2)
+ fixed asterisk on title bar in separate video window (thanks krisq)
+ fixed color customization to allow non-white default background (thanks RedDwarf1)
+ fixed (?) open with unicode filename bug (thanks Zarxrax)

The first three bugs were fixed in previous bugfixes, the last three are newer. The 5th fix means you can set up AvsP with a dark background for the script, just go to "Options -> Fonts and colors..." and configure the default background color. You'll have to change quite a few other colors to completely get rid of the white background, I may make an easier way to do this in a later release. And I *think* I fixed the unicode bug Zarxrax pointed out, please let me know if it still occurs.

I'm currently working hard on the next release, it's shaping up quite nicely (with features such as automatic sliders, resize, calculator, bitrate calculator, encoding gui, etc). There's still a lot of work I need to do, so I can't guarantee when it will come out, hopefully within a month.

Would be great to have AvsP good to go from the start (and with the correct version of msvcr71.dll that you compiled with to go with it).
Okay then, the next version of AvsP will include the msvcr71.dll, thanks for the clarification.

[LL00]

AvsP file information displays RGB color space, but when I put info() in the .avs, It displays YU12.
can you check that?

[honai]

with features such as automatic sliders, resize, calculator, bitrate calculator, encoding gui, etc

Wow, that's impressive, thanks for your efforts, looking forward to it!

[Zarxrax]

And I *think* I fixed the unicode bug Zarxrax pointed out, please let me know if it still occurs.

The first unicode problem I pointed out is fixed now.
However, it still does not seem to work with files which contain japanese text. I'm not sure what, if anything makes these files any different. I right-click on a files with a japanese filename, and choose open with AvsP, and AvsP simply opens up a blank page. No error message.

[ChiDragon]

LL00, :script:, colorspace reporting works fine here.

[qwerpoi]

AvsP file information displays RGB color space, but when I put info() in the .avs, It displays YU12.
can you check that?
Make sure you are using a recent version of Avisynth (I'm using 2.5.7), since AvsP isn't able to directly communicate with older versions of Avisynth.

The first unicode problem I pointed out is fixed now.
However, it still does not seem to work with files which contain japanese text. I'm not sure what, if anything makes these files any different. I right-click on a files with a japanese filename, and choose open with AvsP, and AvsP simply opens up a blank page. No error message.
Yeah, I figured it out, it looks like the Python language specifially has trouble decoding japanese unicode strings properly. Oddly enough, wxPython (the gui library used by AvsP) can handle them fine, so a clunky workaround is to open a japanese file with AvsP, which gets you a blank page, then drag and drop the file on to the blank page. I'll try and see if there's some downloadable Python codecs or some other possible fix to the problem in the meantime.

[LL00]

Make sure you are using a recent version of Avisynth (I'm using 2.5.7), since AvsP isn't able to directly communicate with older versions of Avisynth.


Yes, you right, with 2.5.7 it's fine. I used 2.6.0.0, that's why I got this wrong info with avsp.

[RedDwarf1]

Thanks qwerpoi for adding the ability to change the background colour. That has made a big difference to it's usability for me. I will no longer have to move the video window up to cover as much of the white text window as I can as it did affect how I could see the video having bright white showing. :D :thanks:

[AlanHK]

A while ago qwerpoi was kind enought to give me a macro to save bookmarks (below).

Not being a python coder myself, I wonder if someone can advise how to input a list of bookmarks to Avsp?

macro to extract bookmark list
filename = avsp.GetSaveFilename(title='Save bookmarks to text file')
f = open(filename, 'w')
for bm in avsp.GetBookmarkList():
f.write(str(bm)+'\n')
f.close()

[qwerpoi]

Not being a python coder myself, I wonder if someone can advise how to input a list of bookmarks to Avsp?
Assumming you want to get the bookmark list from the previously written text file (ie, a bookmark frame on each line), the macro would look like this:
filename = avsp.GetFilename(title='Get bookmarks file')
f = open(filename, 'r')
text = f.read()
f.close()
bookmarks = text.split()
avsp.SetBookmark(bookmarks)
Here I'm taking advantage of the fact that the SetBookmark() function can take in a list of frame numbers to set as bookmarks (as opposed to one bookmark at a time). You might also notice that in this macro I passed the function a list of strings instead of numbers - the function automatically does the string to integer conversion for you. Hope that helps.

[callmemusashi]

Excellent app! It's been a while since I had to convert a Real Media file, and the script I thought I was supposed to use wasn't working. I tried your tool, and it worked immediately. Kick ass. (Turns out all I was doing wrong was spelling the damn file incorrectly, but that doesn't mean this tool is any less helpful ;)

[AlanHK]

Assumming you want to get the bookmark list from the previously written text file (ie, a bookmark frame on each line), the macro would look like this
Thanks.

-- I note that response gets very twitchy when I load 188 bookmarks. Not that many people would be doing that.

[qwerpoi]

Just to let you guys know, I'll be releasing the next version of AvsP in about a day or two. Unless there are any major objections, I'm going to release it in a new thread, since it's stepping up to version 2.0.0, which won't be 100% backwards compatible with older versions. Also, this thread's getting a bit long (I believe it's the largest in the avisynth forum!), making it a bit hard to wade through for info.

[gomguk]

AvsP 2.0.2 Korean language file.
Making(Credit) by "Hani"(name).

Download URL:
http://zizybe.bcpark.net/data/avsp202_korean_lang.zip

Please register avsP official website. ^^

[azsd]

nice tools! I have to open three Virtualdubmod to load differnt sripts and click between taskbar til yesterday.
Is there any option to make the priview windows floatable or dock to right of editor?
I have lots of blank on the right of scripts.

[talen9]

This is an OLD thread! Or, better, it is about an old version of AvsP.

Please refer to this thread (http://forum.doom9.org/showthread.php?t=129385) instead :)

[torpare]

I tried out using VirtualDub as external player for previewing, but decided I preferred the internal preview. There seemed no way to revert other than by reversing my steps, ie removing the path to VDub from the box labelled 'External player' in 'Program Settings -> General tab'. So that's what I did.

Since then, every time, a blank preview window comes up and the status bar continues to show "Run the script with an external program" when the mouse cursor is held over the 'play' button. I can't see any way to restore the internal preview.

Can anybody please tell me what I should be doing that I'm not?

[talen9]

Ahem ... did you have a look at (my) post right above yours? ;)