View Full Version : Removing jagged from capture
Aktan
8th March 2010, 02:02
I have game footage captured directly from the console. It was captured using composite. I have tried the following script to deinterlace it, which does the deinterlace well, but the finally output have a lot of jagged lines.
AVISource("pure_.avi")
tdeint(order=1, mode=1, edeint=nnedi2(field=3, qual=3), slow=2, tryweave=false, AP=0, APType=2)
Here is an example of the jagged lines:
http://img514.imageshack.us/img514/6854/78385503.png
Note the jagged lines is not due to it being the first frame. Its there all the time. Here is an example of the clip with the script above:
Deinterlace clip (http://www.zexsoft.com/aktan/?TestCapture/pureFinalS)
Is there any way to remove this?
Thanks.
Source clip (not deinterlaced) (http://www.mediafire.com/?jtmmuqqzt3j)
MadRat
8th March 2010, 03:39
This is what I normally use for anti-aliasing but that might not be your problem, you might have a deinterlacing issue.
w = width
h = height
nnedi2_rpow2(opt=2,rfactor=2,cshift="spline64resize").TurnLeft().NNEDI2().TurnRight().NNEDI2().spline64resize(w,h)
Aktan
8th March 2010, 07:00
I don't think it's a deinterlace issue.
I'll try your script :thanks:.
Aktan
8th March 2010, 14:36
Just using this script:
AVISource("pure_.avi")
nnedi2_rpow2(opt=2,rfactor=2,cshift="spline64resize")
Causes an exception in Avisynth. Here is the cut off error VDub shows:
Error reading source frame 0: Avisynth read error: CAVIStreamSynth: System exception - Access Violation at 0x1a84129, reading f
Even this script does the same thing:
AVISource("pure_.avi")
nnedi2_rpow2(rfactor=2)
Any ideas on the cause?
Lyris
8th March 2010, 14:39
Looks like poor deinterlacing earlier on. All of the dot crawl resulting from Composite connection from the GameCube (or Wii?) will not have made the deinterlacer's motion detection very easy.
It looks like a PAL console as well which doesn't help from the point of view of dot crawl removal...
Aktan
8th March 2010, 15:24
Looks like poor deinterlacing earlier on. All of the dot crawl resulting from Composite connection from the GameCube (or Wii?) will not have made the deinterlacer's motion detection very easy.
It looks like a PAL console as well which doesn't help from the point of view of dot crawl removal...
Wow, how did you know it was a PAL console? The console is a GameCube, and yes I have noticed the dot crawl from Composite. Is there anything that can be done?
Aktan
9th March 2010, 01:36
I tried to use the following script:
AVISource("pure_.avi")
tdeint(order=1, mode=1, edeint=AssumeTFF().SeparateFields().EEDI2(field=3, mthresh=0, lthresh=0, vthresh=0, maxd=29), slow=2, tryweave=false, AP=0, APType=2)
It help fix some of the lines, but the major ones were still there.
scharfis_brain
9th March 2010, 07:28
provide an UNPROCESSED Sample.
your image looks like deinterlaced and then incorrectly re-interlaced...
Aktan
9th March 2010, 16:24
That was the unprocessed sample. Directly from the capture device in graphedit (video compressed of course). Not sure who set it, but the flag of which field first is incorrect. It is suppose to be top field first, so AssumeTFF() may be needed.
Aktan
9th March 2010, 19:34
On second read, you seem to have based your statement off the image. The image is deinterlaced, with the script I posted, but the SOURCE is not.
vBulletin® v3.8.11, Copyright ©2000-2025, vBulletin Solutions Inc.