|
|
| rjisinspired |
| Posted: Jul 2 2010, 11:31 PM |
 |
|
Advanced Member
Group: Members
Posts: 1256
Member No.: 20008
Joined: 12-October 06
|
I had always deinterlaced then removed noise. maybe I should try this in reverse?
I noticed on a videohelp page on a different way of noise cleaning that shows to separate the fields first, denoise, then recombine the fields back. This relates to using Convolution3D from avisynth
Example:
LoadPlugin("Convolution3d.dll")
avisource("D:\CAPTURE\capture.avi")
crop(8,4,-8,-4)
SeparateFields()
odd=SelectOdd.Convolution3D (0, 6, 10, 6, 8, 2.8, 0)
evn=SelectEven.Convolution3D (0, 6, 10, 6, 8, 2.8, 0)
Interleave(evn,odd)
Weave()
DoubleWeave.SelectOdd()
AddBorders(8,4,8,4)
LanczosResize(352,480)
ConvertToRGB(interlaced=true)
Does a deinterlacer work better after doing this step? |
|
| stephanV |
| Posted: Jul 3 2010, 05:29 AM |
|
|
Spam killer ;)
Group: Moderators
Posts: 4348
Member No.: 8917
Joined: 18-February 04
|
A motion-detection based deinterlacer might work better because it will less often confuse noise with motion, but unless your source is really noisy I don't think it matters much.
--------------------
useful links:
VirtualDub, Input plugins and filters, AviSynth, AVI-Mux GUI, AC3ACM by fcchandler, VirtualDub FAQ |
|
|
