IVTC4 plugin for Avisynth

[dsmith]

Did a little bit of testing, and so far it's working exceptionally well. Of about 1000 frames that I've reviewed, only a handful were questionable, and I've only found one that's definitely wrong. Which leads to my (tiny?) request: a way to manually edit the cache information. IE: if frame 1000 is from fields 2500 and 2501, but that's incorrect, allow you to change that to 2501 and 2502, for example. This of course depends on how the cache is designed, so may not be feasible. But for such small changes, I'd really prefer a little manual editing to trying to change the motion parameters (which are going away in the next version anyway) and reevaluating the entire result without knowing if I'm about to screw stuff up.

--
David

[daxab]

@dsmith

This is actually an idea that's been rattling around in the back of my head for awhile. No matter how smart the algorithm gets, it's nice to be able to manually override it if necessary. One scheme I thought of was to write out a .tpr file. Then you could load up the project in TMPGEnc, look at the frame decisions, and adjust them.

Two problems with this: 1. I don't know the .tpr file format. I've dissected a bit of it to write TPRIVTC, but it's a lot easier to read a small section of the file than to write a full, correct file. 2. The .tpr file appears to use something akin to a 60fps selection list. In the current code (not in the released IVTC4 code), I use 30fps source (for efficiency) so the selection gets messier if I have to go back and forth to 60fps selection list. I know it's possible to work around this, but it discourages me from the .tpr idea.

I have some other ideas of how to do this but I just haven't gotten around to this yet. I've been busy trying to get IVTC5 in shape for release. I'm having a bear of a time with my test material, BAV, which is just a mess.

Anyway, thanks for the input, and I'll bump up the priority of cache editing on my todo list.

[Lord Sandwich]

Oops, forgot to check back on this thread. :D

After watching the movie three times, I discovered that both Decimate and IVTC4 produced choppy frames at completely different scenes. So I had to patch them together in order to make an acceptable copy. Decomb became a lot more accurate with 3.7's guidance however, so I used this as the "base."

@neuron2

I'd love to be able to put up clip samples, but my connection here in Asia is painfully slow. :( Uploads of any sort are out of the question until I get back to the States in May.

Anyway, if it's of any help, Decomb tended to make the most mistakes in the Sharkticon and Junkion portions of the TF movie. They start at 58:30 and 1:01:57, respectively.

[Lord Sandwich]

Originally posted by neuron2
Not sure what you mean by this, since Decomb's job is not to "eliminate duplicate frames".

What I meant was that both IVTC4 and Decomb's Decimate(5) function sometimes take out the "wrong" frame, i.e. animation skips or becomes jerky for the entire scene.

Wish I could elaborate further, but I'm still pretty new to this. Lemme see if I can find a way to upload some small samples....

[Guest]

@daxab

How's IVTC5 coming along? Enquiring minds want to know. :)

[daxab]

Well, it's a story I'm sure you're familiar with. I get it working flawlessly with clip #1. Then I try clip #2 and see a few problems. I fix those. Then I try clip #3 and see a few problems. Etc., etc. It's very tricky to strike that perfect balance that works well for a variety of clips. But I'm getting there...I think.

I'm slowing down a little because I'm getting a little burned out. It no longer sort of feels like work -- it completely feels like work. It's like a night shift programming job.

[Roginator]

Well hey, if you need any encouragement, you are doing a great job!

Now get back to work <grin>

[Guest]

@daxab

If you *do* experience a total flameout, bear in mind that you always have the option to release your source code so that others may carry your torch. :)

And you can keep posting your excellent ideas and let the grunts turn them into code for you. :)

[daxab]

@Roginator
Thanks for your kind words. I appreciate it. :)

@neuron2
I still have a little kick left in my legs ;). And as far as "grunts", there's no one on this board that I would apply that label to! I'm always amazed at what high quality work people do even when they aren't getting paid to do it. Maybe it's because they aren't getting paid -- they're doing it only because they want to.