FACAR - As seen on TV!

[r6d2]

Hi there,

I released a new improved version of Gerti's SemiAutoCropAndResize script for DVD2SVCD. Excerpts from the Readme:

FACAR (Fully Automated Crop And Resize) crops and resizes a DVD source to any of 7 typical (X)SVCD resolutions, mantaining exactly the original visual size and eliminating overscan.

Features

<i>. Overscan based cropping
You specify the vertical and horizontal overscan as a percentage. The script then determines the number of blocks to crop in both dimensions. This results in automatic cropping for any resolution you choose.

<ii>. Supports any of the 7 popular output resolutions (As in FitCD).

<iii>. Additional filtering
You may use the PreResize.avs and PostResize.avs scripts to insert any filters you like. The defaults include the KISS recipe, a simple and powerful compression enhancer, and a CCE encoding visualizer.

<iv>. BlockOptimization auto mode
If you set BlockOptimization to 0, a default of 8 is applied to VCD and 4:3 sources, and 16 in all other cases.

<v>. Support for QMF with resizing functions (Batteries included)

<vi>. Overscan overlay with transparency in debug mode
This WYSIWYG feature will show you how much FACAR is actually cropping and may help you decide better the resolution or block optimization you want, should you decide to play with them.

<vii>. Resizer preview modes
This feature will help you decide which resizer to use by showing them on the same frame.

<viii>. "As seen on TV" mode as default (AsoTV)
Gerti's original script handled 704-based frame sizes with vertical shrinking to keep the aspect ratio. Now, 704-based frame sizes have exactly the same height as the original source, so all resolutions work now in "As seen on TV" mode by default.

<ix>. Corrected picture in preview mode (NTSC & PAL)
You'll see the output of the clip with the correct aspect ratio on the screen so you can choose the frame size which works best for you on each particular movie.


Available at:

http://www.geocities.com/r6d2_stuff/ (primary)
http://www.angelfire.com/droid/r6d2/ (secondary)NOT latest version.

Cheers,

[r6d2]

# Change log:
#
# v1.06.7
# - Added corrected aspect ratio in preview mode for PAL (now both NTSC and PAL supported).
# - Fixed OverscanH bug of cropping too much top&bottom on "high" anamorphic movies (DetectedHeight > 448 in NTSC).
# - Changed default values for Overscan to 5%.
#
# v1.06.6
# - Added "real" ASOTV mode and set as default.
# - Fixed aspect ratio on 528x480 frame size, mistaken as 704-based in FitCD.
# - Simplified aspect ratio calculation on 544x480 frame size to make it more general.
# - Added corrected aspect ratio in preview mode (for NTSC only in this version).
# - Reorder parameter entry to most used on top for easier setup.
#
# v1.06.5
# - Added automated AutoCrop values fill in (thanks Tylo)
# - Added resizer preview modes
# - Renumbered and included the 7 resolutions in non-DVD2SVCD mode.
# - Fixed anamorphic source flag bug introduced in 1.06.4 when output was VCD.
#
# v1.06.4
# - Added automated install/uninstall (thanks Tylo)
# - Added visual transparency overlay of overscan area in debug mode
# - Perfectly integrated with D2Sroba (thanks Tylo)
# - Repackaging of third parties utilities (AutoCrop11 now bundled with docs fixed)
# - Fixed: weird things happened if you changed heavily the overscan defaults.
# - Fixed: manual override of BlockOptimization was not being applied.
# - General doc improvements
#
# v1.06.3a
# - Added all needed files on the zip.
# - Added support for QMF
# - Rearranged parameter order for most frequently used first.
# - Fixed: wrong output (just in preview mode) when using non standard res and VCD was selected in DVD2SVCD.
#
# v1.06.2
# - Added BlockOptimization = 0 (auto mode)
# - Added more debug info
# - Fixed: BlocksToCropVertical calculation to reflect anamorphic source
#
# v1.06.1
# - Added support for any output resolution (as in FitCD)
# - Replaced BlocksToCrop parameters by Overscan parameters (adjusts itself now)
# - Added Debug level 3, even more data
# - Fixed: old AviSynth syntax bug (thanks sh0dan)
# - Fixed: Original docs had BlocksToCrop reversed (thanks Holomatrix)

[jorel]

