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.

 

Go Back   Doom9's Forum > Capturing and Editing Video > Avisynth Usage

Reply
 
Thread Tools Search this Thread Display Modes
Old 18th September 2010, 00:19   #1  |  Link
Chainmax
Huh?
 
Chainmax's Avatar
 
Join Date: Sep 2003
Location: Uruguay
Posts: 3,103
Weirdly blended X-Men DVDs, need help sorting it out

It seems like the poor X-Men just can't get a break, as every release there has been for them has an issue of some sort. Now, while the newest Disney DVD release is almost perfect, it has a strange artifact that fully seems like blending. Take a look at the following screenshot, taken only with SeparateFields() in the script:



The interlaced/progressive pattern is I-I-P-I-P, which I find unusual as well. In any case, here's a sample containing the intro and a high motion scene, please have a look at it and let me know what you think:

http://www.mediafire.com/file/uzu70p..._1.demuxed.m2v
__________________
Read Decomb's readmes and tutorials, the IVTC tutorial and the capture guide in order to learn about combing and how to deal with it.

Last edited by Chainmax; 28th September 2010 at 00:44.
Chainmax is offline   Reply With Quote
Old 24th September 2010, 00:01   #2  |  Link
Chainmax
Huh?
 
Chainmax's Avatar
 
Join Date: Sep 2003
Location: Uruguay
Posts: 3,103
One more thing to note: DGIndex found field order transitions, and this issue happens whether I load the fixed d2v or its "bad" version.
__________________
Read Decomb's readmes and tutorials, the IVTC tutorial and the capture guide in order to learn about combing and how to deal with it.
Chainmax is offline   Reply With Quote
Old 27th September 2010, 05:27   #3  |  Link
Chainmax
Huh?
 
Chainmax's Avatar
 
Join Date: Sep 2003
Location: Uruguay
Posts: 3,103
Anyone?
__________________
Read Decomb's readmes and tutorials, the IVTC tutorial and the capture guide in order to learn about combing and how to deal with it.
Chainmax is offline   Reply With Quote
Old 27th September 2010, 12:07   #4  |  Link
Emulgator
Big Bit Savings Now !
 
Emulgator's Avatar
 
Join Date: Feb 2007
Location: close to the wall
Posts: 1,190
Hi chainmax ! I already tried my luck and found some steps to go.

Please be patient, I can not continue right now:

Right now I have to solve an emergency case (Hammond repair for a major studio here in Berlin)
The band (famous act from the netherlands) wants to start their recording tomorrow,
and now this monster (a RT-3, the biggest one) is in my hands...
__________________
"To bypass shortcuts and find suffering...is called QUALity" (Die toten Augen von Friedrichshain)
"Data reduction ? Yep, Sir. We're working on that issue. Synce invntoin uf lingöage..."
Emulgator is offline   Reply With Quote
Old 27th September 2010, 19:15   #5  |  Link
Chainmax
Huh?
 
Chainmax's Avatar
 
Join Date: Sep 2003
Location: Uruguay
Posts: 3,103
Thanks, Emulgator
__________________
Read Decomb's readmes and tutorials, the IVTC tutorial and the capture guide in order to learn about combing and how to deal with it.
Chainmax is offline   Reply With Quote
Old 27th September 2010, 22:46   #6  |  Link
Emulgator
Big Bit Savings Now !
 
Emulgator's Avatar
 
Join Date: Feb 2007
Location: close to the wall
Posts: 1,190
Hm, lovely. Fieldblends in different strength all over the place.
Here DGIndex reports the demuxed source you provided to have Field order TFF globally.

I counted field pattern offsets in a spreadsheet and found something that works
for some parts of the clip's frames.

If one wants to have full frames back, including keeping some movement of background mattes:

ConvertToYV12(interlaced=true).QTGMC(EdiMode="NNEDI", tr2=3, sharpness=2.8)
SelectEvery(5, 1, 2)

This seems to work for fields 71/72 to 241/242. The fields before 70 are black or close to black, so I can not tell.

It breaks at fields 245/246.
245/246: here exist two 50/50 blended fields for the first problematic frame.
248 delivers a slightly blended field for the second problematic frame.
250/251 deliver two 50/50 blended fields for the third problematic frame.
Then 253 is a solitary field that delivers an almost unblended frame.

