+ Reply to Thread
Results 1 to 8 of 8
-
Could be many things. Post a sample of your source. And what software? TFM().TDecimate()?
-
Here is a sample of the source:
sample.m2v
Yes TFM().TDecimate() -
I would blame the horizontal timebase errors from the analog tape step, mainly.
Just add Vinverse to the end of your script IMO. I think the source is too low-detail for it to cause any softening. -
With that video it's just jitter from horizontal time base errors, and MPEG compression artifacts. You can follow up with vInverse() to blur them away.
-
I don't think it's 'deinterlacing artifacts' as it IVTC's perfectly. Sometimes when I have similar problems with tapes I'll use QTGMC followed by SelectEven (or odd, whichever is better as sometimes one field is plainly better than the other) and TDecimate.
Much more problematic, in my opinion, are the blown out whites. But I'm sure you already plan on doing something about them. -
I just tested QTGMC() followed by SelectEven() after IVTC and it seems to give a much cleaner result compared to IVTC() and vInverse().
Well what can you do, when there is no information there is no information.
My plan actually was to render this in tri-toned blue.
But I am open to suggestions.
Last edited by newpball; 12th Nov 2014 at 23:53.
-
The reason I mentioned QTGMC in the first place was because the combination I mentioned will give back a 'pseudo-IVTC' together with cleaning. If all you're using it for is cleaning then you may as well skip the QTGMC and go with a cleaner, ones such as the FFT3DFilter or DFTTest, both of which are used by QTGMC depending on the settings. If you used QTGMC at default then it was DFTTest that cleaned up your video.
Well what can you do, when there is no information there is no information.
Tweak(Bright=-10,Cont=0.9,Coring=False)
Adjust things to your taste. I think tinting is a good idea in which case you might not want to lower the contrast so much. I don't know, up to you.