please r6d2, have another link?
:)

<edit>
now is ok,thanks!
:)

[r6d2]

Originally posted by jorel
i try to open the link 3 times today and got:
"page not found".

please r6d2, have another link?
:)
Added a secondary link. According to Yahoo!, the page has been up all the time, though. Maybe it is a DNS problem with your provider.

Edit: jorel, either your DNS is 5 days old or you browser's cache is playing tricks on you. Both links are up.

[jorel]

great,the secondary link is perfect here,open faster.
r6d2, thanks!
:)

@ DDogg
thank you too my friend,i got it!
:)

[tylo]

@r6d2

I've played around with the AutoCrop C++ code, and made a new version of the AutoCrop avisynth plugin. It enables AutoCrop itself to fill in the detected Top and Width for you, making it independent from D2SRoBa. This will make FACAR very much alike RB's AutoFitCD plugin in functionality (only it will not switch to the FACAR template autmatically after preview).

If you're interested, I will make it available to you (incl source code), so you can include it with your FACAR distribution. :)

Six new optional parameters:
- outFile : ini file name to write back cropping information
- outSection : ini section name
- outKeyLeft : ini key name for detected left
- outKeyTop : ini key name for detected top
- outKeyWidth : ini key name for detected width
- outKeyHeight : ini key name for detected height

When the outFile + outSection are specified, AutoCrop will write the output in preview mode(=1) only. I.e. it will no longer be neccesary with the extra call with mode=2. The new AutoCrop version is fully backward compatible with v1.1.

[AVISYNTH_FACAR DetectBorders]
..
2=AutoCrop(mode=1, ..., outFile=!ThisFile.ini, outSection="AVISYNTH_FACAR", outKeyTop="^DetectedTop.", outKeyHeight="^DetectedHeight")
..
!ThisFile.ini=C:\Program Files\DVD2SVCD\AVISYNTH.INI

[r6d2]

Originally posted by tylo
[B]@r6d2

If you're interested, I will make it available to you (incl source code), so you can include it with your FACAR distribution. :)

@Tylo,

Sounds great! I had been playing with AutoCrop 1.1 calls to detect and use the values directly (like GripFit does), but I found that sometimes AutoCrop just doesn't get it right. Human intervention to say "this is it" is still needed or you may find out later that you lost a lot of time. ;)

If you have time, you might try to modify AutoCrop algo to do something like this: instead of using a predefined threshold, scan the lines and compute the maximum M for all of them. Then stop when (M(n)-M(n-1)) > E, where E is the possible error of a black area (determined experimentally). I think this way human intervention can be left aside.

I'd do it myself, but C++ is quite obscure to me. I'm an old timer. :)

Please e-mail me your code (I PMed you my e-mail address).

[r6d2]

New features/fixes:

# v1.06.5
# - Added automated AutoCrop values fill in (thanks Tylo)
# - Added resizer preview modes
# - Renumbered and included the 7 resolutions in non-DVD2SVCD mode.
# - Fixed anamorphic source flag bug introduced in 1.06.4 when output was VCD.

I've found that for Q=constant, resizers increase the demand for bitrate in this order:

Resizer BR
Lanczos 115%
Bicubic(0,0.6) 111%
Bicubic(0,0.5) 110%
Simple 109%
Bicubic(1/3,1/3) 103%
Bilinear 100%

The percentage vary from source to source and Q used, but the relation is the same.

Please give DebugMode=10 and related a try. Maybe you can see the difference in using the various resizers. Me, at least, I am resizer blind and stick to Bilinear when it's about shrinking an image.

Cheers,

[r6d2]

New features/fixes:

# v1.06.6
# - Added "real" ASOTV mode and set as default.
# - Fixed aspect ratio on 528x480 frame size, mistaken as 704-based in FitCD.
# - Simplified aspect ratio calculation on 544x480 frame size to make it more general.
# - Added corrected aspect ratio in preview mode (for NTSC only in this version).
# - Reorder parameter entry to most used on top for easier setup.

Get it at the usual places linked in the first post. See the Readme for more detail on the changes (also excerpted in the first post).

[DDogg]

