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

foxyshadis

3rd May 2007, 14:43

That particular location is trying to find the location of the avisynth install, so whatever location is in HKLM\Software\Avisynth\@Default in the registry is probably pointing to a location with unicode characters in it. value.encode('ascii') fails on those types of conversions.

I guess one fix would be to move avisynth into another place, like the avsp folder, for now.

Something that'll help people in the future would be replacing line 3399-3400,

if os.path.isdir('C:\\Program Files\\AviSynth\\'):
self.options['avisynthdir'] = 'C:\\Program Files\\AviSynth\\'

with

if os.path.isdir(os.environ.get("PROGRAMFILES")+'\\AviSynth\\'):
self.options['avisynthdir'] = os.environ.get("PROGRAMFILES")+'\\AviSynth\\'

which will work with international installs and anything on non-standard drives, even though that won't fix this exact error. For fixing, is .encode('ascii') necessary? It works fine without, but I also haven't tested it on a folder with upper characters.

AlanHK

3rd May 2007, 17:58

Is there a function to get the bookmark list as text?

I know I could make a macro if there isn't, but would rather not reinvent the wheel.

Also, I saw a function "Insert bookmark Trims (keyboard shortcut Ctrl-I), AvsP will insert a sequence of Trim commands into your script based on the bookmarks" which appears to not be in the current version, perhaps seen as replaced by the Trim Editor. If so, is there a way for the Trim editor to use bookmarks?

And more ambitiously, is there a way to input bookmarks &/or trims as a list instead of through the GUI?

qwerpoi

3rd May 2007, 21:26

Hello folks,

I really would like to congratulated AvsP developer for its wonderful work. Excellent software! I have tried to run AvsP 1.38 in my system, but it never runs it always displays this error log:

[Wed Apr 25 12:13:09 2007]
Traceback (most recent call last):
File "AvsP.py", line 9301, in ?
File "wx\_core.pyo", line 7700, in __init__
File "wx\_core.pyo", line 7352, in _BootstrapApp
File "AvsP.py", line 9293, in OnInit
File "AvsP.py", line 2988, in __init__
File "AvsP.py", line 3407, in getOptionsDict
UnicodeEncodeError: 'ascii' codec can't encode characters in position 28-29: ordinal not in range(128)

Somebody help me! I really love this software because I use Avisynth several times for video editing, so AvsP is a must for me. Please, any ideas?

See you later,

Aeolis
It looks like foxyshadis is right, basically AvsP is supposed to get the Avisynth installation directory from the registry but choked on the unicode pathname. It looks like I'll release a bugfix version as soon as I can (hopefully within the week, but I can't guarantee it). The bugfix version will have no new messages to make it easier on translators.

Hi qwerpoi,

it's me again, :)
maybe there is an alternative solution for COM. For my app it is possible to use PIPE instead of COM. I have done a test with new installed Python on my system :) :
import subprocess
process = subprocess.Popen('C:/test.exe', shell=True, stdout=subprocess.PIPE)
process.wait()
Text = process.stdout.read()

This works on system, but not with AvsP-Macro.
Error-MsgBox is: "an integer is required"
and it is meant to "stdout=subprocess.PIPE" in Popen
I also have tried "stdout=-1", what work on system too, but also not in AvsP-Macro. (AvsP binary Version 1.3.7 + 1.3.8)
(My PythonVersion on system is 2.5)

Rachima
I get the same error using AvsP 1.3.8, which was compiled using Python 2.4. I don't get the error when compiling AvsP with Python 2.5. So hopefully the next release will allow things to work properly. If you could use subprocess instead of win32com.client, that would be fantastic, since it will keep the distribution size down. I'll still consider including win32com if there are other developers who absolutely require it.

Is there a function to get the bookmark list as text?

I know I could make a macro if there isn't, but would rather not reinvent the wheel.

Also, I saw a function "Insert bookmark Trims (keyboard shortcut Ctrl-I), AvsP will insert a sequence of Trim commands into your script based on the bookmarks" which appears to not be in the current version, perhaps seen as replaced by the Trim Editor. If so, is there a way for the Trim editor to use bookmarks?

