View Full Version : problem with MDegrain2
mathmax
11th October 2011, 00:56
Hello
I always have a problem when using MDegrain2 or MDegrain3 (from mvtools2). Suddently the image becomes very dark. If I run the script again, the problem appears randomly on other frames... this is very strange.
Here is an example:
http://img94.imageshack.us/img94/4964/48085251.jpg
and here is the code I use:
super = clip.MSuper(pel=2, sharp=1)
backward_vec2 = MAnalyse(super, isb = true, delta = 2, overlap=4,blksize=8)
backward_vec1 = MAnalyse(super, isb = true, delta = 1, overlap=4,blksize=8)
forward_vec1 = MAnalyse(super, isb = false, delta = 1, overlap=4,blksize=8)
forward_vec2 = MAnalyse(super, isb = false, delta = 2, overlap=4,blksize=8)
clip.MDegrain2(super, backward_vec1,forward_vec1,backward_vec2,forward_vec2,thSAD=400)
Does anyone know about this problem?
Taurus
11th October 2011, 12:43
Just the other day the same thing happened to me.
Without changing the script at a second attempt everything worked out fine.
So as this is the standard script from the MVTools2 Website
it would be interesting which version you are using.
I'm using the latest v2.5.11.3
mathmax
11th October 2011, 15:39
I use the same version..
And as I said, the problem is random. If I run the script again, the problem will appears on other frames. Sometimes the whole video is damaged.. sometimes only a few frames. This is very strange..
Also, when I view in virtualdub, the frames are always intact. The problem only occurs when I render in a video file.
Maybe I should run the script with something else than Vdub?
poisondeathray
11th October 2011, 15:54
where is the rest of the script ?
are you using directshowsource? you can get something like this with because frames get mixed up (not frame accurate or indexed)
mathmax
11th October 2011, 16:54
no, I use avisource(). Here is the full script:
avisource("delogo_1.avi")
separatefields()
top = SelectEven().smoothclip()
bot = SelectOdd().smoothclip()
Interleave( top, bot)
AssumeTFF()
AssumeFieldBased()
Weave()
function smoothclip(clip)
{
super = clip.MSuper(pel=2, sharp=1)
backward_vec2 = MAnalyse(super, isb = true, delta = 2, overlap=4,blksize=8)
backward_vec1 = MAnalyse(super, isb = true, delta = 1, overlap=4,blksize=8)
forward_vec1 = MAnalyse(super, isb = false, delta = 1, overlap=4,blksize=8)
forward_vec2 = MAnalyse(super, isb = false, delta = 2, overlap=4,blksize=8)
clip.MDegrain2(super, backward_vec1,forward_vec1,backward_vec2,forward_vec2,thSAD=400)
}
Didée
11th October 2011, 17:29
What is contained in "smoothclip()" ??
Also, swap the AssumeXXX() lines to
AssumeFieldBased()
AssumeTFF()
Weave()
That's (probably) not the cause of the crashes, but I'm not sure if your order is sane to do. ^This^ order is correct.
mathmax
11th October 2011, 18:05
What is contained in "smoothclip()" ??
Also, swap the AssumeXXX() lines to
AssumeFieldBased()
AssumeTFF()
Weave()
That's (probably) not the cause of the crashes, but I'm not sure if your order is sane to do. ^This^ order is correct.
the function smoothclip() is at the bottom of the script.
I inverted AssumeFieldBased() and AssumeTFF().. but still the same problem :-/
Didée
11th October 2011, 18:14
> the function smoothclip() is at the bottom of the script.
Oh crap, indeed. The acc. german proverb is "to have tomatoes on one's eyes". (When you don't see the obvious) :o :D
Hmh, no idea where that effect comes from. I've never experienced that.
Clutching at straws - what colorspace is your avi file?
mathmax
11th October 2011, 18:24
> the function smoothclip() is at the bottom of the script.
Oh crap, indeed. The acc. german proverb is "to have tomatoes on one's eyes". (When you don't see the obvious) :o :D
Hmh, no idea where that effect comes from. I've never experienced that.
Clutching at straws - what colorspace is your avi file?
http://img809.imageshack.us/img809/2240/info0000.jpg
Didée
11th October 2011, 19:09
Dunno. Lagarith Codec?
mathmax
11th October 2011, 19:38
I tried Lagarith, MSU lossless, or uncompressed AVI.. always the same problem...
Apparently the problem happens when I work on the field separately... but I remember that I also had sometimes the problem when processing a progressive video. To work on separate fields would increase the probability to get such errors?
Taurus
11th October 2011, 20:22
... but I remember that I also had sometimes the problem when processing a progressive video.
Yes, this is the same I've got encoding to UTVideo.
But only sporadic.
I alway thought this might be a colorspace issue I could not define.
But my whole chain is in YV12, so more guessing then knowing :D
It leaves a bad smell, doing countless test samples and afterwards watching the final encode burked somewhere in the middle..:mad:
vBulletin® v3.8.11, Copyright ©2000-2025, vBulletin Solutions Inc.