r6d2, I don't think it gets said enough. You are an absolute jewel of a forum member. The work you have done on improving Gert's semi-auto work with Facar has just made encoding in d2s even more of a pleasure. Facar is so easy, so well thought out, and works so well. That's nearly becoming a trademark of yours :) So, anyway, a very big and sincere thank you for all this work you do for us!

[kru]

Thank you for a great tool!!!

I've been using GripFit for a long while to resize.
What's the differents between FACAR and Gripfit? Isn't GripFit exactly exact as FACAR???

And I'm litle bit qurius about the QFM script?
Should I only remove "#" to use it, and should I use it on every encode? (high/low bitrate)

[DDogg]

The QMF script if more hypothetical than actually useful, but it is good fun to play around with. Perhaps if the motion parameters were lowered it would be more useful.

You certainly should try adding the indicator lines I put in one of these threads to visually show what motion band is being used. It is quite educational.

In practice, the pre and post filters are more practical. I guess what I am saying is if you actually *need* the QMF to achieve a compression target, you would be better off adding another disk for svcd or making more space available on a DVD because that level of compression normally effects video quality adversely. (r6d2 smiles)

[r6d2]

Originally posted by kru
I've been using GripFit for a long while to resize.
What's the differents between FACAR and Gripfit?
GripFit does a good job too! (See my comments to Gerti67 on the subject on the original SemiAuto thread).

FACAR is not as automatic as GripFit because it still requires human intervention to validate autocrop's results. On the other side, GripFit may fail to find correct borders.

They both support any frame size, any resizer. FACAR is more flexible in a way, as it handles parameters in a more automated "default" way. FACAR uses overscan based cropping in a way it is independant of frame size. It also has some experiental features that are visually useful to choose resizers and frame size.

Regarding the "As seen on TV" feature, I'm not sure if they both behave alike. You might try them both and tell us.

/Add: I forgot the most important part: AFAIK, GripFit does not keep the aspect ratio on 704-based resolutions. You might check that too.

[Trahald]

tried out qmf last night.. although i changed the lancos line to simpleresize and the medium and high to bilinear. i tried deen("c3d", 1) for the medium and high for reduction but my test files actually came out bigger. so i went with the defaults. saves a few bits on a 1 cd encode. on my encode tonight where i'll have it set disks=auto, i'll put lanczos and bicubic back in (leave bilinear on the high motion).. for this im not looking to save bits.. just to make the bits i use count more (sharper lanczos frames on slow easy to see frames and bilinear/higher cleaning for high speed frames).. fun stuff

[DDogg]

w00kiee, I would appreciate it if you could let me know if you see any problems caused with the transitions from different resizing filters when you play on a standalone. I think I had a problem with it, but not for sure.

[Trahald]

i watched the movie on my apex today .. looks fine.. no problems to report

[homerjay]

@r6d2 and DDogg - i can remember seeing in another thread a post by jsquare re the qmf function and changes he made to alter the thresholds - i tried his modifications and managed to get a 115 minute film down onto 1cd at a very acceptable quality

was just wondering if this will be implemented

cheers for another excellent tool

hj

[r6d2]

Originally posted by homerjay
was just wondering if this will be implemented
But it is already... The QMF functions provided are a framework, a template. Feel free to customize them.

(Just remember the FACAR installer will overwrite your Pre/Post/QMF scripts, so have them backed up elsewhere.)

[homerjay]

yeah already got that covered - sorry couldnt have explained myself as well as i thought
what i was wondering is if you thought his settings were better in your testing ?

[DDogg]

I think homerjay was speaking of modifying the level of motion detection in QMF. The stock settings don't pick up hi-speed until the action is very intense.

[homerjay]

thats exactly what i was trying to say :o thanks ddogg :rolleyes:

[r6d2]

Originally posted by homerjay
what i was wondering is if you thought his settings were better in your testing ?
Well, I did provide QMF support in FACAR, but as you may be aware of, I'm not much interested in overcompression ;), so I did some testing but not much research.

If the QMF thread (is it alive yet?) agrees on a better function set, I'll be happy to include it as default on the next FACAR version.

[DDogg]

Actually the idea behind QMF is to avoid overcompression by lightly applying the relevant filters to the appropriate level of action. Same would be said for KWAG's MAF. QMF or MAF is not the culprit, the overzealous use of filters in them is. But as a matter of personal practice I quit using either because using your Pre and Post setup is soooo nice with a light filter application like:

