New Visual Editor for AviSynth

[stax76]

wouldn't it be better to bypass the information that is very specific to your application instead of modifying the general descriptions? Your modified descriptions will be outdated very soon and then you have to modify them again and again and....

[FredThompson]

Yeah, that's a good point. If there are general configs and application-specific configs stored as separately, less re-writing and problems. Come to think of it, you'll have a better chance people will want to create the general data if the format is stable and other people start to use it.

[vion11]

To get AVEditor running I had to modify uncorrect entries.
(e.g. I have no version of Blur, which accepts 3 parameter).

I agree my solution is proprietary and I see the problems.
For me the only instance knows about parameter is avisynth itself.

If there is always an actual and reliable definition available,
and xml is the choice, I'll include that and put the picture
attribute elsewhere.

Till then I see 2 solutions:

- avisynth gets capable of rendering out its definitions
- (time needed for coding)

- users keep them accurate
- (web based interface needed)

This Catapult thing is only a start, its an sourceforge project
and the developers may have better solutions ready.
From what I see in the php a webbased interface can't be
like building a cathedral. If anyone is interested in browsing
through the xml-hierarchie, I'll give the basic code as template.

[vion11]

@sh0dan
I'm prepared for split filter now. Look here.
Some PShop filter work as well.

[FredThompson]

Are you working on macro capability as well? Things like this look very interesting: http://forum.doom9.org/showthread.php?s=&threadid=68494

[vion11]

Yes, I like the filter mf has writen a lot and
I use all available brainpower to get them running as template.

[vion11]

To continue the row of updates around AviSynth, here
is an interims release (0.3.0) of AVE Visual Editor.
To keep bandwidth low setup does not contain
the VB Runtimes 6.0 any more.
You may google them for your installed language.

Same with ms xml parser.

AVEditor works best with latest 2.5.4 release of avisynth.
If you need the "show-only-filters-from-installed-plugins"
feature, write "useapi=-1" at the end of ini-file.

Be careful, older version of Avisynth don't like remote
control from VB, strange things may happen.

Workplace accepts now dropped *.aveuf files.
aveuf is an abbreviation for ave userfunction.

An aveuf contains *one* function, with at least one up to three
clip parameter(s). So they should start with "function" and
end with "}"

Example:

# uses Blur(1) to achieve more blurring
Function BlurMore (clip c , int nTimes )
{return ( nTimes == 0 ? c : BlurMore (Blur(c, 1), nTimes - 1))}

Everything writen above "function" becomes the description of function.
The function import is not as clever as HAL. Avoid doublequotes
in parameters and don't start your description with "#function..."

You'll find this as file "BlurMore.aveuf" and "mfToon-v0.52.aveuf"
in folder \testdrop as an exemplification for your own functions .

I've used the mf function for testing, it is hardcore scripting.
Many thanks for inspiration.

AVE analyses dropped files and creates a new file in the
\xml folder, with the function as a loadable filter, available
from startup as userfunction.

If you drop "mfToon-v0.52.aveuf" again, you'll loose working
default parameter values, but may change the picture.

There are other new features more or less hidden. You'll find them.

A hint for new users, install and start, if there are no errors press
spacebar after closing splash screen and look what happens.

There are still problems with some core and plugin functions.
Parameters sometimes optional and sometimes not is a mess.

[Kaiousama]

Vion11: keep up with the good work you're doing, this editor is really revolutionary!

only a question for the moment: are you planning to release AVEeditor sources?

[vion11]

I haven't spend time thinking about future of AVEditor.
In fact I don't know if it's worth while. At the moment
I see no solution to get it bug free, caused by the
unconsistent function interface to AviSynth.

As long there are no rules for developers about designing
functions/filters, it is a daily and manually work to keep
the function description and its parameters layout clean for
at least the current version. Otherwise is it not recommended
to update with every new release for professional reasons.

To use the power of avisynth as a foundation for future
video editing systems with easier use, the function
interface should be maintainance free and generic, so
it could managed by code and not by xml-editors.

In short words, I can't feel the spirit of publishing
sources which don't work, but I'm open to any suggestion.

If somebody is interested in a specific part, I may post it here.

[sh0dan]

I'm sorry to hear that! I had really hoped this project could go somewhere. It is the GUI with the best potential I have seem all my time here.

Making something as groundbreaking as this is bound to give a lot of headaches. I would really like to see a "simple-but-fully-working" implementation - perhaps only with a handful of filters. If your GUI gets accepted and used, it will open the door for many casual users.

[vion11]

Argh - I accidently hit edit instead of quote!!

I'm sorry - I accidently removed half your message

[...] [killed by sh0dan]
For explanation, the quick rec709
thing with ConvertToRGB, has turned 30+ graphs
from running to useless. What can be done to avoid this
sort of changes?

What about ConvertColorSpace(inType, outType, specs)?

[...] [killed by sh0dan]

However, at the moment I'm trying to get avs_invoke running.
Further I'd like to see some screenshots from running graphs,
with more than 10 filter, to get an idea how to implement
a pretty printer or auto-organize filters function.

[vion11]

This was the first implementation for creating proper
parameter strings, its the most vulnerable function.

It should work on all functions, but it doesn't.....

Public Property Get ParamStr() As String

  If IsOptional And Value = "" Then
    ParamStr = ""

  ElseIf Not IsOptional And Value <> "" Then
    If ParamType = "string" Then
      ParamStr = """" & Value & """"
    Else
      ParamStr = Value
    End If

  ElseIf IsOptional And Value <> "" Then
    If ParamType = "string" Then
      ParamStr = ParamName & "=" & """" & Value & """"
    Else
      ParamStr = ParamName & "=" & Value
    End If

  ElseIf Not IsOptional And Value = "" Then
    ParamStr = "Error"

  End If

