blaku92 wrote:what happened to the beta stuff? version 3? I was starting to get used to it.

LimitedSharpenFaster: LimitedSharpenFaster is a great sharpening filter, but unfortunately it will hurt the compressibility of your video. Regardless, you may want to use it, because it can look very good. The main setting is the strength parameter. The default strength value is 100. If you want to increase the strength of the sharpening effect, you would do it like this:
LimitedSharpenFaster(stength=200)
Zarxrax wrote:I have decided that as of right now, AMVApp will not support Windows Vista. When Microsoft releases a service pack for it, I will take another look and see what I can do to get it fully supported. I guess I might add a page in the guide listing all the problems that exist with vista, and just let people run it at their own discretion.
I would like to solve the problem with Zarx264gui in 64-bit OS's though, if I can figure out what the problem is.
Scintilla wrote:I don't know if I've said this before, but:
Does the new version of the A/V tech guide say anything about the <b>d2v</b> parameter of TFM, how it takes additional hints straight from the D2V file and can correct D2Vs with illegal field order transitions? And if not, why not?
MPEG2Source ("C:\yourfolder\blah.d2v")
TFM(cthresh=4, slow=2, clip2=deint, output="C:\yourfolder\something.tfm")
TDecimate(mode=1, output="C:\yourfolder\something.dec")
Crop(0,0,4,2)
Warpwind wrote:Just a quick question what is currently more stable in vista the old amvapp or the new and improved amvapp3beta?
I just got myself a new laptop with vista loaded and I've yet to begin installing much on it yet.
Zarxrax wrote:However, I have never understood exactly what advantages there are in using this parameter. Perhaps you could help explain it to me sometime?
This option is intended to be used if you are using an mpeg2source() with a d2v file.
It sets the name and path to a d2v file, which TFM will analyze to see if there are any
illegal field order changes and optionally set the order parameter using the field
order of the d2v file. If the d2v file is found to have illegal field order transitions,
TFM will create a fixed d2v file with the string "-FIXED" attached to the end of the file
name. The new file will be located in the same directory as the original. You can then
use this fixed d2v file for processing. If the order parameter is set to "-1" then TFM
will detect the field order from the d2v file and set the order parameter to match. <B>Depending
on the value of the "flags" parameter, TFM will also use the d2v info for field matching
and will pass info from the d2v on to tdecimate to help aid duplicate detection and hybrid
detection.</b>
Krisqo wrote:Just to make this known, the links to the the new guide and AMV App all direct to the old ones even though the link says it's now the official guide.

Krisqo wrote:Just to make this known, the links to the the new guide and AMV App all direct to the old ones even though the link says it's now the official guide.
Users browsing this forum: No registered users and 3 guests