PreResize -
undot()
ASharp(1,4)#costs "Q", but I really like the contrast increase
Fluxsmooth(5,5)

[bilinear resizing]

PostResize -
#deen() occasionally. It actually seems to be better post resize
TemporalSoften(3,5,5,10,2) #normally use this

Helps compression greatly without it being noticable to me. If that doesn't work I just increase space/disks.

[r6d2]

Originally posted by DDogg
your Pre and Post setup is soooo nice with a light filter application like [...]:

Kiss 2nd generation :)

I'd like to incorporate "auto IVTC" to FACAR. You know, sometimes DVD2AVI just doesn't get it in spite of the source being force-filmable, because of bad telecining practices.

This forces you to interrupt the D2S process, look at the AVI, find the interlaced frames, change the D2S IVTC setting and resume. Wouldn't it be nice if it was really automatic?

I saw a script once on an italian site which pointed out how it could be implemented but unfortunately I didn't keep the URL.

Does anyone know the whereabouts of something like this?

[DDogg]

I would PM bilu. If anybody ought to know if/how/where it might be him. It may be moot in a month or so anyway. I have a feeling that DG might add something to dvd2avidg. Not for certain, though.

[Trahald]

i have to try that out.. the pre post.. i stopped using the qmf because on an ivtc title it was too much of a speed hit. ive been more inclined to just add disks. (i was/am such a bitrate scrooge) how much of a perfomance hit does the pre/post setup you have cost you ddogg?

[DDogg]

Just depends on the filters. If you use something like I posted above it is not terrible. Seems like it slows me down about 50% over no filters. I haven't been paying attention lately.

Something nice and easy to try is just fluxsmooth(1,1) in Pre and undot() in post (or reverse that). Hardly noticable but helps with compression.

/Later: Yeah, I guessed it just right. The filter setup above dropped me from 2.70 to 1.35 RT

[r6d2]

Originally posted by DDogg
/Later: Yeah, I guessed it just right. The filter setup above dropped me from 2.70 to 1.35 RT [/B]
At first I thought "50% and he doesn't pay attention"? :confused:. Now I see: when being a millionaire, you can afford to give away big tips. :D

[Holomatrix]

Originally posted by r6d2
I'd like to incorporate "auto IVTC" to FACAR.
yes, I agree, that would be a good implemantation :)

Is it possible for FACAR to autochange the FACAR DetectBorders to FACAR in the Frameserver TAB once the border detection and auto fill in is done?

@r6d2 - you might want to fix your sig :) "There is no much you..."

[r6d2]

Originally posted by Holomatrix
Is it possible for FACAR to autochange the FACAR DetectBorders to FACAR in the Frameserver TAB once the border detection and auto fill in is done?
I'd do it if I knew how to. I guess it might be done with Tylo's plugin, but he didn't do it so I think perhaps it's not that easy. You know, moving through a combo box, where the order of items is not defined...

@r6d2 - you might want to fix your sig :) "There is no much you..."
You mean it should say "not"? English is not my native language, so if there's a grammar error please let me know.

[pacohaas]

Originally posted by r6d2
You mean it should say "not"? English is not my native language, so if there's a grammar error please let me know. yup, should be "not"

[Holomatrix]

Yep, maybe in a future release of D2Sroba, no problem.
And yes, should read NOT :)

[bilu]

Guys,

Take a look here:

http://neuron2.net/ipw-web/bulletin/bb/viewtopic.php?t=216

It works better than Decomb IVTC on video parts of hybrid encodings.

But guess what: it doesn't look that nice but it has no stuttering over the film parts too!

I've tried it over FILM and got what I could describe as the best auto-ivtc so far :)

Best regards,
Bilu

[kru]

I have tried to encode some high motions interlaced films. I know it is difficult to get good quality, but here is a script that seems to improve the quality :cool: :