Then the pattern continues like 256/257, 261/262, 266/267, but breaks again later.

So maybe every z frames there is a another different offset for SelectEvery(5, x, y),

You might try searching this pattern...

AnimeIVTC choked.
__________________
"To bypass shortcuts and find suffering...is called QUALity" (Die toten Augen von Friedrichshain)
"Data reduction ? Yep, Sir. We're working on that issue. Synce invntoin uf lingöage..."

Last edited by Emulgator; 27th September 2010 at 22:48.
Emulgator is offline   Reply With Quote
Old 27th September 2010, 23:57   #7  |  Link
Chainmax
Huh?
 
Chainmax's Avatar
 
Join Date: Sep 2003
Location: Uruguay
Posts: 3,103
So, your line would work on fields [0, 242] x n and I'd have to manually fix fields [243,255] x n? Or are fields [243,255] x n unfixable?

This can't have been due to bad ripping: AnyDVD + DVD Decrypter in IFO mode is as straightforward a it comes...damn it, I can't believe even a new release can be so royally screwed up.
__________________
Read Decomb's readmes and tutorials, the IVTC tutorial and the capture guide in order to learn about combing and how to deal with it.
Chainmax is offline   Reply With Quote
Old 29th September 2010, 18:00   #8  |  Link
Emulgator
Big Bit Savings Now !
 
Emulgator's Avatar
 
Join Date: Feb 2007
Location: close to the wall
Posts: 1,190
These 3 have to be unblended, the pattern search may go on, maybe shifted.
Ripping is not the fault. But the treatment of the source definitely was.
I would like to continue searching, but right now too much is coming in for me.
One Organ saved, next is coming in.
Maybe I will find a way later.

Srestore is quite good at auto-deblending, just play around with that one.
A combination of
Assumefps(your guess here, 30000/1001, or 30)
Srestore() or (frate=your guess here)
Vinverse()
can bring out most of the good frames.
Some 12,5fps, 14.385614fps, 15fps should be the real source rate.
__________________
"To bypass shortcuts and find suffering...is called QUALity" (Die toten Augen von Friedrichshain)
"Data reduction ? Yep, Sir. We're working on that issue. Synce invntoin uf lingöage..."

Last edited by Emulgator; 29th September 2010 at 18:36.
Emulgator is offline   Reply With Quote
Old 23rd October 2010, 23:14   #9  |  Link
Chainmax
Huh?
 
Chainmax's Avatar
 
Join Date: Sep 2003
Location: Uruguay
Posts: 3,103
After reading up on SRestore, I finally got around to try it. Some tinkering showed pretty satisfactory results with this:

Code:
d = last.bob(-0.2,0.6).reduceflicker(strength=1)
TDeint(mode=1,type=1,edeint=nnedi3(field=-2),emask=TMM(mode=1))
SRestore(frate=23.976,omode="pp3",speed=-25,dclip=d)
vinverse()
TDecimate(mode=7)
But I did find a few problem spots. As an example, here's a chosen problematic frame:



And here are the ones that were being considered:

Frame 282:

Frame 283:

Frame 284:

Frame 286:

Frame 287:

Frame 288:


As you can see, frame 287 should have been chosen, or at least 286 or 288. The documentation regarding debug or display is not too comprehensive, so I do not understand how to tweak the "dupthresh" and "vidthresh" parameters to effect the final frame choice, or if that's possible at all. I will try Decomb's Decimate and SmartDecimate too, but for now I wanted to exhaust all possibilities here.
__________________
Read Decomb's readmes and tutorials, the IVTC tutorial and the capture guide in order to learn about combing and how to deal with it.

Last edited by Chainmax; 30th October 2010 at 14:07.
Chainmax is offline   Reply With Quote
Old 30th October 2010, 14:07   #10  |  Link
Chainmax
Huh?
 
Chainmax's Avatar
 
Join Date: Sep 2003
Location: Uruguay
Posts: 3,103
Sticking BlendBob after Srestore and before TDecimate did help a bit, but again, not perfect.
__________________
Read Decomb's readmes and tutorials, the IVTC tutorial and the capture guide in order to learn about combing and how to deal with it.
Chainmax is offline   Reply With Quote
Old 31st October 2010, 01:33   #11  |  Link
Nightshiver
Quality Freak
 
