NEW Guides and AmvApp BETA

Scintilla · Post by **Scintilla** » Sun Apr 29, 2007 9:44 am

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 d2v 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?

Zarxrax · Post by **Zarxrax** » Sun Apr 29, 2007 12:28 pm

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 d2v 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?

No, it does not. DGIndex actually could fix the illegal field order transitions, but I think it was removed in a recent version. Also the d2v parameter might complicate things a bit, but if there is a big advantage in doing so I guess it would be worth it.
However, I have never understood exactly what advantages there are in using this parameter. Perhaps you could help explain it to me sometime?

jasper-isis · Post by **jasper-isis** » Sun Apr 29, 2007 6:36 pm

I've installed the new beta amvapp now that I'm in between projects. Today, I was trying out the new 2-pass IVTC methods you have on progressive.html, and I noticed this possible typo:

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)

This was for the better post-processing method. AVIsynth couldn't recognize what "deint" was, but the script ran fine when I removed "clip2=deint." Was that the way to go? I followed it up with the input script as you had it, and everything seemed to work fine.

Zarxrax · Post by **Zarxrax** » Sun Apr 29, 2007 6:56 pm

Ok yea, thats a typo. Good catch. Just remove the clip2=deint from the first script.

Warpwind · Post by **Warpwind** » Wed May 02, 2007 1:18 am

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 · Post by **Zarxrax** » Wed May 02, 2007 11:30 am

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.

I would assume the old amvapp would have much the same problems as the new one.

Scintilla · Post by **Scintilla** » Wed May 02, 2007 5:22 pm

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?

From Tritical's TFM documentation:

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. 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.

The default value of the flags parameter includes the hints functionality quoted in bold: "us[ing] the trf flags for field matching in film sections (sections where the trf flags follow the 012301... pattern)" (you can observe these patterns by opening a .D2V file in Emacs).
(However, the default value of flags also provides that "d2v matches are checked for being combed. If a d2v match is detected as combed then tfm uses its own matching routine for that frame." I wouldn't recommend setting flags to something else.)

Krisqo · Post by **Krisqo** » Wed May 09, 2007 3:59 pm

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.

meleechampion · Post by **meleechampion** » Wed May 09, 2007 8:20 pm

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.

Yeah, so where is it now? I liked the new guide, had lots of nifty picture thingies like "here's the source, and here's the source with added awesome" that were too cool.

Scintilla · Post by **Scintilla** » Wed May 09, 2007 8:28 pm

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.

Wait, what? The link in the original post works fine for me.