You are right, I had been using this source in avisynth with order=1 without any problems and was fooled by it. Probably TFM had some kind of autocorrection, I don't know. By reinspecting it back again I confirmed it's BFF. I had tested before with BFF on YATTA settings and ignored that needed to do the same on YMC.
So this is nice! finally I get something out of YATTA. Now when I hit preview I see the decimated result (as per decimate settings on the "Settings" dialog).
So in this simple case all I left to do, and I ask, is to load the fh.txt file to TFM in avisynth, like as follows?
It seems to work (same output than that of YATTA) but just to make sure.
Now, assuming there was a section where the calculated field matches turned out wrong (unlikely with a soft-telecined source since the pattern is constant), you could go to set pattern and enter the correct pattern. (You can figure out the pattern by playing with the Switch button in a few cycles to find the matches that work.) Then, you'd seek to the first frame that you want to apply the pattern to (this should usually be the first frame in a cycle) and click Try Pattern. The frames displayed in the window will change to reflect the pattern you're trying, and if everything looks good, seek to the last frame you want it applied to (usually the last frame in a cycle) and click Use Pattern, or else click Try Pattern again to reset to the original matches.
So I don't need to implicitly create a new section for a pattern change, or else the section is automatically created when changing the pattern?
Also is there any built in parity field switch detection? or this is something I need to fix previously in the d2v with for example dgindex?Next, No-IVTC projects:
In the help 4 types of projects are described, in the latest yatta version I think they are reduced to 2 types. Type 0, for the things I want to additionally do; detect blends, detect dups (freezeframing basically), and type 1, for field matching and vfr.
What I normally do in avspmod is, create a trim for the section to inspect and start frameskipping and marking with ctrl+b the related frames (blends for example). With this I get a visual feedback of a pattern until it becomes a loop, then I can check its integrity and write down the pattern.
This is quite easy, with this I can then use selectevery's for custom filtering, the downside is indeed sectioning. This pattern can get off eventually or in scenecuts. And this is hard to correct.
My question is whether YATTA can help me in this process.
There is sectioning which is good, and the Switch button for correcting switchs in patterns, but there's nothing as marking. My intention is not to freezeframe nor decimate.
I thought on the post-process button, but it's disabled on project type 0.
Also there's no place to see the whole pattern so you can later take it as reference for custom filtering on sections (The txt's are just a long framenumbers column). YATTA feels more towards processing through patterns than patterns themselves.
My main goal is to obtain an .avs with selectevery's for each pattern section, where I do the filtering