Trigun

[dreamawake]

Alright, so if anybody has a script to deal with Trigun's major frame blending issues, I could really use it right now. I'll post some caps of examples of what I'm talking about here. Oddly enough, these issues only seem to be present on episode 2 for me. Perhaps that means a particular vob may require different settings in dgindex or something? I'm really at a loss here...






Edit:

Seems like a fucked up rip or something, actually, as these issues are only appearing on 2 vobs and don't seem to be showing up elsewhere on the other dvds.

[EvaFan]

If the vobs are like that then either they were probably ripped wrong. It doesn't make sense that those vobs (episode 2) would be messed up without the problem starting from episode one. Even if the anime company did a mash up job of converting, they would of started the problem from episode 1, not 2 (why create problems after something worked?).

It's probably a bad rip. If you ripped using the file option, try IFO. If problem is still there then try another ripper, if still there then your probably just gonna have to go without em.

I've never worked with trigun though.

[EvaFan]

Guess I should add that it's possible if you were viewing the vobs through an indexed file with avisynth then dgindex detected a field order change that was actually not aspost to change, usually it asks you if you would like to make the change and saves the other version with the extension .bad, try checking that if this happened. This could create nasty blending if it did happen and it could happen anywhere in the source without the rest of the source being effected.

If you were viewing the vobs directly with vdub and they are like that then either its a bad rip or the vobs on the dvd are really messed up...

[mirkosp]

Assuming you are IVTCing and these frames are alone, then it might just mean that tdecimate is fucking up the clean frame detection. You can force it to pick the good frames and/or discard the bad ones by way of ovr files.
ovr files are made like so

Code: Select all

123 +
213 -
312,321 +-+++

the first line tells tdecimate to keep the 123rd frame, the second tells it to drop the 213th frame, the third tells it to keep frame 312, drop 313, then keep 314, 315, and 316, then repeat the same keep/drop pattern for the other frames as indicated (aka dropping the second frame in every 5 frames set).
You save this code in a file named like "blabla.ovr" and then in avisynth you have your tdecimate call as

Code: Select all

tdecimate(ovr="blabla.ovr")

keep them in the same folder of course.
Also, the second image shows some leftover combing, so I'm guessing perhaps you should try to see if you can improve the tfm settings.

[Mister Hatt]

No, that's broken field matching, not decimation. What region is the DVD source and how did you IVTC it?