Quote:
But I can explain the mysterious usage of blockbuster done in the optimal script : that was an idea of girv (I think) to use it to "spray" noise on the already existing blocks that are in the MPEG4 sources in order to have the denoiser that just follow to remove most of them. That is not the same usage of blockbuster we used to have with clean sources (there it is used to avoid creation of new blocks, not to remove existing ones. See the difference ?). I think that the script will be changed quite soon : before my departure I did a lot of test using vaguedenoiser and it seems that other peoples have had the same idea here. The results were very promising. And as 4 new realases of vaguedenoiser were done in the last three weeks, I have to return to my test labs :-)) See ya... |
Welcome "home" :D
Since your vacation I've enjoyed your v3 script with great pleasure. Last year I've bpught a capturecard and converted lots of my videotapes to divx. Burning to DVD was too expensive, while working with (S)VCD wasn't giving me good results. With KVCD and your optimized script I finally can put them on CD and watch them on TV again... Thanks! :D |
I Love this new V3 Script Dialhot it is so sweet and has produced some great results on my DivX conversions thanx 4 that.
Just some newb questions: I notice in all the scripts you have the line: Code:
AviSource("movie.avi",false) 2. Does it affect the predictions if you dont use external audio encoding? Thanx. |
Quote:
Quote:
|
Quote:
TOK uses BeSweet and ive heard from a lot of sources say that headac3he is better for the audio conversion. :) :) |
Quote:
|
I haven't compared besweet and headac3he. I use headac3he and am satisfied with the results. I have used besweet only when working with ToK and was satisfied with the results too:)
|
Quote:
Im not saying that Headac3he is better than BeSweet its just that most ppl seem to reccomend Headac3he for conversions. :) Also another question about the V2 & V3 scripts: Version 2: Code:
AviSource("PATH\NAME.avi",false) Code:
AviSource("movie.avi",false) Quote:
Thanx 4 any help given. |
Hi Zyphon where did you get those versions becuase in the optimal versions script it is Vesion 1 and version 2 and they are different
Version 1 Code:
AviSource("PATH\NAME.avi",false) Code:
Version 2 |
Hi bigggt yeah i know that V1 & V2 are different but in this thread on Page 1 at the beginning Dialhot has posted his V3 script.
Now to me the V3 scripts looks identical to the V2 script and im confused by this and was hoping some one could clear this up for me i know im a newb. :) Thanx. |
OK i get you,i remember a while ago Dialhot had two different scripts in the thread i was talking about but after he made this thread(version3) he switched the one in the other thread to get peopls's opinions in the pole..
So in short the optimal script used to be different until this thread was made Hope that makes sense :wink: |
Quote:
Yes this make perfect sense now thank you very much. :wink: |
DVD Quality XViD and Optimal Script v3
Hey
Thanks for the script, i finnally got it working :D (as i am a total n00b) :?: Ok now here are a few problems im getting. :?: 1/ when i played the avs in Windows Media player it came out Upside down wtf is with this. 2/ and also i was reading this thread and it said that if you had a high quality movie you shouldn't use many filters like ATC etc etc, As my video i have is a DVD Quality XViD should i get rid of a few filters and what ones if i need to... 3/ Theres this green line on the right hand side of the video when i play it. Here is my code.. Code:
AviSource("E:\fahisligad\video1.avi",false) |
2/ You can drop at first Undot, then reduce values of temporalsoften to (2,5,5,3,2) or even (1,5,5,3,2)
1/ and 3/ both problems are related to the codec used on your PC for playing Mpeg. Which is it ? |
@ KungFu
The green Border (no matter where it appears) results from a wrong size calculation in Moviestacker. Be shure to set everythng right. Or use GripFit as included in the optimal script. GripFit includes an automatic detection and calculation routine to avoid problems like in your case. Try this on very clean and good Dvix/Xvid Sources (like 2x700 MB Dvix/Xvid Movies). ############################# AviSource("PATH\NAME.avi",false) BlindPP(cpu=4) GripCrop(528, 576, overscan=1, source_anamorphic=false) GripSize(resizer="LanczosResize") TemporalSoften(1,5,5,3,2) Asharp(1,2) # 1= sharpen factor, 2= threshold for only sharpen edges and no cleaned surfaces #DCTFilter(1,1,1,1,1,1,0.5,0) #Blockbuster(method="noise",detail_min=1,detail_ma x=10,variance=0.5,seed=5623) GripBorders() ############################# You don't need to use the Blockbuster at the beginning if there do not appear any artefcts or blocks in your Dvix source. TemporalSoften just cleans a little the surfaces. And only if needed: DCTFilter performs the DCT routine in combination with the Blockbuster at the end to avoid new Blocks in your encoding. First try to make a test encoding using sampler() at the end of your script WITHOUT DCT & Blockbuster. When there will appear blocks etc. remove the "#"s in front of DCT & Blockbuster an do another test with sampler() included at the end of the script. Then you decide ;-) Only use Asharp if the Value of the predictionned CQ allows this. If the result of the CQ will be to low .. remove the Asharp line. |
1/ an asharp after Lanczos ? That is the first time I see someone no telling me that Lanczos is too sharpy :-)
2/ DCTfilter has nothing (or very little) to do with DCT blocks and you should use it everytime as it lower the file size wihtout any visual effect. |
Your totally right Dialhot, .. I meant the Combination Between them (DCT and Blockb.) = less filesize = more CQ = less blocks
I see the things in the result :) And I testet it on many movies. And still to use Lanczos in the script I posted above is very funny, I agree. Thats because why I write too fast and copied the lines of the script before. In this case KungFu, change the line above GripSize(resizer="LanczosResize") to GripSize(resizer="BicubicResize") Cause Lanczos seems to me that it sharpens to much the wohle picture and I think it doesn't work adaptive, so Temp.Soften with this should work harder on the sharpened Surfaces by Lanczos when used before. Thats why I use bicubicresize and a little a(daptive)sharp after the cleaning. But still I'm not at the end of my Dvix/Xvid testings ... :D |
If i'm using a CQ of 90 with pretty good quality source which filters in general are best left in and the settings?
AviSource("123.avi",false) BlindPP(cpu=4) GripCrop(704, 576, overscan=1, source_anamorphic=false) GripSize(resizer="LanczosResize") #TemporalSoften(1,5,5,3,2) #Asharp(1,2) # 1= sharpen factor, 2= threshold for only sharpen edges and no cleaned surfaces #DCTFilter(1,1,1,1,1,1,0.5,0) #Blockbuster(method="noise",detail_min=1,detail_ma x=10,variance=0.5,seed=5623) GripBorders() |
You can use dctfilter.
|
Site design, images and content © 2002-2024 The Digital FAQ, www.digitalFAQ.com
Forum Software by vBulletin · Copyright © 2024 Jelsoft Enterprises Ltd.