And more ambitiously, is there a way to input bookmarks &/or trims as a list instead of through the GUI?
Other than a macro, there isn't a way to save the bookmark list as a text file. In case someone wants it, here's a simple macro to do it:
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()
Also, you're correct, the function "Insert bookmark trims" was removed and replaced with the trim editor. If you want to use the bookmarks for trimming you can write a macro, but it may make more sense to simply insert selection start/stop points using the Home and End keyboard shortcuts instead of using bookmarks.

And currently there's no way to input bookmarks other than the gui or saving a session. If it would be helpful, I could add a macro to set bookmarks, that way you could set bookmarks from a given text file.

AlanHK

4th May 2007, 04:58

Other than a macro, there isn't a way to save the bookmark list as a text file. In case someone wants it, here's a simple macro to do it:

Thanks, that's good.
How could I just paste the list to the clipboard?

If it would be helpful, I could add a macro to set bookmarks, that way you could set bookmarks from a given text file.

Thanks. It might be useful to stash them in the AVS file in some #~ format, like sliders, so they could be reloaded semi-automatically (you should have an option to load or ignore).

it may make more sense to simply insert selection start/stop points using the Home and End keyboard shortcuts instead of using bookmarks.
That works, but the action of creating the Trim list changes the bookmarks, which I want to keep in their original places to check transitions.
What I'm doing is making a sequence of nologo filters, marking on and off as the logo appears with bookmarks, so the original trim list format was closest to that; I don't actually want to delete anything from the video, just run a filter on different sections.
If I persist I can probably work out how to make a Python macro to do it all, but at the moment I use Ultraedit.

I just found the "scrap window". It seems that the toggle off control-P doesn't work if the cursor is in the scrap window...

An observation: I see a few spelling mistakes in the macro files comments. Eg:
# This example shows how to use AvsP's macros to turn AviSynth into an
# all-puropose image editor. It's similar to the batch example, but instead

And in HTML docs:

Trimming video is fairly straightforward in AviSynth with the Trim() command. However, it can get a bit unweildy

Doing a spellcheck would find most of these.

Rachima

4th May 2007, 22:33

Hi,

I get the same error using AvsP 1.3.8, which was compiled using Python 2.4. I don't get the error when compiling AvsP with Python 2.5. So hopefully the next release will allow things to work properly.

by testing I accidently run this code in AvsP 1.3.8 instead of my IDE, and was wondering that it now runs without errors:
process = subprocess.Popen([exefile, params], shell=False, stdin=subprocess.PIPE, stdout=subprocess.PIPE, stderr=subprocess.STDOUT)
when explicitly set all three streams, stdin stdout stderr, it runs. Just curious.

If you could use subprocess instead of win32com.client, that would be fantastic, since it will keep the distribution size down. I'll still consider including win32com if there are other developers who absolutely require it.

To use COM maybe necessary or _must_be, when there is (more) interaction between AvsP and the called App. For my app, it is only necessary to get an initially input and to write the result back.
I have attached a sample Macro, with dummy exe and even Sourcecode in VB6 showing how to use stdIn & stdOut.

(I also have decided to write my app as a AvsP-Plugin only, because now I have seen how much power there is in AvsP. :thanks: )

Rachima

qwerpoi

6th May 2007, 03:22

