New Visual Editor for AviSynth

[vion11]

I'd like to get some feedback on this new approach
to script editing. Nearly everything can be adjusted
with mouse. Sourcefilters are accepted from Explorer
by drag'n'drop, etc.

The project is in alpha state, but can generate
(some) working scripts.

There are still problems with many functions I don't
know which parameters are required or can be named.

The function descriptions are placed in a ini-file.
Ideas for better solutions are highly welcome.

If the API is ready, I will include support for plugins,
user functions, *.avs reading and writing and
preview for filters.

I wish a lot of fun, and tell me what you think about!

Current version now: 0.3.3
There is a new guide and download available.

Changes:
- frame preview per filter
- auto organize filters
- experimental AVI Export (video only)
- better INI handling
- updated to msxml 4

Changes May 2004
- slightly updated filter definitions in xml

[Richard Berg]

There is an (ugly but useful) API that enumerates internal and external functions using the string database. VDubMod uses this. Look in avisynth.cpp.

[sh0dan]

This looks a lot like a GUI that would be my next big project if I by some big chance got the time for it. It looks great!

It does however throw a "run-time error '76' - Path not found" when I try to launch it.

Windows XP, SP1.

You should have a look at importing the XML-files found at used for AVSEdit.

[vion11]

Setup is updated.
Some error handling is added and ignore is an option.

I'll try to get some information out of the string database now..

[sh0dan]

Now the GUI shows up, but a similar error '76' is showed right after the GUI is drawn.

[vion11]

Setup is updated (0.1.8)
Error(76) found and fixed.

[sh0dan]

Wow! Looks really great - it almost feels like Shake! My dream come true!

A really great start!

Minor stuff I'd like:

* Link targets should be droppable on the entire clip frame - just connect to the first non-used input connector. The orange dots are hard to hit.

* One output -> multiple inputs. I suspect this would require some kind of sorting/ordering to keep everything in the right order. Also circular graphs are already a problem I can see.

[vion11]

Next targets are:

* local function database
- import or check of available functions depending on current avisynth version
- a gui for maintenance the functions (at least for me)
-> no overwriting of user defined default values on updates
-> enables faultless handling of multiple and optional clip variables (Overlay, BlankClip, etc)
-> automatic use of colorconversion filter

* redesign of Filter UserControl
-> automatic check of parent or child use for target drop
-> visual feedback for child drop if multiple connectors
-> more icons

* use of C API
-> loading and saving
-> "pretty printer" for other scripts
-> autoload last project
-> special Filter for User Functions
-> plugin-support

* keyless parameter input
-> $Color with picker and palette
-> optionlists

* Forgotten something?


I can't identify any API on available functions
except FunctionsExists. More Hints please.

[FredThompson]

Wow! It sure paid to surf through this forum today!

That screenshot is incredible.

There are a number of timeline editors for audio which might, just might, be capable of being folded into this. Let me know when you're ready to look at them and I'll supply the info.

[Richard Berg]

// *******************************************************************
// *** Make Plugin Functions readable for external apps            ***
// *** Tobias Minich, Mar 2003                                     ***
// BEGIN *************************************************************
#if 1 
    if (prescanning) {
    AVSValue fnplugin;
    char *fnpluginnew;
    try {
      fnplugin = env->GetVar("$PluginFunctions$");
      int string_len = strlen(fnplugin.AsString())+strlen(name)+2;
      fnpluginnew = new char[string_len];
      strcpy(fnpluginnew, fnplugin.AsString());
      strcat(fnpluginnew, " ");
      strcat(fnpluginnew, name);
      
      env->SetGlobalVar("$PluginFunctions$", AVSValue(env->SaveString(fnpluginnew, string_len)));
      delete[] fnpluginnew;

    } catch (...) {
      fnpluginnew = new char[strlen(name)+1];
      strcpy(fnpluginnew, name);
      env->SetGlobalVar("$PluginFunctions$", AVSValue(env->SaveString(fnpluginnew, strlen(name)+1)));
      delete[] fnpluginnew;
    }
    char temp[1024] = "$Plugin!";
    strcat(temp, name);
    strcat(temp, "!Param$");
    env->SetGlobalVar(env->SaveString(temp, 8+strlen(name)+7+1), AVSValue(params));
    }
#endif
// END ***************************************************************

I don't have the corresponding VDubMod code handy, but this should give the basic idea.

[vion11]