Join Date: Jun 2007
Location: Area 52
Posts: 597
You know, this is probably one of those sources that you won't be able to fix 100%, so you should already be prepared for that. If you dislike it so much, just do a bunch of freezeframe() calls.
Nightshiver is offline   Reply With Quote
Old 31st October 2010, 17:05   #12  |  Link
Chainmax
Huh?
 
Chainmax's Avatar
 
Join Date: Sep 2003
Location: Uruguay
Posts: 3,103
I am afraid that will turn out to be the case, but first I wanted to exhaust possibilities of there being an automatic way before resigning myself to examine each frame manually.
__________________
Read Decomb's readmes and tutorials, the IVTC tutorial and the capture guide in order to learn about combing and how to deal with it.
Chainmax is offline   Reply With Quote
Old 12th November 2010, 06:36   #13  |  Link
kazary
Registered User
 
Join Date: Aug 2006
Posts: 10
I was thinking about buying this DVD. got any good results?
__________________
Core i3 64 bit
kazary is offline   Reply With Quote
Old 12th November 2010, 06:56   #14  |  Link
Lyris
Registered User
 
Join Date: Sep 2007
Location: Europe
Posts: 601
Those images look absolutely hideous - not so much the field blending, but the total lack of detail. Is that something in your own script or have these been blasted with noise reduction?
Lyris is offline   Reply With Quote
Old 15th November 2010, 00:41   #15  |  Link
Chainmax
Huh?
 
Chainmax's Avatar
 
Join Date: Sep 2003
Location: Uruguay
Posts: 3,103
kazary: for now, all I have left to try is find the places the current script fails at and make an insanely high number of freezeframe calls. If I am lucky, I can find a function that links every instance of a bad decimation choice. If not, then I'll have to give up. It is, however, something that will take a long time and I can't feel like doing it just now, so unless a better way is found this will be on hold.

Lyrys: the current script is this:
Code:
TComb(fthreshL=6,fthreshC=7,othreshL=7,othreshC=8)

d = last.bob(-0.2,0.6).reduceflicker(strength=1)
TDeint(mode=1,type=1,edeint=nnedi3(field=-2),emask=TMM(mode=1))
SRestore(frate=23.976,omode="pp3",speed=-25,dclip=d)
vinverse()
TDecimate(mode=7)

RemoveGrain(mode=5)

Crop(6,0,704,480,align=true)

source=last
preNR=source.dfttest(sigma=1.25,tbsize=3).FFT3DFilter(sigma=4,plane=3,bw=32,bh=32,bt=3,ow=16,oh=16)
preNR_super=preNR.MSuper(pel=2, sharp=1)
source_super=source.MSuper(pel=2, sharp=1)
backward_vec3 = MAnalyse(preNR_super,isb = true, delta = 3, overlap=4)
backward_vec2 = MAnalyse(preNR_super,isb = true, delta = 2, overlap=4)
backward_vec1 = MAnalyse(preNR_super,isb = true, delta = 1, overlap=4)
forward_vec1 = MAnalyse(preNR_super,isb = false, delta = 1, overlap=4)
forward_vec2 = MAnalyse(preNR_super,isb = false, delta = 2, overlap=4)
forward_vec3 = MAnalyse(preNR_super,isb = false, delta = 3, overlap=4)
source.MDegrain3(source_super,backward_vec1,forward_vec1,backward_vec2,forward_vec2,backward_vec3,forward_vec3,thSAD=350)

FFT3DFilter(sigma=4,plane=3,bw=32,bh=32,bt=3,ow=16,oh=16)

aWarpSharp2(depth=16,chroma=4)

dull=last
sharp=last.LimitedSharpenFaster(SMode=4,Strength=150)
Soothe(sharp,dull,25)

GradFunkMirror(1.51)
So, as you can see, there isn't really that much in the way of detail killing. The source is just that bland. In all fairness though, this is a very high motion intro scene, and from a early 90s western cartoon, so it's probably par for the course. The show itself looks a little better.
__________________
Read Decomb's readmes and tutorials, the IVTC tutorial and the capture guide in order to learn about combing and how to deal with it.
Chainmax is offline   Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT +1. The time now is 13:43.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2022, vBulletin Solutions Inc.