New version 1.3.9, download from the AvsP download page (http://avisynth.org/qwerpoi/Download.html) or from the mirror (http://www.savefile.com/files/696932). This version is actually compatible with both XP and win98. As a result, the directory structure is a little different, so in order to upgrade, you should unzip the file to a new directory and transfer over your *.dat files (you can read a bit more detail at the download page). This is a bugfix version, so the changelog's relatively small:

* remember the last saved image path (suggested by 3ngel)

* changed "Show calltip" to work when cursor is in filter name (thanks AlanHK)

* changed editor to properly clear undo buffer when loading a file

* merged windows xp and 98 versions

+ fixed parity info reported by AvsP (thanks krisq, ChiDragon)

+ fixed crash when switching zoom modes (thanks Alain2)

+ fixed unnecessary scrollbars with zoom "fit inside window" (thanks foxyshadis)

+ fixed unicode bug when saving script

+ fixed unicode bug with recent file list (thanks Henrikx)

+ fixed unicode bug with Avisynth install directory (thanks Aeolis, foxyshadis)

+ minor fixes to window layout code
The changes in this version are pretty much self explanatory. The size of the distribution file is actually smaller this version, for those curious it was mainly achieved by the different directory structure and using upx lzma compression.

In order to make things easier for translators, this version has no new messages, ie, the v1.3.8 translation is compatible with v1.3.9. There were some fairly easy feature requests that did not make it to this version because I didn't want to add any new messages, so for those requesters, I offer a small apology, you'll have to wait patiently for the next version. The main reason I wanted to release this version now is because it seems AvsP wouldn't run at all if you installed AviSynth in a directory with unicode characters, a big mistake. Hopefully everything works properly now.

Since it's important, I'll emphasize one last time that to upgrade from an older version you can't simply replace the AvsP.exe anymore since it's no longer contained in a single executable (read more details here (http://avisynth.org/qwerpoi/Download.html)). Anyway, I'm guessing the next version won't be for a while, since I still have a lot of work to do on the automated user slider concept. Still, be sure to report back with any new problems or requests.

Alain2

6th May 2007, 09:32

Thanks qwerpoi, will try asap :) About the workload for translators, to be honest I don't see the problem, the last release had a few more strings to translate but the amount was similar to previous versions (looking in the translation.py file I see that I translated similar amounts for 1.2.1), it didn't take me long to translate them. Don't restrain yourself for this :)

Henrikx

6th May 2007, 10:34

the v1.3.8 translation is compatible with v1.3.9.
German translation v.1.3.8 does not function.
Any idea ?

max24

6th May 2007, 12:03

Hi,

version 1.3.9 doesn't the file provide "translation.pyo" can it because of it be?

Henrikx

6th May 2007, 13:12

@max24
Maybe ? Only qwerpoi knows !
In moment, i "clean" the old version,but i dont think that is the mistake.I can be mistaken....

Fizick

6th May 2007, 15:23

IMHO,
Rahima's suggestion is important.
It wold be great to have language-independen plugin API in AvsP.
But implementation may be various.

Aeolis

6th May 2007, 15:53

Hello folks,

Thank you very much qwerpoi! Now it works. Thank you.

See you later,

Aeolis :thanks:

Aeolis

6th May 2007, 16:57

Hello folks,

It’s me again. I entered the path to a external player in AvsP Program Options: “C:\Arquivos de programas\Edição e Criação de Filmes e DVD\Media Player Classic\mplayerc.exe” and I had the following error after reopening AvsP:

[Sun May 06 12:02:23 2007]
Traceback (most recent call last):
File "AvsP.py", line 9358, in <module>
File "wx\_core.pyo", line 7700, in __init__
File "wx\_core.pyo", line 7352, in _BootstrapApp
File "AvsP.py", line 9350, in OnInit
File "AvsP.py", line 3026, in __init__
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe7 in position 28: ordinal not in range(128)

So, I decided to erase the option.dat file in AvsP folder and everything went back to normal if I try to enter the external player path the problem gets back. I think there is a Unicode problem to the path of external player too. qwerpoi if you can take a look on that issue I will be really happy and grateful. Thank you one more time for your attention. :) :)

See you later,

Aeolis

lolent

6th May 2007, 17:10

Thanks for the new version qwerpoi ;) , I will test it

Henrikx

6th May 2007, 17:14

I create a "clean" new German Language file.( 1:1) But nothing.
AvsP will not work with the new,too ?
I have no more ideas !!
Language files :
http://forum.gleitz.info/showpost.php?p=301023&postcount=14

Terranigma

6th May 2007, 19:00

krisq

6th May 2007, 19:49

:thanks: qwerpoi :D

qwerpoi

6th May 2007, 19:55

German translation v.1.3.8 does not function.
Any idea ?
Oh cr**! The new directory structure alters how AvsP looks for python files to import - you'll need to add the translation.py file into the library.zip file in the lib directory (just drag translation.py into the zip file). Very sorry about that. Sigh. I may release another version within a week which will have this fixed up.

Thanks qwerpoi, will try asap :) About the workload for translators, to be honest I don't see the problem, the last release had a few more strings to translate but the amount was similar to previous versions (looking in the translation.py file I see that I translated similar amounts for 1.2.1), it didn't take me long to translate them. Don't restrain yourself for this :)
I wasn't so worried about the amount of translation work, I was just trying to give translators some time to catch up. Right now it's a little clunky when you are in the middle of translating a new version and a newer version comes out. Again, I'm going to try and make some sort of tool that simplifies things, roughly speaking it will import an older translation file and place all identical messages into the current one.

