I use TDeint to deinterlace and SRestore to bring the framerate back to 23.976 instead of 59.940. However there is a weird line effect that isn't preset in the source but in the encode. I would say this is because the source is a mix of hard and soft telecine and this part is only soft-telecined, and TDeint is trying to deinterlace a progressive source.Code:MPEG2Source("%source_file%") TDeint(mode=1, mtnmode=3, blim=100) LoadPlugin("J:\StaxRip-x64-188.8.131.52\Apps\Plugins\AVS\GRunT\GRunT.dll") Import("J:\StaxRip-x64-184.108.40.206\Apps\Srestore.avsi") Srestore(frate=23.976) KNLMeansCL(D = 1, A = 1, h = 4, device_type="auto") DeHalo_alpha_mt(rx=2.0, ry=2.0, darkstr=1.0, brightstr=1.0, lowsens=50, highsens=50, ss=1.5)
Deinterlaced and IVTC'd video:
+ Reply to Thread
Results 1 to 14 of 14
Deinterlacers sometimes misidentify closely spaced horizontal lines as interlacing and kick in a deinterlacer. That's probably what you are seeing. Upload a short sample if you want it examined more closely.
TDeint is trying to deinterlace a progressive source.
Deinterlaced and IVTC'd video:
As jagabo suggests, a short sample will tell the tale.
Last edited by manono; 13th Jan 2019 at 21:43.
For double frame rate field matching (much faster than QTGMC) try:
Zoom in, it's very faint:
Isn't this interlaced YV12 being treated as progressive YV12 or vise versa? The source VOB claims to be Progressive scan in MediaInfo, but it has the 2:3 Pulldown flags. It's mix of hard and soft telecine. This scene at the toy factory seems to be hard telecined.
Last edited by Vitality; 14th Jan 2019 at 09:00.
If the IVTC doesn't work well - and sometimes it doesn't - then the bob/decimate solution might sometimes work better. But you're using the wrong bobber (TDeint(Mode=1)) if the resulting aliasing bothers you. My suggestion was to try QTGMC as the bobber. It wasn't really designed to work with animations with repeated frames, but you'll never know until you try. jagabo proposed a different solution which, apparently, improves the result. The resulting minor interlacing can be removed by adding Vinverse afterwards or, perhaps, by lowering the CThresh.
Manono, as usual, is correct:
IVTC <> Deinterlacing
MPC-HC, hardware deinterlace), but when you watch it raw it just looks like interlacing lines.
Is there anywhere to remove the chroma bleed? And if the deinterlace filter is causing the chrome bleed, could I hook up my DVD player over composite/S-Video into my Digital8 camcorder and stream the "raw" NTSC signal to my PC over DV-AVI?
Last edited by Vitality; 14th Jan 2019 at 14:36.
All of this was covered in your previous thread.
The chroma of your video is screwed up in the source. The luma is screwed up in places too. Problems like this are quite common with cartoons because shots are often crudely time adjusted after being telecined.
You can always go through and replace bad frames with the frame before, the frame after, or a motion interpolated frame.
Handbrake has some good routines built into it. It's not a slouch. But anything they have is going to be outclassed by what's available for AVISynth. I just think you're not applying the filters in the correct way. TFM will do exactly what Deinterlace-Decomb does(deinterlace only the combed areas), but do it better and in higher quality. Use something like this:
TFM(pp=7,mode=3,clip2=i.deint(mode=2,edeint=edeint )) #Also try pp=6. Add the "mi" parameter and continue to decrease if you still see residual interlacing