------------------------------- "The koalas are so hungry they are eating pine needles," "What will tourists think of a habitat of denuded trees with desperate, starving koalas roaming the damaged landscape?"
RE: Help with Convolution3D usage (interlaced video)
The (Un)ViewFields script may be simpler, but as scharfis_brain pointed out, you should not use it in conjunction with spatial filtering (having an impact in the vertical direction). bb
------------------------------- Kenny... "...and despite your rather demented sense of humor, poor board manners, and general attitude, you drive well."
RE: Help with Convolution3D usage (interlaced video)
As mentioned, just use my . They're designed to be used with spatial-temporal smoothers. The primary disadvantage of the SeparateFields() method is that Dust doesn't like to be called twice. By the way, what's the deal with the DoubleWeave().SelectOdd() stuff? Shouldn't Interleave(...).AssumeFieldBased().Weave() be sufficient? Edit: Oh, that reminds me. Another complication with the SeparateFields() method is that you'll need to keep track of the field-order. There really needs to be an AssumeTFF()/AssumeBFF() call before Weave(). FWIW, my Unfold/FoldFieldsVertical functions take care of all that for you.
RE: Help with Convolution3D usage (interlaced video)
Let me ask a direct question. I basically use one noise filter combo, Undot().Deen() on my progressive source when needed because it is simple and effective and I don't have to think about it much. My limited understanding of Stickboy's [un]UnfoldFieldsVertical is that it takes care of all the stuff I don't want to think about the few time a month I do interlaced. Assuming top field first, when dealing with 60i from a DVD source like an interlaced trailer, is this a correct usage?: jdl_UnfoldFieldsVertical(flip=true) Undot().Deen() # resize here also if vertical resize? jdl_FoldFieldsVertical(flip=true) What I am looking for is the simplest way to take the commands from my progressive source scripts and move them over to the interlaced scripts with the least amount of effort. I suspect there may be a lot of other folks that would like a simple recipe also. Frankly, interlaced is just a PITA and good enough is good enough for a cheesy trailer.
RE: Help with Convolution3D usage (interlaced video)
John, you are correct, you don't need the "DoubleWeave.SelectEven()". Now if you take a deep breath and dig into what these weave and select commands do, you'll find out that nobody needs this command, because it is a NOP, i.e. it does nothing except eating processing time. bb