Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
10th August 2020, 23:44 | #41 | Link | |
Registered User
Join Date: Feb 2002
Location: California
Posts: 2,691
|
Quote:
I looked at the original and then looked at your initial attempt. I watched the original using VLC and watched it both with deinterlacing turned off as well as with VLC doing YADIF deinterlacing. I watched both clips several times and then looked at some snapshots. VLC's deinterlaced output looks better than your QTGMC output every single time. So, my recommendation still stands. If, in the future, there are no players or TVs which deinterlace (an extremely unlikely prediction, given the need to deal with legacy video) you can deinterlace then. In the meantime, you are wasting your time trying to deinterlace, and I stand by my original recommendation that you instead skip it. Your time would be much better spent denoising the source using MDegrain2 or something similar. |
|
11th August 2020, 00:04 | #42 | Link |
Registered User
Join Date: Aug 2010
Posts: 40
|
I definitely won't leave the result interlaced, it's a menace that in the future somebody will have to deal with it, either for editing, play on a PC, bad modern TV deinterlacing, etc
Yadif is inferior, the image just isn't good enough and the motion isn't that good even on 50fps mode QTGMC Slower-Slower / yadifmod2(order=1, mode=1) Note that on VLC yadifx2 (double framerate mode) on my sample doesn't recognize TFF and does BFF, ie back-and-forth frames and yadif on VLC is the original fps one which makes the motion choppy Last edited by Hacker?pcs; 11th August 2020 at 00:40. |
11th August 2020, 00:23 | #43 | Link |
Registered User
Join Date: Jan 2012
Location: Mesopotamia
Posts: 2,587
|
BWDIF Double rate bug just fixed https://github.com/Asd-g/AviSynth-BWDIF
Code:
AVISource("amarec(20200806-1406)_sample.avi") ConvertToYV16 AssumeTFF DFMDeRainbow(interlaced=true) QTGMC(EdiExt=BWDIF(-2),ThSAD1=1500,MatchTR2=2,tr2=2) not perfect but again it will be better when BWDIF get edeint parameter
__________________
See My Avisynth Stuff |
11th August 2020, 00:46 | #44 | Link |
Registered User
Join Date: Jan 2012
Location: Mesopotamia
Posts: 2,587
|
that because .avi should be BFF (avi has no info for field order IIRC)
__________________
See My Avisynth Stuff |
11th August 2020, 05:33 | #45 | Link | ||
Registered User
Join Date: Mar 2011
Posts: 4,823
|
Quote:
I used MPC-HC and de-interlaced with fffdshow, because you can force TFF, but even with the field order correct I think Hacker?pcs's original sample looks better than Yadif. There's less aliasing, although SourceMatch caused a little more flickering. Quote:
Personally I don't mind QTGMC's default settings, but I imagine it might look too "smooth" for some people. It gets rid of the noise though, and kills mist of the flickering. |
||
12th August 2020, 11:39 | #46 | Link | |
Registered User
Join Date: Aug 2010
Posts: 40
|
Quote:
Here are some tests, and a second sample with the small ball in the big picture motion that seems that Slower/Slower QTGMC doesn't handle well Sample 2: https://mega.nz/file/0ygF2ZCD#VYfabW...5CwkMzjPtWYmAQ 1) QTGMC(preset="Slower") 2) QTGMC(preset="Slower").QTGMC(Preset="Medium", InputType=1) 3) QTGMC(preset="Slower").QTGMC(Preset="Slower", InputType=1) 4) QTGMC(EdiExt=BWDIF(-2),ThSAD1=1500,MatchTR2=2,tr2=2) 1) https://mega.nz/file/p25V3B7I#2sWmhg...vseN325h5CDlGA https://mega.nz/file/9yoDwDhS#LM-xfw...T0SGPY4Wx4JXAs 2) https://mega.nz/file/0voFGJQZ#TndhRV...TiW5_DD_8XPsMM https://mega.nz/file/gihz1TxA#uqXCKR...gkP0rjUVNZrqUQ 3) https://mega.nz/file/Jyx1GDxb#yGLqdp...nZZtfjlqXwVoBM https://mega.nz/file/tjwBCJSC#FhDTAc...FLvtT4bFd-8MaA 4) https://mega.nz/file/MuxxAJJB#uLdObA...z7ZJZIedsHB5Pc https://mega.nz/file/ov53gR6Z#hFDL7I...HMjwDDesyt6bnI 1 vs 2 vs 3 vs 4 Notes: QTGMC 1 has visible flickering, 2 and 3 progressively removes it. 4 BWDIF has practically no flickering but the logo is a bit "pixelated", lower quality than the others Note: On QTGMC 1, Α and Δ letters are "jumpy", they are shaking visibly, on 2 and 3 this is progressively fixed. BWDIF 4 doesn't have jumpiness but there are interlacing artifacts Note: On the second sample I provided on this post, the motion of the moving ball is of concern. On QTGMC 1 it's good enough but on 2 and a lot more on 3 it deteriorates in non-natural way. BWDIF is similar to QTGMC 1 I think the Slower-Medium QTGMC solution for a balance in logo flickering - Ball motion and no interlacing artifacts may be my final choice Last edited by Hacker?pcs; 12th August 2020 at 11:44. |
|
12th August 2020, 21:15 | #48 | Link | |
Registered User
Join Date: Jan 2012
Location: Mesopotamia
Posts: 2,587
|
Quote:
it's better now anyway I still wait https://github.com/Asd-g/AviSynth-BWDIF/issues/3
__________________
See My Avisynth Stuff |
|
12th August 2020, 21:26 | #49 | Link |
Registered User
Join Date: Dec 2005
Location: Germany
Posts: 1,795
|
You need to ask in vapoursynth repo and then it gets ported to avs xD
But it's funny how the life cycle for some plugins are: avs to vs to avs
__________________
AVSRepoGUI // VSRepoGUI - Package Manager for AviSynth // VapourSynth VapourSynth Portable FATPACK || VapourSynth Database |
12th August 2020, 21:30 | #50 | Link |
Registered User
Join Date: Jan 2012
Location: Mesopotamia
Posts: 2,587
|
it's good idea but also bad since I am never used vs in my life so how can I tell if the update work? so since you use both then can you do it please?
__________________
See My Avisynth Stuff |
13th August 2020, 00:56 | #51 | Link | |
Registered User
Join Date: Aug 2010
Posts: 40
|
Quote:
QTGMC Slower-Medium / BWDIF try 2 (quoted above) If BWDIF gets the improvement you ask, will it get even better? Should I wait for it before I start encoding? :P |
|
13th August 2020, 01:23 | #52 | Link |
Registered User
Join Date: Jan 2012
Location: Mesopotamia
Posts: 2,587
|
Quote:
and yes it will be better, since BWDIF now act like Bob(0.0, 1.0) for spatial predictions which is very low qualty, when it get edeint it can have the best of nnedi3 (the QTGMC default spatial predictions) and BWDIF itself in the Temporal predictions (which give you the less logo flickering)
__________________
See My Avisynth Stuff |
13th August 2020, 02:42 | #54 | Link |
Registered User
Join Date: Jan 2012
Location: Mesopotamia
Posts: 2,587
|
I am not a Developer but I think it depend on how the code easy or hard to read, adding edeint itself should not be that hard and not need so much time
__________________
See My Avisynth Stuff |
13th August 2020, 23:02 | #55 | Link |
Registered User
Join Date: Nov 2009
Posts: 2,352
|
This is what I use and it dealt with the flickering and pixelation just fine, in case it helps:
Code:
QTGMC(tr2=3,preset="very slow",Lossless=1,sourcematch=2,sharpness=0.2,MatchEnhance=0.0,MatchPreset="Slow", MatchPreset2="Slow",border=false) |
15th August 2020, 20:09 | #57 | Link | ||
Registered User
Join Date: Mar 2012
Location: Texas
Posts: 1,664
|
Maybe worth a try (also read the following post in the QTGMC thread):
Quote:
Quote:
|
||
17th August 2020, 04:48 | #58 | Link | |
Banana User
Join Date: Sep 2008
Posts: 985
|
Quote:
"Medium" mode is least blurring in motion areas, I use "Slower" only if there is visible precision problems in stabilization, it looks like a view trough hot air, rarely happens on some scenes, so "Slower" is more precise stabilization but stronger blur in motion areas. |
|
17th August 2020, 05:18 | #59 | Link |
Cary Knoop
Join Date: Feb 2017
Location: Newark CA, USA
Posts: 397
|
The flickering is in the fields, it's not a deinterlace issue.
If you separate the fields you see the red spot popping up in the logo one in every four events on both fields. Masking (remove a bit of red coloration in a small area in the logo one in every four events) is the solution. Last edited by Cary Knoop; 17th August 2020 at 05:26. |
17th August 2020, 20:06 | #60 | Link | |||
Registered User
Join Date: Aug 2010
Posts: 40
|
Quote:
Quote:
Quote:
Last edited by Hacker?pcs; 18th August 2020 at 00:32. |
|||
Thread Tools | Search this Thread |
Display Modes | |
|
|