[AVISYNTH_MA Interlaced]
0=nf=0
1=SeparateFields()
2=UnDot()
3=BicubicResize(^TargetWidth-(^Edge*2),^TargetHeight/2,0,0.6)
4=MergeChroma(Blur(1.5))
5=MergeLuma(Blur(0.1)) # use only if the video won't get too blurry!
6=STMedianFilter(4,32,0,0)
7=SwitchThreshold = (Width<=352) ? 4 : (Width<=480) ? 3 : 2
8=even=SelectEven().ScriptClip("nf=YDifferenceToNext()"+chr(13)+"nf>=SwitchThreshold?unfilter(-(fmin(round(nf)*2,100)),-(fmin(round(nf)*2,100))):TemporalSoften(fmin(round(2/nf),6),round(1/nf),round(3/nf),0,2)")
9=odd=SelectOdd().ScriptClip("nf=YDifferenceToNext()"+chr(13)+"nf>=SwitchThreshold?unfilter(-(fmin(round(nf)*2,100)),-(fmin(round(nf)*2,100))):TemporalSoften(fmin(round(2/nf),6),round(1/nf),round(3/nf),0,2)")
10=Interleave(even,odd)
11=Weave()
12=AddBorders(^Edge,^BorderTop,^Edge,^BorderBottom)
13=Limiter()
14=function fmin(int f1, int f2) { return (f1<f2) ? f1 : f2 }
^Edge=16

The only bad thing with the script is that the resizer is very bad.
So, is it possible to use FACAR to resize it?

[r6d2]

Originally posted by kru
The only bad thing with the script is that the resizer is very bad.
So, is it possible to use FACAR to resize it?
Well, it would require some tweaking, since you are separating fields and resizing separately and then interleaving.

Besides, remember FACAR uses the regular resizers from AviSynth... So if Bicubic is bad for this, I don't know if using other resizer will look better to your eyes. You may replace the resizer in your script and check if that improves the output.

[DDogg]

kru, I just glanced at this, but off the top of my head why not try the interlacedresize that is in simpleresize? It only works in yuy2, so to leave it in its present position you would need a:

converttoyuy2(interlaced=true)
interlacedresize(480,480)
#addborders (x,x)
converttoYV12(interlaced=true)

Else you could move the resize down to the end (which might be more proper) of your routine and just do the converttoyuy2()

As an alternative, you might want to evaluate something like this:

(untested)

#Presents as TFF
Import("G:\convert60ito24p.avs")
mpeg2source("D:\interlaced.d2v").DoubleWeave.SelectOdd
jdl_UnfoldFieldsVertical(flip=true)#jdl_util.avsi from Stickboy (http://www.avisynth.org/~stickboy/)
#Whatever filters
jdl_FoldFieldsVertical(flip=true)
Converttoyuy2(interlaced=true).InterlacedResize(x,x)

[tylo]

Is it possible for FACAR to autochange the FACAR DetectBorders to FACAR in the Frameserver TAB once the border detection and auto fill in is done?
I'd do it if I knew how to. I guess it might be done with Tylo's plugin, but he didn't do it so I think perhaps it's not that easy. You know, moving through a combo box, where the order of items is not defined...Well, RB did it in his AutoFitCD.dll plugin, but that's a different story...

However, the upcoming D2SRoBa 3.0 automatically toggles D2S back to the Frameserver tab after the preview window is closed. (This only happens whenever 'FACAR DetectBorders', or any plugin that modifies AVISYNTH.INI was used). Then it should be easy to (remember to) change it back to the 'FACAR' script.

PS: AutoIt3 supports modifying GUI controls in apps (e.g the Avisynth setup ListBox), so it may even be possible to also do the changing back to FACAR from D2SRoBa 3, but I won't look into that now.

[syzygytec]

Just tried this script for the first time.

A couple of points and questions
I have been using AutoFitCD for quite sometime.
Today I encoded the exact same movie as yesterday, today I used FACAR instead of AutofitCD, not other changes.
Today's encode took 1:15 longer, and I see some artifacts that were not present in yesterdays job.
I am wondering if the slow down and artifacts can be attributed to simple resize versus Bicubic resize.
As far as Im concerned with my linited understanding and from what I may have read here all I have done is used a different cropping method and different resize filter correct?

I'd like to know if it's OK to use Bicubic with the FACAR script, exactly how to edit the script for this and someones opinions on it.
There are things I like about both encodes, but overall I like the AutFitCD far better, my main reason for changing was because I came to believe from reading on gerdi's topic that FITCD does not accurately crop.

[r6d2]