IMHO,
Rahima's suggestion is important.
It wold be great to have language-independen plugin API in AvsP.
But implementation may be various.
It's something that has crossed my mind. I believe that Rahima's approach works well, the plugin is written as an executable which can communicate with stdout pipe, and interfaced through AvsP with a macro. The only thing that needs changing is that there should be a separate directory for plugins (instead of adding it to the macros) and that there should be more macro functions exposed for plugins to give direct access to some of AvsP's databases. I'll try and rewrite the avs2avi gui as a plugin and see how it goes.

I entered the path to a external player in AvsP Program Options: “C:\Arquivos de programas\Edição e Criação de Filmes e DVD\Media Player Classic\mplayerc.exe” and I had the following error after reopening AvsP:

[Sun May 06 12:02:23 2007]
Traceback (most recent call last):
File "AvsP.py", line 9358, in <module>
File "wx\_core.pyo", line 7700, in __init__
File "wx\_core.pyo", line 7352, in _BootstrapApp
File "AvsP.py", line 9350, in OnInit
File "AvsP.py", line 3026, in __init__
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe7 in position 28: ordinal not in range(128)
Oof, thanks for bringing it up. I'll check it out and have it fixed by the next version.

lolent, have you been able to vent that problem you've been having with AvsP? I have a pretty good idea what's causing the problem, as i've gotten the same exact error message earlier today that you've shown with the screenshot. It has to do with your plugins/scripts, so it's not an avsp problem. You could fix this by manually going to your plugins folder, right-click and choose "Arrange Icons By Modified"; Then either delete or move your latest modified plugins 1 by 1 while hitting F5 with avsp and see if it generates a preview.
Thanks for pointing this out, I really need to get an faq put together. I'll have the error message be more clear, and perhaps I'll make the error message have a suggestion to examine any unstable plugins as you point out.

Henrikx

6th May 2007, 23:07

@qwerpoi
THX
Difficult birth!
Update German Translation.......

lolent

7th May 2007, 00:00

lolent, have you been able to vent that problem you've been having with AvsP? I have a pretty good idea what's causing the problem, as i've gotten the same exact error message earlier today that you've shown with the screenshot. It has to do with your plugins/scripts, so it's not an avsp problem. You could fix this by manually going to your plugins folder, right-click and choose "Arrange Icons By Modified"; Then either delete or move your latest modified plugins 1 by 1 while hitting F5 with avsp and see if it generates a preview.

oh, that's a good idea ! Thank you Terranigma ;)
I will try that and found which plugin causes the problem by testing them one bye one :)

EDIT :
I solve my problem :)
I had some ***SSE3.dll that my cpu doesn't support (PIV 2.4 GHZ) that I had forgotten to delete from my avisynth plugin directory ^^
Thx again Terranigma ;)

Alain2

7th May 2007, 12:40

zemog

7th May 2007, 20:28

qwerpoi, :thanks: for the new versions.

killerhex

9th May 2007, 06:30

can this tool analyse wmv files

qwerpoi

9th May 2007, 08:04

Arf the window width resizing bug is still there, but the sliders section automatically hides again when I don't use any :thanks:

btw a funny thing is when I close avsp, both windows disappear (also from the task bar), and for some reason the preview window flashs back (in the task bar as well) and disappear again. Not a big issue, just thought to mention :)
I figured out the window resize bug, it'll be fixed in the next version. I'll try and see what's causing the flashing window.

qwerpoi, :thanks: for the new versions.
Thanks for the updated translation, I've updated the links accordingly. Just as a reminder to those using translation files, there's a bug in v1.3.9 that requires you to add the translation.py file in the library.zip file (in the lib directory, just drag and drop). This too will be fixed in the next version, sorry about the inconvenience.

