Quantcast Avisynth: What Scripts are you Using? - digitalFAQ.com Forums [Archives]
  #1  
04-04-2007, 06:12 AM
rainer rainer is offline
Free Member
 
Join Date: Dec 2005
Posts: 45
Thanks: 0
Thanked 0 Times in 0 Posts
post your latest and greatest scripts for making kdvds/kvcds!
Reply With Quote
Someday, 12:01 PM
admin's Avatar
Site Staff / Ad Manager
 
Join Date: Dec 2002
Posts: 42
Thanks: ∞
Thanked 42 Times in 42 Posts
  #2  
04-04-2007, 07:09 AM
Dialhot Dialhot is offline
Free Member
 
Join Date: May 2003
Posts: 10,463
Thanks: 0
Thanked 0 Times in 0 Posts
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)  ")
Reply With Quote
  #3  
04-08-2007, 04:16 PM
digitall.doc digitall.doc is offline
Free Member
 
Join Date: Jul 2003
Location: Valencia (España)
Posts: 741
Thanks: 0
Thanked 0 Times in 0 Posts
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?
Reply With Quote
  #4  
04-11-2007, 02:51 PM
Boulder Boulder is offline
Free Member
 
Join Date: Sep 2002
Location: Lahti, Finland
Posts: 1,652
Thanks: 0
Thanked 0 Times in 0 Posts
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?)
Reply With Quote
  #5  
04-12-2007, 02:29 AM
Dialhot Dialhot is offline
Free Member
 
Join Date: May 2003
Posts: 10,463
Thanks: 0
Thanked 0 Times in 0 Posts
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.
Reply With Quote
  #6  
04-12-2007, 02:36 AM
Boulder Boulder is offline
Free Member
 
Join Date: Sep 2002
Location: Lahti, Finland
Posts: 1,652
Thanks: 0
Thanked 0 Times in 0 Posts
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
Reply With Quote
  #7  
04-12-2007, 03:07 AM
Dialhot Dialhot is offline
Free Member
 
Join Date: May 2003
Posts: 10,463
Thanks: 0
Thanked 0 Times in 0 Posts
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.
Reply With Quote
  #8  
04-12-2007, 03:37 AM
Boulder Boulder is offline
Free Member
 
Join Date: Sep 2002
Location: Lahti, Finland
Posts: 1,652
Thanks: 0
Thanked 0 Times in 0 Posts
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
Reply With Quote
  #9  
04-17-2007, 12:34 AM
supermule supermule is offline
Free Member
 
Join Date: Sep 2005
Location: Donkeyland
Posts: 210
Thanks: 0
Thanked 0 Times in 0 Posts
so finally is the "mode" parameter required or not ???
Reply With Quote
  #10  
04-17-2007, 12:51 AM
Boulder Boulder is offline
Free Member
 
Join Date: Sep 2002
Location: Lahti, Finland
Posts: 1,652
Thanks: 0
Thanked 0 Times in 0 Posts
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"
Reply With Quote
Reply




Similar Threads
Thread Thread Starter Forum Replies Last Post
what are AviSynth Scripts? krustytheklown Avisynth Scripting 11 08-10-2003 08:43 PM
Sizes with scripts for avisynth 2.08 vs avisynth 2.52 ? jorel Avisynth Scripting 24 07-10-2003 09:57 PM
Avisynth: Can Avisynth chain scripts? MrTibs Avisynth Scripting 6 06-19-2003 06:28 PM
Avisynth: My avisynth scripts do not work ! Kane Avisynth Scripting 2 04-16-2003 03:40 AM
Avisynth: Scripts for VRO files? Bud Avisynth Scripting 8 06-04-2002 09:04 AM

Thread Tools



 
All times are GMT -5. The time now is 11:55 PM  —  vBulletin © Jelsoft Enterprises Ltd