neily
16th September 2003, 00:21
Hi,
As far as I can tell, ApplyRange doesn't work on single frames, it has a minimum of 2. I don't mean to whinge, but I can't see any logical reason why it shouldn't. It seems to be an unneccessary limitation arising from it being based on Animate, where having a minimum of 2 frames makes sense.
I also wonder whether anyone has had the idea of with ApplyRange and Animate, including a Decomb-style ovr file, where single frames and ranges could be specified?
The reason I ask, though it is not really relevent, is that I want to process a number of camcorder captures, where for reasons that can't be completely eradicated, intermittently a field slips by a variable number of lines. I have written an external program that successfully detects the fields and enumerates the errant lines, and can then generate a script to correct the capture, but at the moment I am having to do a DuplicateFrame(F), ApplyRange(F,F+1,...),DeleteFrame(F+1) for each.
As far as I can tell, ApplyRange doesn't work on single frames, it has a minimum of 2. I don't mean to whinge, but I can't see any logical reason why it shouldn't. It seems to be an unneccessary limitation arising from it being based on Animate, where having a minimum of 2 frames makes sense.
I also wonder whether anyone has had the idea of with ApplyRange and Animate, including a Decomb-style ovr file, where single frames and ranges could be specified?
The reason I ask, though it is not really relevent, is that I want to process a number of camcorder captures, where for reasons that can't be completely eradicated, intermittently a field slips by a variable number of lines. I have written an external program that successfully detects the fields and enumerates the errant lines, and can then generate a script to correct the capture, but at the moment I am having to do a DuplicateFrame(F), ApplyRange(F,F+1,...),DeleteFrame(F+1) for each.