Originally posted by syzygytec
As far as Im concerned with my linited understanding and from what I may have read here all I have done is used a different cropping method and different resize filter correct?
As per the information you provided, yes, but these decisions have collateral effects (see below).
I'd like to know if it's OK to use Bicubic with the FACAR script, exactly how to edit the script for this and someones opinions on it.
It's absolutely OK to use the resizer of your choice with FACAR. You just set the ResizeMethod variable to 1-4 and you're set. My personal opinion on a resizer for SVCDs, if you're interested, can be found here (http://www.geocities.com/r6d2_stuff/IdiotsGuide/IdiotsGuide.htm#_Toc53234278). Of course it's just my opinion, and it is an open issue. An interesting discussion on the topic was held on this (http://forum.doom9.org/showthread.php?s=&threadid=63691&highlight=Resizing) thread. There's a blind test also on this (http://forum.doom9.org/showthread.php?s=&postid=390440&highlight=OK+this+is+the+Pepsi+Challenge#post390440) post you might try.
There are things I like about both encodes, but overall I like the AutFitCD far better, my main reason for changing was because I came to believe from reading on gerdi's topic that FITCD does not accurately crop.
FitCD crops correctly. It sometimes gets confused because it iterates, and some border conditions may be misleading. In my experience, these cases are rare though, and loading the source again gets it right. (The old principle of Turn off then back on).

The only case I know where FitCD always fails is in 528x480 output frame size, but otherwise it is a very good resizer tool.

What gerti67 pointed out, and might have had you thinking, is that in DVD2SVCD, 704-based frame sizes (VCD, CVD) are not cropped correctly, and this is true, although I guess noticeable only to the trained eye (a little more than 2% aspect ratio error on NTSC).

FACAR's main purpose is to operate on "As seen on TV" mode, where you get the same cropping the original DVD has when played on a 4:3 TV, and you save the overscan bitrate consumption. FACAR does not zoom out or zoom in.

You can get also get the same result as in FACAR with FitCD by cropping manually, but it turns out to be cumbersome. FACAR completely automates this task.

There are some cases, however, where you might want to zoom out indeed. For instance, typically with some 720x480 anamorphic movies where the standalones crop the DVD source too much (and of course FACAR does the same), giving you almost a 4:3 full screen picture.

On these cases I use FitCD since by setting overscan=3 I get almost the whole film pixel on the viewable area of my 4:3 TV, as if it was encoded with a letterboxed AR.

But which tool to use is a matter of taste. Both crop and resize correctly.
Today's encode took 1:15 longer, and I see some artifacts that were not present in yesterdays job.
I am wondering if the slow down and artifacts can be attributed to simple resize versus Bicubic resize.
Resizers have different impact on detail retention and speed. Also, speed is influenced by the amount of film pixel you encode. If you zoom out in FitCD, you retain more film pixel, but also your encodeable picture is smaller, thus faster to encode.

Also, if you kept the number of media used in both encodes (same output size), a bigger film pixel encode will have less available bitrate, producing more artifacts.

But if you compare two clips resized with FACAR (unzoomed) and FitCD (zoomed), both with the same quantization, you should not notice any quality difference or strange artifacts on either clip.

I hope I did not put more confusion on you ;)

[syzygytec]

Looks like I have so reading and learning to do. The speed in my second encode didn't bother me any the picture size is a bit bigger cropped by FACAR over AutoFit CD which I like as I guess for now I'm going to blame simple resize for what I don't like.

Could someone please show me the changes in this to use bicubic resize .6 like I used in AutofitCD?

