VideoHelp Forum




+ Reply to Thread
Results 1 to 8 of 8
  1. Banned
    Join Date
    Oct 2014
    Location
    Northern California
    Search PM
    I am working on an old film source which is encoded with a 2:3 pulldown and put on an NTSC DVD.

    Applying an inverse telecine still gives me artifacts that look like interlacing artifacts:

    What causes that? A bad scan, compression artifacts?

    Click image for larger version

Name:	Compare.png
Views:	1686
Size:	63.5 KB
ID:	28494
    Quote Quote  
  2. Could be many things. Post a sample of your source. And what software? TFM().TDecimate()?
    Quote Quote  
  3. Banned
    Join Date
    Oct 2014
    Location
    Northern California
    Search PM
    Here is a sample of the source:

    sample.m2v

    Yes TFM().TDecimate()
    Quote Quote  
  4. Formerly 'vaporeon800' Brad's Avatar
    Join Date
    Apr 2001
    Location
    Vancouver, Canada
    Search PM
    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.
    Quote Quote  
  5. 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.
    Quote Quote  
  6. 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.
    Quote Quote  
  7. Banned
    Join Date
    Oct 2014
    Location
    Northern California
    Search PM
    Originally Posted by manono View Post
    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.
    I just tested QTGMC() followed by SelectEven() after IVTC and it seems to give a much cleaner result compared to IVTC() and vInverse().

    Originally Posted by manono View Post
    Much more problematic, in my opinion, are the blown out whites. But I'm sure you already plan on doing something about them.
    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.
    Quote Quote  
  8. Originally Posted by newpball View Post
    I just tested QTGMC() followed by SelectEven() after IVTC and it seems to give a much cleaner result compared to IVTC() and vInverse().
    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.
    The information isn't missing because the whites are blown out. They aren't so bad that they can't be fixed. There's no information there because this thing has been through the mill already and and whatever detail it once may have had has already been destroyed. I might do something like this:

    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.
    Quote Quote  
Visit our sponsor! Try DVDFab and backup Blu-rays!