"Broken Line" problems on FLCL footage

This forum is for questions and discussion of all the aspects of handling and cleaning up your footage with Avisynth.
Locked
User avatar
AngelOfTheDark
Joined: Fri Apr 21, 2006 6:13 pm
Org Profile

"Broken Line" problems on FLCL footage

Post by AngelOfTheDark » Tue Sep 11, 2007 6:49 pm

I'm making a video using FLCL and I need to deinterlace it for what I'm trying to do. After testing each of the codes in ErMacs Guide I found that the smoothest motion and best picture came from using the Avisynth code:

mpeg2source("I:\Videos\FLCL1.d2v",ipp=true,cpu=4)
KernelDeint(order=1, threshold=10)

The only problem is that it leaves the lines around the characters broken on every other frame, giving the footage an ants-crawling-around-the-characters sort of effect. Granted, it is better than any of the others I tried, but I try to be as much of a perfectionist as time and circumstances (ie - my course schedule and budget) will allow. Here's what two neighboring frames look like, to give you an idea about what I'm talking about:

Here's the broken line
Image

And here's the frame adjacent to the frame above:
Image

It doesn't look like much of a problem until you see the footage in motion. I would prefer for all of the frames to look like the latter one. I fed a little footage through my editing program and rendered a sample with the same settings I would use for an AMV to play with it and see if I can fix it post-production, but so far I'm having no luck (plus, any of the filters slow it down so much I can't see what the movement looks like, even when I only use one).

So, what I want to know is either: a) Is there a way to fix this in post-AMV-production, and if so, how? OR b) Has anyone found a better technique (Avisynth code) for deinterlacing FLCL footage so it doesn't do that, and if so, what is it?

Any help I get is greatly appreciated.
"They say that there is no medicine that can cure a fool... I guess that's true." (Potion shop's old woman- LoZ OoT)

User avatar
Scintilla
(for EXTREME)
Joined: Mon Mar 31, 2003 8:47 pm
Status: Quo
Location: New Jersey
Contact:
Org Profile

Post by Scintilla » Tue Sep 11, 2007 7:26 pm

Only times I've ever used FLCL, I've always IVTCed before editing.

I suppose you could try TomsMoComp if you haven't already, or Telecide or TFM without decimation (if that doesn't break up the motion too much)?
ImageImage
:pizza: :pizza: Image :pizza: :pizza:

User avatar
Kariudo
Twilight prince
Joined: Fri Jul 15, 2005 11:08 pm
Status: 1924 bots banned and counting!
Location: Los taquitos unidos
Contact:
Org Profile

Post by Kariudo » Tue Sep 11, 2007 7:27 pm

that looks like the results of a bad resize to me...perhaps you should try using TIsophote() (you'll probably need to download it)
you might want to get TIVTC and try using TFM instead of kerneldeint()
(I assume that you're using NTSC footage and are referring to eadfag v2...not sure if you'll want to use tfm on PAL footage)
Image
Image

User avatar
Scintilla
(for EXTREME)
Joined: Mon Mar 31, 2003 8:47 pm
Status: Quo
Location: New Jersey
Contact:
Org Profile

Post by Scintilla » Tue Sep 11, 2007 7:48 pm

Kariudo wrote:that looks like the results of a bad resize to me...
Usually, jagged lines on edges like that are the result of a bad deinterlace job; in fact, I've seen this referred to before* as the "Deinterlace-when-speed-is-below-100% effect". :P


* Usually by me.
ImageImage
:pizza: :pizza: Image :pizza: :pizza:

User avatar
Kariudo
Twilight prince
Joined: Fri Jul 15, 2005 11:08 pm
Status: 1924 bots banned and counting!
Location: Los taquitos unidos
Contact:
Org Profile

Post by Kariudo » Tue Sep 11, 2007 8:06 pm

bah...I think I picked up the bad resize thing after watching gangstj8's assault and battery.

sure enough...here's where I got that from
Image
Image

User avatar
AngelOfTheDark
Joined: Fri Apr 21, 2006 6:13 pm
Org Profile

Post by AngelOfTheDark » Wed Sep 12, 2007 1:21 am

Hmm, I think I got the field order wrong. (Oops.. that makes me feel stupid) :oops: I could have sworn it was order=1, but the broken line doesn't seem as pronounced in this filter when I change it to order=0 (though it is still there). It wasn't as noticeable in some of the other filters I tried, but I guess I lost track of which adjusts I had tried with which filters. My 4-5 hours of experimenting kinda got mushed together in my mind Guess I'll have to fiddle around with the filters some more, but that'll have to wait until after my calc 3 quiz tomorrow morning (good thing it's my only class tomorrow). For now I need sleep. Thanks for the suggestions. I'll post back here after I've played with it a little more.
"They say that there is no medicine that can cure a fool... I guess that's true." (Potion shop's old woman- LoZ OoT)

Locked

Return to “AviSynth Help”