digitalFAQ.com Forums [Archives]

digitalFAQ.com Forums [Archives] (http://www.digitalfaq.com/archives/)
-   Avisynth Scripting (http://www.digitalfaq.com/archives/avisynth/)
-   -   Avisynth: What scripts are you using? (http://www.digitalfaq.com/archives/avisynth/14507-avisynth-scripts.html)

rainer 04-04-2007 06:12 AM

what scripts are you using?
 
post your latest and greatest scripts for making kdvds/kvcds!

Dialhot 04-04-2007 07:09 AM

Still the same since several monthes :
Code:

DGDecode_Mpeg2Source("PATH\NAME.d2v",cpu=4,idct=7)
ColorMatrix(d2v="PATH\NAME.d2v")

#TDeint(tryweave=true)

LanczosResize(...)

LimitedSharpenFaster()
LRemoveDust_YV12(17,1)

MergeLuma(Blur(0.2))
MergeChroma(Blur(1))

Addborders(...)

In very rare situations, when I need more compressibility I add a motion adaptative part juste before the add border :
Code:

ScriptClip(" nf = YDifferenceToNext()" +chr(13)+ "unfilter( -(fmin(round(nf)*2, 100)), -(fmin(round(nf)*2, 100)) ).TemporalSoften( fmin( round(2/nf), 6), round(1/nf) , round(3/nf) , 1, 1)  ")

digitall.doc 04-08-2007 04:16 PM

Quite similar here, I just don't make use of merge*.

I used to LanczosResize in my scripts before, I now let LimitedSharpenFaster do the job, with dest_x and dest_y.
I think I saw that LSF internally resizes with LanczosResize, and decided to let it do the resizing... is this a bad choice?

Boulder 04-11-2007 02:51 PM

Using LSF as the resizer instead of LSF + a separate resize is the better choice.

By default, LSF does supersampling so it upsizes the image, does its magic, then downsizes back to the original resolution. If you set dest_x and dest_y to your final resolution, it downsizes straight to that resolution so you'll save one extra resizing step.

Phil, you should add mode="rec.601->rec.709" to your ColorMatrix parameters. Otherwise you'll be doing the conversion in the wrong way (you're using HC, right?)

Dialhot 04-12-2007 02:29 AM

Quote:

Originally Posted by Boulder
Phil, you should add mode="rec.601->rec.709" to your ColorMatrix parameters. Otherwise you'll be doing the conversion in the wrong way (you're using HC, right?)

:?: :?:
The d2v parameter of Colormatrix isn't it to adapt automatically the mode to the one used in the DVD ? I even thought that you can't have both d2v and mode parameter.

Boulder 04-12-2007 02:36 AM

The mode parameter is needed too, the d2v file is used to check whether the conversion should be done or not (based on the selected mode). By default mode is rec.709->rec.601 which basically means going from MPEG2 to MPEG4.

By the way, ColorMatrix v2.1 supports multithreading if you haven't updated yet. http://bengal.missouri.edu/~kes25c/

A new lightning-fast deinterlacer, YADIF, is available too. I did a quick test and the results are very good. http://forum.doom9.org/showthread.php?t=124284

Dialhot 04-12-2007 03:07 AM

That's not what is in the doc :
Quote:

mode (default "Rec.709->Rec.601")

mode can be "Rec.601->Rec.709" or "Rec.709->Rec.601", see Description of this filter for examples of when to use this options. Note this option will be overrided when using hints = true or d2v = filename.
May be it's because I don't have the latest version ?
Quote:

Version 1.10. December 27th, 2005
I'm will try to upgrade to see what's the diff.

Boulder 04-12-2007 03:37 AM

Yes, looks like the restriction has been removed. I don't understand why it was there in the first place..the idea of hints/d2v is supposed to be that you can set the mode and the conversion is done if needed, based on the hints or the d2v file. In later versions, it does work like I said.

I don't know how it works in older versions though - does it use the default mode or what...it's also possible that the manual has an error there.

EDIT: the manual needed a slight correction : http://forum.doom9.org/showthread.ph...932#post618932 . Something just told me that I had talked about the issue before :lol:

supermule 04-17-2007 12:34 AM

so finally is the "mode" parameter required or not ???

Boulder 04-17-2007 12:51 AM

If you don't use it, ColorMatrix assumes mode as rec.709->rec.601. This is incorrect if you encode with CCE or HC, I don't remember what the other encoders need. For those two, you must specify mode="rec.601->rec.709"


All times are GMT -5. The time now is 01:35 AM  —  vBulletin © Jelsoft Enterprises Ltd

Site design, images and content © 2002-2024 The Digital FAQ, www.digitalFAQ.com
Forum Software by vBulletin · Copyright © 2024 Jelsoft Enterprises Ltd.