yup
20th February 2007, 11:46
Hi folk!
I write small script for interlaced source:
AviSource("sel.avi",pixel_type="YUY2")
AssumeTFF()
source=SeparateFields() #
bv1 = source.MVAnalyse(isb = true, truemotion=true, delta = 1, idx = 1, overlap=4, dct=1)
bv2 = source.MVAnalyse(isb = true, truemotion=true, delta = 2, idx = 1, overlap=4, dct=1)
fv1 = source.MVAnalyse(isb = false, truemotion=true, delta = 1, idx = 1, overlap=4, dct=1)
fv2 = source.MVAnalyse(isb = false, truemotion=true, delta = 2, idx = 1, overlap=4, dct=1)
bc1 =source.MVFlow(bv1, idx=1, thSCD1=1000)
bc2 =source.MVFlow(bv2, idx=1, thSCD1=1000)
fc1 = source.MVFlow(fv1, idx=1, thSCD1=1000)
fc2 = source.MVFlow(fv2, idx=1, thSCD1=1000)
interleave(fc2,fc1, source, bc1,bc2)
DeGrainMedian(limitY=9,limitUV=13,mode=1, norow=true)
SelectEvery(5,2)
Weave()
Please advise this script valid? Many script use separately even and odd fields, but if use all fields for same time I can use more data (3 frame equal 5 fields), predicted fields will be close to central fields by time and motion. Only one problem MVTools could estimate motion between fields up and down, but I think MVTools can this things.
yup.
I write small script for interlaced source:
AviSource("sel.avi",pixel_type="YUY2")
AssumeTFF()
source=SeparateFields() #
bv1 = source.MVAnalyse(isb = true, truemotion=true, delta = 1, idx = 1, overlap=4, dct=1)
bv2 = source.MVAnalyse(isb = true, truemotion=true, delta = 2, idx = 1, overlap=4, dct=1)
fv1 = source.MVAnalyse(isb = false, truemotion=true, delta = 1, idx = 1, overlap=4, dct=1)
fv2 = source.MVAnalyse(isb = false, truemotion=true, delta = 2, idx = 1, overlap=4, dct=1)
bc1 =source.MVFlow(bv1, idx=1, thSCD1=1000)
bc2 =source.MVFlow(bv2, idx=1, thSCD1=1000)
fc1 = source.MVFlow(fv1, idx=1, thSCD1=1000)
fc2 = source.MVFlow(fv2, idx=1, thSCD1=1000)
interleave(fc2,fc1, source, bc1,bc2)
DeGrainMedian(limitY=9,limitUV=13,mode=1, norow=true)
SelectEvery(5,2)
Weave()
Please advise this script valid? Many script use separately even and odd fields, but if use all fields for same time I can use more data (3 frame equal 5 fields), predicted fields will be close to central fields by time and motion. Only one problem MVTools could estimate motion between fields up and down, but I think MVTools can this things.
yup.