Log in

View Full Version : Newbie help with AVISynth-Several questions


chipzoller
13th July 2005, 23:38
So after years of encoding my videos to DivX through GordianKnot, I thought since there is no version that currently works with DivX 6 (yes, I'm aware AutoGK does), I thought it a good time to find out what goes on behind the scenes and perhaps learn to script. I am aware of all the resources both here and at the AviSynth homepage, but I just wanted to ask some general questions I'm sure can be fielded by anyone with a working knowledge of AviSynth.

1.) I was noticing what a script looked like after being generated with modest options from GK and found there really isn't much to it. Keep in mind I don't really do a whole lot of encoding from dirty sources including VHS and TV, I mostly stick to good-quality DVDs from my collection. Most things that were involved in the script were the loading of the source (mpeg2source), crop values, and UnDot. So I'm wondering if any of these more complex commands and variables are only used when a lot of cleaning has to be done to the source.

2.) Since GK is setting the crop values, how would I know which values to input if I don't have a GUI to set them? Do most people have a GUI generate a script for the crop values?

3.) How much control is given to AviSynth and how much to (YourCompressorOfChoice)? For instance, cropping (as you all well know) is available in the DivX codec, yet most people crop before encoding. Also, because of the distrobution of control, should the codec only be used to set bitrate, pass modes, and advanced encoding effects? I would just like to hear some commentary on this, please.

4.) Is there some completely filled-out script that basically has ALL the options availble, just deactivated to see what a max. amount of command it can contain? I am aware of the filters and commands sections of the webpage.

5.) I often have to use subtitles in my encodes, and sometimes they have been set in the script and sometimes through VDub. If I use both the bitmap subs in VobSub format as well as occassional text subs, what's the best way to go?

I have been avoiding scripting directly through AviSynth because of the amount of things you have to know, as well as the amount of time it occupies to generate a working script tailored to your needs. Thanks for any answers you may have!


Chip

lamer_de
14th July 2005, 08:54
1) yes. If your source doesn't need filtering, there's no need to use many filters.

2) I do use a gui as well, but there are scripts and/or filters who can aid you, like autocrop etc. Or simply trial and error ;)

3) No filtering control to the codec for me. I don't use DivX, so I don't know what things it can do. Usually you do everything beforehand and use the codec only to do what it's meant for, de/encode. Some people like to utilise ffdshow filters during playback though (like adding noise on-the-fly).

4) No. I don't see the sense in it. I know of people who created scripts with several thousands of freezeframe() commands, so I guess avisynth can cope with a "sufficient" amount of commands.

5) avisynth. This way you can use "fast recompress" in vdub and avoid unnecessary colourspace conversions.

CU,
lamer_de

chipzoller
14th July 2005, 12:55
Thanks for your reply. What GUI do you use? AVIScript? DVX?

Wilbert
14th July 2005, 13:09
2.) Since GK is setting the crop values, how would I know which values to input if I don't have a GUI to set them? Do most people have a GUI generate a script for the crop values?
Use FitCD, or just calculate it by hand:

http://shh.sysh.de/

5.) I often have to use subtitles in my encodes, and sometimes they have been set in the script and sometimes through VDub. If I use both the bitmap subs in VobSub format as well as occassional text subs, what's the best way to go?
See response of lamer_de, but personally i prefer to use external subs. You can even mux it (.srt) in your video with AviMux.

Thanks for your reply. What GUI do you use? AVIScript? DVX?

I personally don't use a gui, but AVSEdit is a free one.

manono
14th July 2005, 15:28
Hi-

1. Yes, that basic GKnot script is so unwieldy that it's hard to figure out what's being done. Once you remove all the lines beginning with "#", you're often only left with 3 or 4 lines that actually do anything. I have about half a dozen "template" scripts that I use, depending on the source, and still use GKnot to get the crop, resize and the bitrate.

I thought that lamer_de answered the questions well.