can this tool analyse wmv files
Huh? If you mean can AvsP work with wmv files, a simple script like DirectShowSource("test.wmv") should do the trick. You can read the overview (http://avisynth.org/qwerpoi/Overview.html) if you want to find out about what AvsP is and what it isn't.

canuckerfan

9th May 2007, 20:30

in the save as avi dialogue... is priority 0 normal and 2 high, with 1 in between?

Alain2

11th May 2007, 20:41

Feature request: when using a separate video window, fully separate its behaviour from the script window. At the moment:
- minimising the script window minimises the video window as well
- if script window is minimised and video window maximised, making the script window appear again change the video window to a flotting one (not maximised) and refreshes it

qwerpoi

11th May 2007, 23:03

in the save as avi dialogue... is priority 0 normal and 2 high, with 1 in between?
The save as avi dialog is simply a frontend for avs2avi, priority 0/1/2 is idle/normal/above normal, respectively.

Feature request: when using a separate video window, fully separate its behaviour from the script window. At the moment:
- minimising the script window minimises the video window as well
- if script window is minimised and video window maximised, making the script window appear again change the video window to a flotting one (not maximised) and refreshes it
Sounds reasonable, I'll see what I can do.

Incidentally, I won't be in town for the next week or so, my internet access there will be limited, so I may not be able to reply during that time. But I wanted to give you guys something to look forward to, so check out this screenshot (http://avisynth.org/qwerpoi/AvsP_v2.00_preview.jpg) of the next version of AvsP. There's a lot of details that still need ironing out, but what you're looking at is user sliders that have been automatically generated without any manual input. That means you just write a script, show the video, and you'll automatically get user sliders for every specified argument in the script. Not just user sliders, but string list selectors, boolean radio boxes, and filename pickers. Without any manual input. And if you're worried that there will be too many user sliders, you can hide user sliders for any filter by clicking the filter name, and there will be ways to customize which user sliders to automatically create. This version will hopefully be released within the month, it's going to be smoking...

~bT~

11th May 2007, 23:47

this prog is getting crazier by the day! awesome! waiting for v2.00

digitalone

12th May 2007, 06:10

awesome stuff qwerpoi! looking forward to v2.0!!

Zarxrax

12th May 2007, 23:47

Wow, that looks awesome!

Feature request though:
Could we get some hotkeys for the DeleteFrame() and DuplicateFrame() functions? Sometimes there will be frames in the video that are just screwed up for some reason, and those functions are useful for cleaning up areas like that.

Also, would it be possible to give the interface higher priority than the video display? The reasoning being, you might make a mistake and do something which will take avisynth a LONG time to process a frame. In this situation it would be nice to be able to turn off the video display so you could fix your mistake immediately instead of having to wait on the frame to render.

qwerpoi

14th May 2007, 02:02

Could we get some hotkeys for the DeleteFrame() and DuplicateFrame() functions? Sometimes there will be frames in the video that are just screwed up for some reason, and those functions are useful for cleaning up areas like that.
Sounds like macros would fit the bill nicely. Make a text file in the macros subdirectory named something like "DeleteFrame.py", and add the following text:
frame = avsp.GetFrameNumber()
avsp.InsertText('\nDeleteFrame(%i)' % frame)
avsp.ShowVideoFrame(forceRefresh=True)
Restart AvsP, when you click on this macro in the Macros menu it will insert the DeleteFrame command with the current frame number at the end of the script and refresh the video. You can then assign a keyboard shortcut to this macro from the "Options -> Configure shortcuts..." dialog (the macros show up at the end of the list). Obviously making a DuplicateFrame macro would be very similar.

Also, would it be possible to give the interface higher priority than the video display?
In order to do this, the video would have to be requested in a separate thread, and threading is unfortunately not my area of expertise. However, I was recently able to get a socket server running in a separate thread for the single instance option some people were requesting, so I'll look it over and give it a try, no guarantees though.

Henrikx

15th May 2007, 09:42

@qwerpoi
CT software collection 11.05.2007 with AvsP
http://www.heise.de/ct/ (German)
Software-Kollektion 3/07, c't 11/07
http://www.heise.de/software/default.shtml?s=cdd&id=51

http://img300.imageshack.us/img300/4310/ctavsplw8.th.png (http://img300.imageshack.us/my.php?image=ctavsplw8.png)

jarthel

19th May 2007, 13:32

any possibility to add find/replace across all the files that are open?

thank you.

jarthel

19th May 2007, 13:40

I'm not sure if this has been asked but here goes:

If I decided to use the "slider" feature, would AvsP automatically remove the extra text I typed?

for example:

deen("w3d", 3, 3, [<"ti", 0, 10, 5>])

would become deen("w3d", 3, 3, 5).

Thanks for the replies.

gzarkadas

19th May 2007, 14:14

@qwerpoi

Could you consider in a future release an additional category, "external function", in dialog "Options"|"Avisynth function definition...", "Function type" field ? Although not that important, it would help to better classify the functions of my library.

Thanks anyway for this great app; I have at last found my Avisynth editor of choice :).

