View Full Version : Avisynth QTGMC please help me!
puppeteer
24th March 2024, 19:16
This is an interlaced video that is not a DVD. I get this result with Avisynth QTGMC, what is the reason? and is there a solution? Thanks in advance.
https://i.postimg.cc/T3bH1pnY/Shared-Screenshot.jpg (https://postimg.cc/9DWBNXxv)
Sample: https://mega.nz/file/lUdQUJYS#Eg0gY83xRNPTRBrMR113Dk76r1YUsB8LFvidKgjvw8Y
lollo2
24th March 2024, 19:53
Post the source
FranceBB
24th March 2024, 19:54
I can see that the video is 640x480, this means that whoever encoded it took the original 720x480 anamorphic file and brutally resized it before deinterlacing it!
That's... bad.
Your best bet is to resize to 720x480 first and then try to deinterlace to see if the fields magically match.
If they don't, we will have to take more drastic approaches.
Post the source
+1
As lollo said, please upload a sample and we're gonna try to help you. ;)
lvqcl
24th March 2024, 20:30
I can see that the video is 640x480, this means that whoever encoded it took the original 720x480
You mean 720x576?
puppeteer
24th March 2024, 20:37
This is an adult video, I don't know if I can share it here. Maybe I can share non adult part of video.
johnmeyer
24th March 2024, 20:40
Your problem is the result of resizing an interlaced video without first deinterlacing it. I don't think the script you posted is responsible for the problem.
puppeteer
24th March 2024, 20:49
this is sample Is there a way to fix this.
https://mega.nz/file/lUdQUJYS#Eg0gY83xRNPTRBrMR113Dk76r1YUsB8LFvidKgjvw8Y
FranceBB
25th March 2024, 06:23
You mean 720x576?
Oh crap, I completely missed the framerate, 25i!
Whoever encoded it the first time severely screwed up then as he downscaled a 720x576 25i to 640x480 while still interlaced... No wonder we're left with a field mess... :eek:
This is an adult video.
Hahahaha I was gonna say it when I read "Die unschuld von lande" (aka the innocence of the countryside) but I wasn't sure, thanks for pointing it out. By the way, I've seen far kinkier titles at work when I had to encode those kinds of stuff from dorcel and creaways and I'm not gonna lie I still laugh today when I read some of the titles lmao. Why people still watch those contents on linear is very much a mystery to me, though. Older generations I guess? XD
puppeteer
25th March 2024, 19:46
Post the source
I shared the source, is there a way to fix it?
Selur
25th March 2024, 20:02
resizing to 640x352 and upscaling to original resolution should remove some of the artifacts
adding some deflickering and spotless will help to remove some of the residual artifacts, but some will still be there
lollo2
25th March 2024, 20:53
I shared the source, is there a way to fix it?
The problem is in the source, not in QTGMC nor in your script (which is not optimal anyhow); in addition, the source is NOT interlaced, there is no de-interlacing to apply anyhow!
The solution proposed by Selur (Y downsize, resize) may mitigate some of the jagged edges introduced by the wrong processing in the source. Many threads on videohelp forum have attempt to fix this (common) problem, have a look at them.
FranceBB
25th March 2024, 22:20
Unfortunately the source is severely compromised by being resized while still interlaced.
What you can do, however, is a linear blending deinterlacing and blur vertically the lines to get rid of the interlacing artifacts.
This is gonna work:
#Indexing
video=LWLibavVideoSource("test.mp4")
audio=LWLibavAudioSource("test.mp4")
AudioDub(video, audio)
#Linear Blending Deinterlacing
mt_convolution("1","1 2 1",chroma="process")
#Vertical Blur
Blur(0.0, 1.0)
#Soft highlights rollback
Levels(0, 1.0, 255, 0, 235, false)
#Limited Tv Range
Limiter(min_luma=16, max_luma=235, min_chroma=16, max_chroma=240)
Left (Before) - Right (After)
https://i.imgur.com/Oa0aglm.pnghttps://i.imgur.com/x79iA6e.png
https://i.imgur.com/klbt8e0.pnghttps://i.imgur.com/m95XP2Q.png
This also takes care of the levels given that the original source is overshooting significantly way over 0.7V (i.e 235) and it's reaching almost 255, waaaaaay out of range.
Before (first picture) after (second picture):
https://i.imgur.com/O8hOErx.png
https://i.imgur.com/TZStWeb.png
This way you can then encode in Limited TV Range as always.
Cheers,
Frank
puppeteer
26th March 2024, 11:02
Unfortunately the source is severely compromised by being resized while still interlaced.
What you can do, however, is a linear blending deinterlacing and blur vertically the lines to get rid of the interlacing artifacts.
This is gonna work:
Left (Before) - Right (After)
https://i.imgur.com/Oa0aglm.pnghttps://i.imgur.com/x79iA6e.png
https://i.imgur.com/klbt8e0.pnghttps://i.imgur.com/m95XP2Q.png
This also takes care of the levels given that the original source is overshooting significantly way over 0.7V (i.e 235) and it's reaching almost 255, waaaaaay out of range.
Before (first picture) after (second picture):
https://i.imgur.com/O8hOErx.png
https://i.imgur.com/TZStWeb.png
This way you can then encode in Limited TV Range as always.
Cheers,
Frank
Thanks man, this works for me. I really appreciate your effort.
Selur
26th March 2024, 12:58
side note: using a combing mask (i.e. MTCombMask) with the convolution could save some additional details
using "santiag(strh=3)" also works for removing the combing artifacts.
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.