[AVISYNTH_FACAR]
0=ResizeTo=^ResizeTo. global ResizeMethod=^ResizeMethod. DebugMode=^DebugMode
1=GammaCorrection=^GammaCorrection. Hue=^Hue. Saturation=^Saturation. Brightness=^Brightness. Contrast=^Contrast
2=DetectedTop=^DetectedTop. DetectedHeight=^DetectedHeight
3=OverscanH=^OverscanH. OverscanV=^OverscanV. BlockOptimization=^BlockOptimization. AsoTV=^AsoTV
4=global Bicubic_b_Value=^b_value. global Bicubic_c_Value=^c_value
5=DestinationWidth=^TargetWidth
6=DestinationHeight=^TargetHeight
7=LoadPlugin(!SimpleResize.dll)
8=# Import(!PreResize.avs)
9=Import(!FACAR.avs)
10=# Import(!PostResize.avs)
^ResizeTo.=0
^ResizeMethod.=1
^DebugMode=0
^GammaCorrection.=1.0
^Hue.=0
^Saturation.=1.0
^Brightness.=0
^Contrast=1.0
^DetectedTop.=0
^DetectedHeight=0
^OverscanH.=0.04
^OverscanV.=0.04
^BlockOptimization.=0
^AsoTV=1
^b_value.=0
^c_value=0.6
!SimpleResize.dll=C:\DVD2SVCD\Avisynth2.5 Plugins\SimpleResize\SimpleResize.dll
!FACAR.avs=C:\DVD2SVCD\Avisynth2.5 Plugins\FACAR\FACAR.avs
!PreResize.avs=C:\DVD2SVCD\Avisynth2.5 Plugins\FACAR\PreResize.avs
!PostResize.avs=C:\DVD2SVCD\Avisynth2.5 Plugins\FACAR\PostResize.avs
Thankyou

[r6d2]

Originally posted by syzygytec
Could someone please show me the changes in this to use bicubic resize .6 like I used in AutofitCD?
The script is already using [0, 0.6] values for Bicubic. And if you want to change them, you don't need to modify the script. Just the variables of your current run in DVD2SVCD.

Please take a look at the FACAR Readme, which includes gerti67's original readme, on how to do that.

[syzygytec]

I have read everything you have suggested and then some others pages offshot from those.

I have read the documentation of the script by gerdi in the FACAR ReadMe.

I think I was incorrect in referring to simple resize before as a resize method. The script uses Bilinear by default, simpleresize is the filter used?
Do all of the four resize methods use simpleresize.dll or is some of it internal avisyth umm routines?

I'm actually really confused now. My main point in starting this discussion was because I thought maybe the resize method was the reason behind not being nearly as happy
with my encode of the same movie using FACAR as I was using AutoFitCD. I want to be as happy with FACAR because I see room in it for easily advancing in the future to more advanced encoding
such as adding some filters.

There is a whole lot I need to learn and understand here about these scripts in general and thier usage before I can feel confident about making any changes.
Besides some of the questions I have asked in this reply, what I have gathered from Gerdi's documentation in the facar readme is the all I need to do is change the resize method to =2
to be using the same resize methed as AutoFitCD? It does not seem right to me as it will still have 7=LoadPlugin(!SimpleResize.dll) in the script, there is nothing like that in the AutoFitCD script.

Im so lost, you said not to be afriad to post questions, I am however because most things here sound like professional debate and discussion as opposed to newbie support.

[r6d2]

Originally posted by syzygytec
Do all of the four resize methods use simpleresize.dll or is some of it internal avisyth umm routines?
No, ResizeMethod defines which resize to use. The call to simpleresize is just a loading of the library, in case you decide to use it. It is not invoked unless you say so in the ResizeMethod variable.
I want to be as happy with FACAR because I see room in it for easily advancing in the future to more advanced encoding
such as adding some filters.
To compare apples to apples, use the same resizer in both tools. FitCD does not support all resizers but if you used some flavor of bicubic, use the same one in FACAR by setting the variables.
Besides some of the questions I have asked in this reply, what I have gathered from Gerdi's documentation in the facar readme is the all I need to do is change the resize method to =2
Yes, that simple. The defaults for Bicubic values are 0, 0.6.
It does not seem right to me as it will still have 7=LoadPlugin(!SimpleResize.dll) in the script, there is nothing like that in the AutoFitCD script.
As explained above, don't worry about this.
Im so lost, you said not to be afriad to post questions, I am however because most things here sound like professional debate and discussion as opposed to newbie support.
Go ahead! This is the basic forum and your questions are welcome indeed. There are no stupid questions, just stupid answers. :)

You are a good student and I have no doubt you'll be a "pro" if you want to.

[DDogg]

syzygytec, I just want to make sure you do understand that all these settings are done in the frameserver tab in the small scrolling window under where is says "FACAR". The first line is:

ResizeTo=3 ResizeMethod=2 Debugmode=0 (these settings are what I was using at the time of writing this post)

I am sure this is obvious to you, but after years of being in this forum I learned never to assume.

[syzygytec]

