NTSC DVD Encoding Anomaly

[Sharc]

But in this file you often get a sequence like A B B B C D D D -- two unique frames, and two duplicates. You can see it in the attached clip if you step through frame by frame.

Ah yes. Where this happens the "fix" would be to add to the standard IVTC script

TDecimate(cycle=4,CycleR=2)
ChangeFPS(23.976)

Would require laborious manual work as I don't think it can be automated. Probably not worth the pain.

[aheatherly]

The "Christmas" disc isn't broken, it just looks like the encoder flagged progressive frames instead of using pulldown flags. I've seen that before. It's actually cleaner, not worse.

For the "Season 2" one, I'd split it. Run IVTC on the animation, deinterlace the car scene separately, then put them back together. That way you don't get the blends you're seeing with Bob 2x.

I've dealt with similar mixed sources. It takes a bit more work upfront but the result is smoother.

[Christheminecraft47]

For the "Season 2" one, I'd split it. Run IVTC on the animation, deinterlace the car scene separately, then put them back together. That way you don't get the blends you're seeing with Bob 2x.

I've dealt with similar mixed sources. It takes a bit more work upfront but the result is smoother.

Could be done, however in the video files I've demonstrated, at the end of the car scene, there is a 29.97i transition into the animation, which makes it extremely tedious and time-consuming. Plus, nobody's going to notice the blends when watching the content.

I don't really have the time to be this meticulous about it, and my final product is ultimately going to be 59.94fps anyways, so it's not really worth the time or effort to put in such work.

[VWestlife]

Just keep it as 59.94i, de-interlace using QTGMC, and don't worry about trying to put Humpty Dumpty back together again.

[Sharc]

Just keep it as 59.94i, de-interlace using QTGMC, and don't worry about trying to put Humpty Dumpty back together again.

Yes. See posts#10, #12 and #18 for example. Unfortunately he is not on Avisynth. So he has/wants to live with his mediocre deinterlacing with blends and jaggies.

[Alwyn]

@Christheminecraft4, for QTGMC use the new Vapourbox.

I'm a long-time AVISynth (basic) user and tried VB just now. For your use-case, to produce a QTGMC-deinterlaced lossless AVI to work on after, it's great.

It's a simple, GUI that works well. It can produce HUFFYUV files.

The install itself is 15mb but it will then download all the dependencies (~171MB) when you run it the first time.

Definitely worth a try if you don't like AVISynth but want QTGMC.

FWIW, the VDub2 deinterlaced-result is awful compared to the QTGMC version.

[Christheminecraft47]

# v1 is VTS_01_2.VOB

v1 = v1.ColorYUV(gain_y=-5, cont_u=-35, cont_v=-35)
hmask = v1.MaskHS(StartHue=160, EndHue=170, MinSat=30, MaxSat=80).BilinearResize(v1.width, v1.height)
v1 = Overlay(v1, v1.Tweak(hue=-2, sat=1.7), mask=hmask)

I know it's been awhile since I've chatted here, but I was wondering how I can actually use Avisynth to my advantage here, because I have been thinking about using it compared to what I have been doing previously in Avidemux. You guys seem to know what you're doing so I'm asking you. Oh yeah, I'm also gonna need the exact one you're using and a step by step on how to use it. Thank you in advance.

[jagabo]

You should use a recent 64 bit version of AviSynth+. You can get it from this site.
https://www.videohelp.com/software/AviSynth-Plus

You will probably need a source filter. I recommend LSMASH for 64 bit AviSynth:
http://www.avisynth.nl/index.php/LSMASHSource
Put the 64 bit dll files in AviSynth+'s plugins64+ folder.

I create my scripts with notepad. Be sure to change the file extension to .AVS instead of .BAT when you save the script. Many people prefer to use AvsPMod which is designed specifically for AviSynth scripts. It holds you hand a bit while creating scripts.
https://www.videohelp.com/software/AvsP

I usually use 64 bit VirtualDub2 to preview and debug my scripts.
https://www.videohelp.com/software/VirtualDub2

I usually use x264 CLI or ffmpeg CLI to encode the final results. Or you can use VirtualDub2 or any other editor/encoder that can use AviSynth scripts.

The script I gave you earlier in this thread is only a fragment. A full script needs to load the source file before processing can start:

v1 = LWlibAvVideoSource("VTS_01_2.VOB")

v1 = v1.ColorYUV(gain_y=-5, cont_u=-35, cont_v=-35)
hmask = v1.MaskHS(StartHue=160, EndHue=170, MinSat=30, MaxSat=80).BilinearResize(v1.width, v1.height)
v1 = Overlay(v1, v1.Tweak(hue=-2, sat=1.7), mask=hmask)

return(v1)