Avisynth reverse scripting possible?

[telemachus]

Hello all,

I am completely new to this and am daunted by the difficulty of writing a script... excuse me if I am not understanding a basic premise of this process.

I was wondering if it would be possible to open Virtualdub and to save all the filter, format, codec choices you want via vitualdub's script saving ability, and then use that script as the basis for your Avisynth script.

This way, people who dont want to deal with scripting manually can create Avisynth scripts via Virtualdub's UI. Would that work?

Mark.

[Mug Funky]

virtualdub's scripts save a little more than video filters - avisynth wouldn't know what to do with codec settings.

but to be honest, simple linear processing like what's done in virtualdub can be done in avisynth just as quickly - just practise a little :)

[esby]

The idea in itself is not bad, as it can link vdub settings to an avs script used...
But that would not be 'reverse scripting', but rather some Sylia & Avisynth syntax merge.
Which is not really possible actually, unless you suppose some trick in the syntax...

One possibility would be to allow some special avs comments that could be interpreted by virtualdub...

something like that:

#*#insert sylia scripting <-- would be interpreted by vdub
#normal comment <-- would be ignored by vdub & avs
src = avisource # normal avisynth line <-- would be ignored by vdub but interpreted by avs

And that would suppose to have vdub open the avs as an avi and as a textfile for sylia based interpretation.

esby

[telemachus]

thanks guys
mark

[Zarxrax]

There are a number of graphical interfaces for Avisynth out there. Try some of them maybe?

[telemachus]

Hi there,

Thanks, but initially i thought Avisynth might be able to help me export de-interlaced video from my NLE but it seems it can only work by filtering IMPORTED video clips... which does not help me, I capture in real time with time code via Targa 3000 card... (long explanation on Xvid thread!) but in short i dont think Avisynth can do what I would like it to, ie to "see" my timeline when I export the media - do it's thing on my already edited timeline.

thanks again,

Mark

[ShawnFumo]

Originally posted by telemachus
Thanks, but initially i thought Avisynth might be able to help me export de-interlaced video from my NLE but it seems it can only work by filtering IMPORTED video clips... which does not help me, I capture in real time with time code via Targa 3000 card... (long explanation on Xvid thread!) but in short i dont think Avisynth can do what I would like it to, ie to "see" my timeline when I export the media - do it's thing on my already edited timeline.


Well, Avisynth is a frameserver, but many NLEs can do that as well. If they don't support it natively, I think there are plugins out there (like for Premiere) that let them frameserve. In that case, they save a fake avi that can be read by other programs. I'm pretty sure you could import THAT file into avisynth to de-interlace and serve up to a compressor.

However, if your final destination is progressive video, you should probably de-interlace BEFORE you edit. If you have special effects and they are progressive, it could interfere with later de-interlacing (like putting a blur filter on). If all effects are interlaced then they won't have as much resolution as they could have (like overlayed titles will have half the vertical resolution).

In that case, you may want to make avisynth files for each of your source video clips (there are batch tools out there) and then replace the original clips with those for the final render (most NLEs have options for replacing clips for purposes of things like editing at lower res). Might need a plugin for the NLE to open avisynth files but I believe there are ones out there for all the major NLEs. Also, if the project needed different settings for interlaced versus non-int, you could probably start with avs files with fast de-interlacing and then replace with slower for the final render.

But I'm still new at this also, so anyone feel free to correct this. :)

Shawn