foxyshadis

19th May 2007, 14:56

BruceL

19th May 2007, 15:23

This version will hopefully be released within the month, it's going to be smoking...

@qwerpoi

Sounds like a donation button is in order!

Thank you for all your hard work.

:thanks:

max24

23rd May 2007, 16:49

Is possible AR feature planned?

http://img511.imageshack.us/img511/5189/arzh1.jpg

jamieuk

25th May 2007, 22:29

yer its comming in the future

Zarxrax

26th May 2007, 02:33

krisq

27th May 2007, 11:17

I don't know if anyone else encounters this problem, but most of the time if I try to use the save avi feature it wont work. Sometimes it works, but usually it doesn't. There is no error or anything... it simply doesn't encode anything.

If avsp had some better encoding options, this thing could take over vdub for almost all of my video processing tasks :p

is there any chance that you have spaces in the name of your .avs file?

Is possible AR feature planned?

http://img511.imageshack.us/img511/5189/arzh1.jpg

AFAIK there is AR info on the status bar.

Zarxrax

27th May 2007, 18:07

is there any chance that you have spaces in the name of your .avs file?
That's probably it. Spaces aren't supported, I take it.

qwerpoi

29th May 2007, 17:41

I'm back, just wanted to let you guys know that v2.0.0 is progressing smoothly. I might release a preview version in a couple of days, since I could use some help completing the filter database necessary for automatic sliders.

CT software collection 11.05.2007 with AvsP
http://www.heise.de/ct/ (German)
Software-Kollektion 3/07, c't 11/07
http://www.heise.de/software/default.shtml?s=cdd&id=51

That's very cool! I'll add those links to the About page when I get the chance.

any possibility to add find/replace across all the files that are open?
Good request, unfortunately it's a bit tricky to implement. I'll add it to my todo list, so we'll see.

Could you consider in a future release an additional category, "external function", in dialog "Options"|"Avisynth function definition...", "Function type" field ? Although not that important, it would help to better classify the functions of my library.

Thanks anyway for this great app; I have at last found my Avisynth editor of choice :).
Glad you like the program! As far as an "external function" category, I'm not sure what that would be for. The categories are named a bit confusingly, here's how it looks to me:

Internal filter: core filters (avisource, levels, etc)
External filter: 3rd party dll plugins (decomb, undot, etc)
Internal function: Avisynth-language functions (assert, apply, etc)
Clip property: (width, height, framerate, etc)
User-defined: Non-dll avisynth functions (LimitedSharpen, mftoon, etc)

I think "user-defined" covers what you want for "external function". Let me know if I've misunderstood something. In any case, it's probably a good idea to rename those categories to be a bit more consistent with the Avisynth documentation notation.

Is possible AR feature planned?
Yes, as jamieuk noted, it will come in the form of a resize calculator in the Tools menu. Unfortunately it's a lot of work to do it right and I'm currently busy with developing the automatic sliders for the upcoming release, so I can't give you a good idea when it will happen. In the meantime, as krisq pointed out, the aspect ratio is given in the status bar whenever the video has focus, combine that with the crop editor (Video -> Crop editor...) and you have a basic tool for managing aspect ratios.

I don't know if anyone else encounters this problem, but most of the time if I try to use the save avi feature it wont work. Sometimes it works, but usually it doesn't. There is no error or anything... it simply doesn't encode anything.
Spaces in the script filename caused this to occur, but I believe this problem was fixed as of version 1.3.8. If it's still occuring with a newer version, let me know.

If avsp had some better encoding options, this thing could take over vdub for almost all of my video processing tasks :p
Yeah, that's my thought as well. Unfortunately, virtualdub is an extremely comprehensive and well-written program, so it's a daunting task to say the least. The compromise is to make a gui wrapper around a more comprehensive command line encoder. I really like avs2avi, but it was meant for quick encoding tasks, and doesn't cover everything needed for video processing (audio handling, etc). I'm not really familiar with other tools, but it may be something I'll give strong focus on after this upcoming release.

gzarkadas

29th May 2007, 20:07

...I think "user-defined" covers what you want for "external function"...