End Property

[Kaiousama]

Originally posted by vion11
The latest version (0.3.0) counts 56 downloads
and absolutely no feedback except from Kaiousama.

Don't know the reasons, may be to complicated,
setup doesn't works, where are the features,
filter doesn't work, how can I save, whatever.

You can load, change and save graphs, what is missing?

Maybe i can provide you a possible answer (telling my experience)....

I've tested for the first time AVE at my university workstation, all is gone right (the pc was reformatted the day before, so i've worked on a clean windowsXP installation) and i was really amazed by your application.
Now i'm at my home pc and i can't find a way to start AVE properly, the application hangs on inital splash screen, it says all filters were correctly loaded but the splash screen remains still. if i click with mouse nothing happens, if i press "enter" key the application exits.

I tried AVE at my friend's home pc and the result is exactly the same, the program hangs on inital splash screen....

I don't know where is the problem, can you suggest me what can i check, or try to reinstall, in order to start AVE properly?

Maybe other people didn't gave you their reports because they failed to start AVE.

I agree with Shodan that AVE has a great potential, and it can place the basis for implementing graphical properties pages into avisynth filters, in this way each filter will be configurable, without the needing of an updated XML file that lists each filter's parameters.

I asked if you planned to release AVE sources because i'm also coding an application in VisualBasic (a subtitling application), and maybe i can give you a hand with this language

[morsa]

It takes time for people to begin using a new interface.
Most of advanced avisynth users are really confortable with the simple text-no-GUI interface.

[vion11]

This is the complete init sequence, whats your last line?


Starting AVE Version 0.3.0

Checking system...
79 % Memory free.
Windows 2000 detected

Searching INI File...
C:\Development\AVEditor\AVEditor.ini
INI-Version: 0.3

Running in DEBUG Mode!

Initialising objects..

Checking AviSynth...
avisynth.dll: 2.5.5.0
Checking AviSynth Api ...
Response OK

Checking PluginMode...
using registry
13 plugins found

Checking functions...
Using ave - Functions.xml
212 functions(s) found.

Importing descriptions...
Loading English
37 description(s) found

Searching AviSynth documentation...
Using C:\Tools\AviSynth 2.5\docs\

Preparing workplace...
4 forms successful loaded.

Importing userfunctions...
3 userfunction(s) found.

Importing graphs...
2 graph(s) found.

Preparing graphmanager...

Preparing object chooser
... OK

Opening forms

Initialisation finished
0 error(s)

Doubleclick to continue...

[vion11]

Originally posted by Kaiousama
.... and it can place the basis for implementing graphical properties pages into avisynth filters, in this way each filter will be configurable, without the needing of an updated XML file that lists each filter's parameters.

I see no need for coding grapical property pages, as long the
parameters are well defined they can be created on the fly with
sliders, droppers, choosers, radio buttons, edit boxes, drop down
combos.....

[Kaiousama]

When i start AVE i can see the following sentences appear on hanged splash screen:

Editor\AVEditor.ini
INI-Version: 0.3

Initialising objects..

Checking Avisynth...
avisynth.dll: 2.5.5.0
Api disabled.

Checking PluginMode...
using registry
26 plugins found

Checking functions...
Using ave - Functions.xml

And the "212 functions(s) found." you written 2 posts before does not appear as well as all the rest.

Because the last checked thing is xml file i reinstalled m$ xml parser (i have version 4.0 sp2 with SDK on my system) but nothing changed.

[Kaiousama]

I've found the problem!
It was due to my version of M$ XML parser, i had 4.0 sp2, i uninstalled it and installed version 3.0 sp4 and all is solved, AVE now starts properly and i can use your GUI to create avisynth scripts, YATTA!

Maybe it would be useful if AVE during initializations checks even if the proper version of XML parser is installed on user's system

[vion11]

I'll upgrade AVEditor to Version 4 and link to the merge package
for download. THX for lighten up the MS DLL hell.

[Kaiousama]

After my first usage of AVE with on my home pc i have some suggestion for you:

1) I feel the lacking of a classical menu with "open scrpt" and "save script" commands.

2) Can you add a preview window where users can watch the effect of each added filter?

3) Bug report: I have resized the "Functions list" window with the "[s]" button, but i've resized it too much so the "[s]" button is not visible anymore and i can't resize anymore the window nor bringing it to normal size ^_^ can you limit minimal resize to window's title size?

4) When i add a new filter to the graph, how can i remove it? (i tried to select the filter and press "Cancel" key but nothing happens)

5) Can you provide auto-arrangment for on-screen filters (like windows' auto arrangment for icons)?

6) Can you add combobox for selecting enumerated plugin properties? (see the example for detailed explaination)

Assume we want to add "Deen" filter; i drag deen out from filters box and select it.
Now i have to choose the "String name" property, valid values are only "a2d", "a3d", "c3d". I know it because i read the documentation but a newcomer doesn't know it. Having a combobox with this options enumerated would be a great solution.

7) Remaining on "Deen" example, i make the same consideration for the "clip" field, having a combobox with a list of avaible clip's names used in actual script would be a good thing.

8) Remaining on "Deen" example, another interesting feature would be to have a ToolTipText for each parameter's textbox indicating valid ranges for the parameter's value.

9) Many filters have the same icon, so graphically is a little disorienting if you are using more than one filter of each type; can you add also the name on the graphical representation of each filter?

I hope this feedback may help you.

p.s. I have a newbie-coder question: if i have an unknow filter's dll file on my hard disk, can i retrieve the function name and the parameter's number&type in order to call this function? (note i haven'r an header file, only the raw dll)