AVISynth Script from FitCD Question

[Maikeru-sama]

Hello forum, I have a simple question about AVISynth Scripts from FitCD. I want to automate the task of making .avs files with FitCD for my movies. By automate, I want to use the same AVISynth script for a group of movies/series. I have a question about one of the values in the AVISynth Script, which is the #Trim value:

[SAMPLE]

# -= AviSynth v2.0.8.0 script by FitCD v1.2.8 =-
AVISource("C:\mymovie.avi")
LanczosResize(656,448,0,0,576,432)
AddBorders(32,16,32,16)
#Trim(0,28578).FadeOut(150)
ConvertToRGB24() # For TMPGEnc or VFAPI

[/SAMPLE]

I have noticed that say for a group of similar movies/series, that the #Trim value in the AVISynth Scripts changes a little. For instance, the above script, it has a value of (0,28578) and in another similar movie/video it would be (0,28507). How big of a deal would it be if I used the same #Trim value for my groups of movies/series? I would just use the #Trim value of the first movie/series of that group and use it for all the others.

Note:What I mean by similar movies/series is that they were encoded into whatever format the same way and have similar width/height dimensions.

I will hang up and listen

[Mr_Odwin]

At the moment Trim does nothing as it is commented out by the #, but if not commented out it's not connected with resize - it trims the length of the video. So, using the same values for every file would be a terrible idea.

[Maikeru-sama]

At the moment Trim does nothing as it is commented out by the #, but if not commented out it's not connected with resize - it trims the length of the video. So, using the same values for every file would be a terrible idea.

Thanks for the reply.

Let me ask a you 2 more questions.

1. So # sign denotes code/values that are commmented out?

2. In FitCD GUI, where do you specify whether #Trim is commented out, or does FitCD, internally decide?

Thanks

[guns1inger]

From what I can remember of the last few versions, the trim statement had always been commented out. As it is set to the length of the clip, it would do nothing anyway. It also has a fade out, which would fade to black over the last 150 frames, if you remove the comment symbol. I suspect is a hang over from earlier days.

You can edit the script in FitCD before you save it, so you can either uncomment the line, or even delete it if you want. I usually change the resize method from Lanczos to Lanczos4 before saving.

[Alex_ander]

Trim is for selecting encoded range of the source video (0 is the first frame, 28578 is the last one), '#' symbol disables any line in the script (also used for comments). If you want to use trim/fade functions you have to enter your own numbers, then edit out '#'. Default fade out number here is a bit long (6 seconds for PAL). So treat it as a template.

[Maikeru-sama]

Thanks for the help everyone.

So based on all the informative information, I really don't need to worry about Trim, as it is always commented out.

I think I will go ahead and automate this process and always have the Trim value commented out.

Thanks

- Mike G.

[manono]

I think I will go ahead and automate this process and always have the Trim value commented out.

Or just remove it entirely from your template script, as it's never used. In fact, you can streamline your script like this (assuming the source AVIs all have the same 576x432 resolution):

AVISource("C:\mymovie.avi")
LanczosResize(656,448)
AddBorders(32,16,32,16)
ConvertToRGB24()

[Maikeru-sama]

I think I will go ahead and automate this process and always have the Trim value commented out.

Or just remove it entirely from your template script, as it's never used. In fact, you can streamline your script like this (assuming the source AVIs all have the same 576x432 resolution):

AVISource("C:\mymovie.avi")
LanczosResize(656,448)
AddBorders(32,16,32,16)
ConvertToRGB24()

Taking this code from the sample I provided:

LanczosResize(656,448,0,0,576,432)

Based on your response, it would seem I can omit the last 4 numeric values. What does the 0,0,576,432 do? I would be a little nervous omitting that, so that is why I am asking you.

Thanks

[manono]

They are the crop values, but since no cropping is being done, they can be safely removed. That will also gain you a very slight encoding speedup. I'd also check out the script in Vdub(Mod), if I were you, so you can see what it looks like, and to make sure you really want the additional black around the edges of the video. Maybe you do, if you have burned in subtitles, some of which might be lost in your TV set's overscan. Maybe you don't.

[Maikeru-sama]

They are the crop values, but since no cropping is being done, they can be safely removed. That will also gain you a very slight encoding speedup. I'd also check out the script in Vdub(Mod), if I were you, so you can see what it looks like, and to make sure you really want the additional black around the edges of the video. Maybe you do, if you have burned in subtitles, some of which might be lost in your TV set's overscan. Maybe you don't.

Yes, that is the reason why I use FitCD, because I want that border around my videos to prevent overscan.

Thanks for your help, I will proceed as directed.