Yes, if I were the end-user. I am of course when I use the app, but as a distributor of a package I would prefer not to clutter the "user-defined" category with ~200 functions (see the relevant avsp macro is in this post (http://forum.doom9.org/showthread.php?p=1004300#post1004300)) and let that category for the end-user, so as to easily distinguish his/her own functions. This could benefit other distributors also.

For the moment I just pretending my functions to be "internal functions" and giving the user the ability to change my preferences by setting some variables inside the .py macro file. I could continue with that because it is just a matter of convenience, but then I noticed there is a free corner in the related radiobuttons space that "calls" for filling it :D.

Thanks in any case for the time you took to review my request :), whatever the result will be.

ChiDragon

29th May 2007, 20:57

I might release a preview version in a couple of days, since I could use some help completing the filter database necessary for automatic sliders.

Now that AvsP can make calls directly to the AviSynth script environment, isn't it possible to get loaded filters and their arguments directly from AviSynth instead of making a separate database?

tsp

29th May 2007, 21:17

ChiDragon: No as there are no way to know what range/inputs that are valid for the different arguments. Maybe this was something that could be implemented in avisynth 2.6?

Zarxrax

29th May 2007, 22:57

I just upgraded to the newest version, and it seems unicode doesn't work now. I could swear it worked in earlier versions though.

Also, it wont automatically suggest a default filename for the avs if I load the input file via directshowsource. When I use avisource it will suggest a filename.

krieger2005

30th May 2007, 07:47

ChiDragon: No as there are no way to know what range/inputs that are valid for the different arguments. Maybe this was something that could be implemented in avisynth 2.6?

I think this should be made i a future version of avisynth. When i read projects to include avisynth in a NLE-Like Programs this would be one first step for. Also your MT-Plugin could get information from there so it can decide which mode should be used with this filter...

qwerpoi

30th May 2007, 15:35

Yes, if I were the end-user. I am of course when I use the app, but as a distributor of a package I would prefer not to clutter the "user-defined" category with ~200 functions (see the relevant avsp macro is in this post (http://forum.doom9.org/showthread.php?p=1004300#post1004300)) and let that category for the end-user, so as to easily distinguish his/her own functions. This could benefit other distributors also.
Okay, I see what you mean. I'll rename the categories and include the new one, but I can't guarantee it'll be in the next release.

Now that AvsP can make calls directly to the AviSynth script environment, isn't it possible to get loaded filters and their arguments directly from AviSynth instead of making a separate database?
You can get the loaded filters and arguments directly from Avisynth, but as tsp pointed out you can't get the additional info necessary for making user sliders. For int or float arguments, you would need the min and max values, as well as default values and step sizes. In order for the automatic slider feature to work properly, communication with Avisynth is still necessary, particularly when trying to accurately determine whether a clip has been automatically passed to any given filter.

I just upgraded to the newest version, and it seems unicode doesn't work now. I could swear it worked in earlier versions though.
I've been trying to nail down all the unicode bugs for the last couple of versions, looks like I may have introduced a new one. Basically issues arise when there are both unicode and non-unicode strings being handled by the program, so the best practice is to make sure all strings are unicode, which is what I've been trying to do these past releases. I just recently discovered that for some reason converting a string to unicode when it is already unicode can cause a crash, which is fairly unbelievable. I've fixed these issues, so what I'll do is release version 1.4.0 in a couple of days. This version will have the automatic sliders, but the option will be disabled by default. That way anyone intersted in helping with the database or giving feedback on the new option can easily do so.

Also, it wont automatically suggest a default filename for the avs if I load the input file via directshowsource. When I use avisource it will suggest a filename.
Yeah, right now the feature is not very intelligent - it activates only if the filename has a source extension as defined in the Extension-based templates. This was done to avoid issues such as using plugin dll names as the suggested name. But as you point out it will often fail with DirectShowSource and unknown extensions, so I improved how the feature works, it'll be in the new release.

I think this should be made i a future version of avisynth. When i read projects to include avisynth in a NLE-Like Programs this would be one first step for. Also your MT-Plugin could get information from there so it can decide which mode should be used with this filter...
When I release the next version, you can check out how I'm storing the information. It's basically a simple documentation string for each filter, which means it's up to the filter developer to make sure the doc string corresponds appropriately with the actual filter arguments. If people think my method is clear enough, then it could be as simple as adding a method named something like GetDocString() to each filter.