Yes DDogg I figured that out, I just did a new encode totally different results major actually. I changed to resize method 2 and changed d2sroba to sample 2% down from 5 encode time dropped from 5hr 15min to 3hr 15min. I'm still reviewing and comparing it. If anyone would like offer to review a sample and logs let me know as can up it to my hosting, I've cut a nice 32mb clip.

EDIT

One other difference...today I used RB's progressive template, last encode was with the progressive template as described by DDogg in the roba3 topic, I just now noticed DDogg posted a sticky about this. Im going to have a look and see if its the same as he posted in roba3

[DDogg]

Same except for the reuse VAF part and some expanded wording.

Oh and BTW, I have found 1% sample works about as good as anything. Sure saves time.

[Crackhead]

hey there!

i only have pal-dvds and often they are interlaced. so now i wanted to deinterlace with separate fields from the d2s drop-down menu, but then cce comes up with an error message saying "frame size 776x80 is not supported. frame size up to 720x576 is supported".
so now i got the question if it is possible to deinterlace with your facar-script? and if so, how? :D is it actually recommended to deinterlace?

btw tried also to deinterlace with "reduce vertically by 2", same error message!

here's the avisynthscript-fileLoadPlugin("C:\PROGRA~1\DVD2SVCD\AVISYN~1.5PL\Mpeg2dec\MPEG2D~1.DLL")
mpeg2source("D:\SVCD\DVD2AV~1.D2V")
SeparateFields()
SelectEvery(2,0)
ResizeTo=0 global ResizeMethod=1 DebugMode=0
GammaCorrection=1.0 Hue=0 Saturation=1.0 Brightness=0 Contrast=1.0
DetectedTop=4 DetectedHeight=572
OverscanH=0.04 OverscanV=0.04 BlockOptimization=0 AsoTV=1
global Bicubic_b_Value=0 global Bicubic_c_Value=0.6
DestinationWidth=352
DestinationHeight=216
LoadPlugin("C:\Programme\DVD2SVCD\Avisynth2.5 Plugins\SimpleResize\SimpleResize.dll")
# Import("C:\Programme\DVD2SVCD\Avisynth2.5 Plugins\FACAR\qmf15b1.avs")
# Import("C:\Programme\DVD2SVCD\Avisynth2.5 Plugins\FACAR\QMF_functions.avs")
Import("C:\Programme\DVD2SVCD\Avisynth2.5 Plugins\FACAR\PreResize.avs")
Import("C:\Programme\DVD2SVCD\Avisynth2.5 Plugins\FACAR\FACAR.avs")
Import("C:\Programme\DVD2SVCD\Avisynth2.5 Plugins\FACAR\PostResize.avs")
Import("D:\SVCD\ResampleAudio.avs")
ResampleAudio(44100)
ConvertToYUY2()this encode should be with vcd resolution, but also tried it with svcd-resolution!

//add: tried separating fields in preresize.avs, again same error!

[syzygytec]

I had that same error in fact every time I recovered it was a bit different....trying to remember. I'm trying to help, something got messed up, I did one or all of these 3 things, started over with fresh dvd2svcd.in & SVCD.ini & avisynth.ini (I save oringinal backups of them.(Then reinstall all plugin's ie: Roba Facar, Delete the CCE registry keys, and uninstall-reinstall avisynth.
I'm sure doing all of that will fix it because it did here!

[r6d2]

Originally posted by Crackhead
so now i got the question if it is possible to deinterlace with your facar-script? and if so, how? :D is it actually recommended to deinterlace?
I've never tried since my DVDs are all NTSC. All the PAL sources I have are progressive.

But try this:

Put SeparateFields() in preresize.avs and Weave() in postresize.avs.

This is not exactly a deinterlacing method, but should resize properly interlaced sources.

Please post your results.

[Crackhead]

Originally posted by r6d2
Put SeparateFields() in preresize.avs and Weave() in postresize.avs.

This doesn't work either, same error message.
when I play the avisynthscript with zoomplayer, it says:
you cannot use crop to enlarge or 'shift' a clip:
(C:\Programme\DVD2SVCD\Avisynth2.5 Plugins\FACAR\FACAR.avs, line 196)
(D:\SVCD\AviSynth_Script_file.avs, line 14)

:mad: i have no idea what could solve this prob...:angry: