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. |
5th December 2011, 02:26 | #1001 | Link |
Registered User
Join Date: Nov 2011
Posts: 3
|
Can anyone please help me find a way to eliminate the vertical shimmers in this clip?
Sample clip: http://www.mediafire.com/?zc2egghbal2vb11 The shimmers are most visible on the vertical lines of the window blind and cabinets. I even tried the preset "Placebo", but the shimmers are still there. Please pardon my ignorance if these are not called shimmers as I just started learning about encoding. I am still finding my way around MeGUI, QTGMC and Srestore. |
5th December 2011, 23:43 | #1003 | Link |
Registered User
Join Date: Nov 2011
Posts: 1
|
__________________
http://www.egitimduragi.com/ Last edited by bluered1; 7th December 2011 at 21:40. |
6th December 2011, 00:21 | #1004 | Link |
Registered User
Join Date: Jul 2010
Posts: 448
|
ihhm: QTGMC can deal with horizontal shimmering effects, but not really the vertical problems that clip is showing. It's not even a shimmer really, being rather occasional...?
Mr Alpha: Similarly, that doesn't initially look like anything to do with QTGMC, but I can't tell without seeing a short clip of the affected source. bluered1: You're welcome. |
6th December 2011, 10:43 | #1006 | Link | |
Registered User
Join Date: Jul 2008
Posts: 75
|
Quote:
|
|
6th December 2011, 21:46 | #1007 | Link |
Registered User
Join Date: Jul 2010
Posts: 448
|
That's a messed up source. The last shot is progressive and needs no deinterlacing. The first shot looks interlaced, and the top fields are fine, but the bottom fields are just a blend of the current and next frames (i.e. they do not contain a new temporal frame). I think the middle shot (from which your screen cap is taken) is the same. Then there's that fairly strong noise, over a detailed image.
You're not going to get double rate out of this, so QTGMC may not be the correct approach, although it does even out the differences in the fields - you'll want a SelectEven afterwards. The frame blending means the noise has a temporal echo, which may fool any temporal denoising into thinking it's not noise, meaning you need a stronger denoise that you would expect. A spatial denoise of sufficient strength will destroy the detail. Also the temporal processing of QTGMC is reinforcing the issue, leaving you with that fairly stable grain. Really this needs a more customized repair job, beyond the scope of QTGMC. Within the QTGMC settings you might want to set TR1=1 and TR2=0 (or 1), to reduce the temporal processing of QTGMC and stop the grain from being stabilized. That will leave you with more noise to get rid of though... Last edited by -Vit-; 6th December 2011 at 22:01. |
7th December 2011, 12:40 | #1008 | Link | |
Registered User
Join Date: Jul 2008
Posts: 75
|
Quote:
A side question: What about crop? Would it make more sense to move crop to before QTGMC and thus save me some pixels to process, or would that interfere with QTGMC? Last edited by Mr Alpha; 7th December 2011 at 12:43. |
|
7th December 2011, 14:02 | #1009 | Link | |
Registered User
Join Date: Jul 2010
Posts: 448
|
Quote:
Yes, that's fine. |
|
10th December 2011, 05:30 | #1010 | Link | |
partially-informed layman
Join Date: Jan 2002
Location: Bangkok, Thailand
Posts: 314
|
Quote:
e.g. Code:
#720x576 interlaced source QTGMC() NNEDI3_rpow2(rfactor=2, cshift="spline36resize", fwidth=1280, fheight=720) -Vit-, if you are considering including resizing in a future version of QTGMC, is this something you could look at instead of, or in addition to the more basic resizers? |
|
10th December 2011, 14:56 | #1011 | Link | |
Registered User
Join Date: Jul 2010
Posts: 448
|
Quote:
Last edited by -Vit-; 10th December 2011 at 15:00. |
|
13th December 2011, 14:04 | #1014 | Link |
Registered User
Join Date: Dec 2007
Location: Germany
Posts: 632
|
I have to disagree, the main purpose is to bob-deinterlace interlaced content which means the result has double the frame rate of the source.
There are no "adjacent frames" that need to be interpolated. It's actually the other way around, if you want to stay with the source frame rate, then you are throwing away 50% of the available temporal information (every other bob-deinterlaced frame is discarded). As a consequence, with most videos, especially ones with fast and/or shaky motion, this will lead to a stroby looking video. QTGMC offers the option to add motion blur to aid this but still it's naturally very recommendable to go with the double rate output if there's no particular reason not to (like YouTube). Last edited by TheSkiller; 13th December 2011 at 16:07. |
15th December 2011, 00:03 | #1018 | Link |
Registered User
Join Date: Apr 2002
Location: Germany
Posts: 5,389
|
At max settings, up to fourteen fields for each output frame.
Don't compare QTGMC (its workflow) with that of other deinterlacers. it works different, it IS different. Usual deinterlacers go "to weave, or not to weave, that's the question". QTGMC basically is a motioncompensated temporal superresolution filter.
__________________
- We´re at the beginning of the end of mankind´s childhood - My little flickr gallery. (Yes indeed, I do have hobbies other than digital video!) |
15th December 2011, 00:17 | #1019 | Link |
Registered User
Join Date: Dec 2007
Location: Germany
Posts: 632
|
tormento sorry you don't seem to understand how this whole deinterlace thingy of interlaced video works.
If you deinterlace an interlaced video using QTGMC("slower") naturally both fields will be taken into account for deinterlacing and that is why the output has double the frame rate of the input. It converts 50 fields per second (wrapped in 25 interlaced frames per second) to 50 frames per second. If you then try to end up with 25 progressive frames per second you are throwing away what originally was in every other field. So to take "both fields into account" you have to stick with double rate output, as simple as that. You cannot keep the motion of 50p or 25i (50i) with just 25p. The speed of the video stays the same of course, speed is not even involved at all. Last edited by TheSkiller; 15th December 2011 at 00:23. |
15th December 2011, 01:32 | #1020 | Link | |
Registered User
Join Date: Feb 2002
Location: San Jose, California
Posts: 4,406
|
Quote:
I love how you get to the heart of the issue without dumbing it down much. Thanks Didée. I have noticed that QTGMC does take both fields into account even if you output 25p, by this I mean there are more details on the output frame than exist on one field. I will have to leave how this is accomplished to others. |
|
Thread Tools | Search this Thread |
Display Modes | |
|
|