@FredThompson
Which advantages could users expect from a graph editor
extended with timeline oriented features in the audio domain?

@Richard Berg
THX, is there no way to get information about internal functions?

[FredThompson]

If you have multitrack sound capability with a timeline paradigm you could have environmental sound. There are a number of very good free audio apps and data files. Music, sound effects, voiceover, etc. are all possible. The key is to specify when a track or effect is to be used, for how long, and the parameters.

If you look at the links page I keep on Donald Graft's site you'll see a section for audio. In there are links to Audacity and some cSounds sites.

In some regards, your question is kind of like asking what AviSynth is userful for except these are for audio, not visual.

The casual converter from analog to digital probably wouldn't care about this type of thing but if you're interested in taking AviSynth more in the direction of Adobe Premiere, this is something that fits.

[vion11]

IMHO AviSynth will never replace Premiere in any way.
I can't imagine someone will get money for this job.

AviSynth emerges as a powerful production tool due its
script language when you have to automate the process
of preparing and organising thousands of video files for
DVD-Authoring.

So its place in the production pipeline is between Premiere
and authoring.

Upcoming DVD-Applications like quizzes, iq-tests, catalogues
and last not least interactive movies will be enabled by
intelligent DVD-Publishing applications using AviSynth as
engine. That's the place coder and scripter get paid.

[FredThompson]

I didn't mean AviSynth would replace Premiere. I meant a GUI interface with the ability to "hide" the details of working in the time dimension will be a huge boost. Cinelara is more of a competitor for Premiere. Many times people work on just one source video file. They may need different processing at different times within that one file. AviSynth can do it, certainly, but it is far more complex to do by hand than with some kind of GUI. Regardless, it looks as if what you are developing will be a fantastic way to quickly see the effect of multiple operations.

[FredThompson]

I've thought of a few more operations where a timeline would be helpful:

1) conditional application of overlay. Some sources are a mix of true 4:3 and letterboxed content. Masking the letterbox with a known solid or pattern has advantages.

2) conditional application of logos. This can be used to reduce swim in stationary bugs. The idea is to get a good averaged copy of the bug then overlay it. However, this only works when the bug is stationary.

3) conditional application of forced B&W

4) conditional applicaition of smoothing (more useful during movie credits than during the actual movie, for example.)

See what I mean? There are a number of reasons a visual editor would be a huge benefit with application of filters to only part of a stream. Sure, you could load the stream into VirtualDub and write frame numbers on a piece of paper then hardcode them into the script. A GUI with timeline would be far more useful.

[vion11]

@Sh0dan
After a third and fourth look I found core.xml at sourceforge.
No questions any more on function description, THX.

@FredThompson
You are right: there is a need for timeline editors. I remember
1993 an editor from AiM called videomaker. You could load pictures
and render avis with common effects. It had a timeline and a view
to show different compositing layer. The gui was a shame
but it works under win 3.1 and some videos have been made with it.
Don't know the current version of Premiere 1993.

Now 2004 we have AVID DV as freeware, which needs about
3 XGA-Screens to handle all option and project settings
windows plus output. From the video point of view it's the
best non-linear editing system available compared by price.

But and this is a really big one, the only thing
you can do is linear video. It's the cutter who puts one scene
after the other and when he is ready no one will change anything.

What I'm talking about are interactive movies, the user decides
what seeing next. He is the cutter. He looks his own movie, with
happy end or all dead. So movie meets gaming and DVD is the
plattform.

My requirements are like the follwing:
A bunch of video file and all have to start with a 1 sec fadein,
With avisynth its a ten second job for humans, with timeline
editors it is like marathon with 40 mouse kilometers.

Things are still in development and real interactive Movies are
expensive to produce, let's talk in two or three years again,
where to invest power and energy.

If you interested, you'll find backgrounders and good links
at www.sagas.de (english only)

[FredThompson]

What is your vision for this GUI?

[vion11]

I will give Hollywood the tools to make interactive-movies.

[FredThompson]

Ah, I see, that's a very different use than I imagined. I was thinking visual timeline application of AviSynth. That would also be very helpful but is quite different.

[Richard Berg]

As long as we're fielding timeline-like feature ideas, I think a simple but useful application would be an editor in the literal sense: allow someone to turn a bunch of footage into a scene. You don't need any fancy transitions, and the output can be a human-readable script file. In the grander version of this, you have a bunch of editors each composing scenes into a movie; with Avisynth the only "server" component you need is a CVS for the scripts.