Still have flicker after Denoising with AviSynth

[unclescoob]

I'm not worried about colors yet, folks. I'm still on the stage of getting MCTemporalDenoise to work, but I did not have an opportunity to do that last night. In terms of color correction, I'm currently using tweak(sat0.8) and that helps me just fine with the reds, particularly. I'm sure the posted method works much better and I will get to it...but first... MCTemporal ok? I don't want to get ahead of myself nor become confused. Please keep in mind that I just got slightly comfortable with avisynth the other day, after much tackling with it. So baby steps for me.

Once I load the script as advised and see the results, I will post additional information.

Thanks.

[2Bdecided]

Thanks, jagabo. Yep, I figured it was the clip. Never saw it before, doesn't happen any other time. I clipped off the weird frames. What was really odd was that frame 2 in the "bad" frames is actually another 7 or 8 frames down the line. I kinda guessed something was wrong with that first frame group.

When there are frames from an Open GOP that can't be decoded, some decoders will delete them, but DGindex will try to keep them, or repeat other frames, to avoid changing the overall number of frames (and hence maintain audio sync without messing with the audio). It'll also pop-up a notice about open GOPs to warn you about what it's doing.

Cheers,
David.

[jagabo]

I also find that if you seek back and forth near the beginning of such a video you don't get the same frame every time.

[unclescoob]

Can we please stick to the subject?

[sanlyn]

I'm not worried about colors yet, folks. I'm still on the stage of getting MCTemporalDenoise to work, but I did not have an opportunity to do that last night. In terms of color correction, I'm currently using tweak(sat0.8) and that helps me just fine with the reds, particularly. I'm sure the posted method works much better and I will get to it...but first... MCTemporal ok? I don't want to get ahead of myself nor become confused. Please keep in mind that I just got slightly comfortable with avisynth the other day, after much tackling with it. So baby steps for me.

Understandable, unclescoob. I had a helluva time with MCTD the first time I put it together over a year ago. I don't know if you missed it, but I posted a zip file yesterday attached to an earlier post, here. The ZIP has everything I've been using with MCTD for over a year. There's a folder with two files that belong in System32 (just copy them into that folder). Another folder has all the scripts and plugins you need in the Avisynth plugins folder.

The only other Avisynth piece you might need is the script stab.avs. That's a separate function, so I attached a copy of it below. Copy it directly to your Avisynth plugins folder as-is.

The script I used is the same as jagabo's script as posted here with no changes. Very similar to MCTD and Deflick scripts I've been using.

You're correct about saturation. Red ain't the only problem there, but you're right to clean up noise first. Can tackle color later.

Holler if any problems.

[unclescoob]

No doubt, sanlyn. Good lookin' out. I'll check this tonight.

[unclescoob]

As far as "bad frames" is concerned...it's an 80's animated cartoon folks, not a Pixar production. I don't notice any 'bad frames' when it's playing on TV, so I don't really care about it. If it doesn't affect my filtering (the way interlaced frames would if I had not IVTC first) then it's another story. I'm not going to start finagling with the frames, and botching up my stuff, just because I can. Next thing you know, I have choppy video that is out of sync because I'm trying to play Frames God on my video. So let's just please stick to the subject of cleaning this up, fixing the colors and I'll move on with my life. I'm not clipping anything other than my toenails.

[sanlyn]

Your original download played OK. Likely a glitch with my own setup. Sometimes happens with certain apps.

[2Bdecided]

Can we please stick to the subject?

So let's just please stick to the subject of cleaning this up

When you're paying our wages, you get to tell us what to do.

When you own the forum, you get to tell people what they can talk about here.

In the meantime...



If it's old film, the removedirt / degrain pair in the middle of the 8mm film restoration script is a great start. stab() first works wonders too. e.g. hacking out the relevant part...

stab()

denoising_strength= 900  #denoising level of second denoiser: MVDegrainMulti() 
denoising_frames= 3  #number of frames for averaging (forwards and backwards) 3 is a good start value
block_size= 16  #block size of MVDegrainMulti()
block_size_v= 16
block_over= 8  #block overlapping of MVDegrainMulti()

Import("03_RemoveDirtMC.avs")


#CLEANING/PRESHARPENING/RESIZING
#..........................................................................................................................................


#CLEANING PARAMETERS
#--------------------------------------------------------------------------------------------------------------

dirt_blur= 0.1 # some blur before cleaning to avoid pixel artifacts
dirt_strength=40 # set this lower for clean films.


#DENOISING PARAMETERS
#----------------------------------------------------------------------------------------------------------------------------


denoising_strength= 900  #denoising level of second denoiser: MVDegrainMulti() 
denoising_frames= 3  #number of frames for averaging (forwards and backwards) 3 is a good start value
block_size= 16  #block size of MVDegrainMulti()
block_size_v= 16
block_over= 8  #block overlapping of MVDegrainMulti()





# FOUR STEP SHARPENING PARAMETERS
#--------------------------------------------------------------------------------------------------------------------------------

USM_sharp_ness1= 120   USM_radi_us1= 3  #first sharpening (UnsharpMask) after cleaning with removedirtMC()

USM_sharp_ness2= 80    USM_radi_us2=2   #second harpening (UnsharpMask) after cleaning with removedirtMC()

USM_sharp_ness3= 70    USM_radi_us3=1   #third sharpening (UnsharpMask) after degraining with MVDegrainMulti()


last_sharp= 0.4 #final sharpening step after interpolation

last_blur= 0.2 #this smooths out the heavy sharpening effects



#AUTO LEVELS PARAMETER
#--------------------------------------------------------------------------------------------------------------------------------
X=2   # X is a special parameter for reducing the autolevels effect on the whites
X2=2  # X2 is a special parameter for reducing the autolevels effect on the blacks 





stab2=last


noise_baseclip=stab2.blur(dirt_blur)




cleaned= RemoveDirtMC(noise_baseclip,dirt_strength)# .unsharpmask(USM_sharp_ness1,USM_radi_us1,0).unsharpmask(USM_sharp_ness2,USM_radi_us2,0).Lanczos4Resize(W,H)



#DEGRAINING/SHARPENING
#...................................................................................................................................................................


vectors= cleaned.MVAnalyseMulti(refframes=denoising_frames, pel=2, blksize=block_size, blksizev= block_size_v, overlap=block_over, idx=1)
denoised= cleaned.MVDegrainMulti(vectors, thSAD=denoising_strength, SadMode=1, idx=2).unsharpmask(USM_sharp_ness3,USM_radi_us3,0)

return denoised

from http://forum.doom9.org/showthread.php?t=144271

Cheers,
David.

[unclescoob]

David, mate would you do me a favor and apply that script to the sample clip I posted? I'm just curious as to how it would look. If it's not too much trouble.

[sanlyn]

Coming up with new scripts looks pretty interesting, but unclescoob is still trying to get MCTemporalDenoise to run.

[sanlyn]

If it's old film, the removedirt / degrain pair in the middle of the 8mm film restoration script is a great start. stab() first works wonders too. e.g. hacking out the relevant part...

[code]
. . .
Import("03_RemoveDirtMC.avs")
. . .

2B: that looks like part of Video Fred's script. Does 03_RemoveDirtMC.avs actually exist?

[unclescoob]

Hi folks. This is an extremely busy week for me, so I'm not going to get to this script until Monday morning. Just letting you all know. Merry Christmas.

[sanlyn]

I'll be in Tennessee, but the laptop will be with me.So Merry Whatever, as the line goes in the 1951 Brit classic A Christmas Carol, "In keepin' with the sit-yew-ation".

I ran jagabo's script again as before but added jagabo's RemoveSpots() function, his modification of RemoveDirt(). Cleaned up all the dots and freckles except for one or two tiny ones:

Left image = original m2v. Right image = after script with RemoveSpots().
Top = small white dot on chest of guy's jacket
Middle: white string to left of girl's earring
bottom: white freckle on lower right margin


[Attachment 10211 - Click to enlarge]

Script with RemoveSpots() added near bottom:

# ###################################################
#
# Added function RemoveSpots(), requires RemoveDirt()
#
# ###################################################

LoadVirtualDubPlugin("D:\VirtualDub\plugins\deflick.vdf","DeFlick") 
import("D:\AviSynth 2.5\plugins\Stab.avs")

Mpeg2Source("G:\forum\toon1\sample1.d2v", CPU=6) 
AssumeTFF()
TFM(d2v="G:\forum\toon1\sample1.d2v")
TDecimate() 

ColorYUV(off_y=6,cont_y=-5)
ColorYUV(cont_v=-18)
ColorYUV(gain_y=-12)
Tweak(coring=false,sat=0.95) 

Stab(dxmax=2, dymax=2)
Crop(10,2,-6,-2)

ConvertToRGB32()
DeFlick(8, 0, 0, 10, 0) # - window size,softening,interlaced,sc threshold,show sc
ConvertToYV12()
McTemporalDenoise(settings="very high")

RemoveSpots()  # <-- ADDED
AddBorders(8,2,8,2)
ConvertToRGB32(matrix="Rec601")

function RemoveSpots(clip input, bool "_grey", int "repmode")
{
_grey=default(_grey, false)
repmode=default(repmode, 16)
clmode=17
clensed=Clense(input, grey=_grey, cache=4)
sbegin = ForwardClense(input, grey=_grey, cache=-1)
send = BackwardClense(input, grey=_grey, cache=-1)
alt=Repair(SCSelect(input, sbegin, send, clensed, debug=true), input, mode=repmode, modeU = _grey ? -1 : repmode )
restore=Repair(clensed, input, mode=repmode, modeU = _grey ? -1 : repmode)
corrected=RestoreMotionBlocks(clensed, restore, neighbour=input,  alternative=alt, gmthreshold=70, dist=1, dmode=2, debug=false, noise=10,  noisy=12, grey=_grey)
return corrected
}

[unclescoob]

I loaded all the dll files in my Avisynth plugins folder.

The McTemporalDenoise avsi is in my plugins folder.

I placed the fft3d in system32

Tried to load McTemporalDenoise(settings="very high") on my script

Nothing.

Any suggestions?

[unclescoob]

actually, I should be a bit more specific:

I'm doing this with AvsPmod. When I try to call MC, I get a message that says:

FFTR3DFilter: Can not load FFTW3.Dll!

[jagabo]

If you are running 32 bit AviSynth and VirtualDub under 64 bit Windows fftw3.dll goes in the SysWOW64 folder.

[unclescoob]

I have a 32 bit system

[jagabo]

Then C:\Windows\System32\fftw3.dll is usually the right place.

[unclescoob]

I know. And that's why I placed it there. Nothing.

Sigh

[unclescoob]

Does it make a difference what automatic program I use to open the actual file? for instance, the fftw opens with word if I click on it. Should I change it?

[unclescoob]

Or maybe I'm not calling it correctly in my script. How should my script look like, as an example

[jagabo]

If all the filters are installed in your plugins folder you can get away with as little as:

WhatEverSource()
MCTemporalDenoise()

Or:

WhatEverSource()
MCTemporalDenoise(settings="high")

Of course, MCTD has a lot of other settings, but you can use as little as the above.

[sanlyn]

Or maybe I'm not calling it correctly in my script. How should my script look like, as an example

The script most of us have been using is jagabo's, posted here:
https://forum.videohelp.com/threads/341188-Still-have-flicker-after-Denoising-with-AviS...=1#post2128405

Here's another copy of it:

LoadVirtualDubPlugin("[path to VirtualDub folder]\plugins\deflick.vdf","DeFlick") 
import("[path to Avisynth folder]\plugins\Stab.avs")

Mpeg2Source("[path to folder containing video]\sample1.d2v", CPU=2) 
TFM(d2v="[path to folder containing video]\sample1.d2v") 
TDecimate() 
Stab(dxmax=2, dymax=2)
Crop(10,2,-6,-2)
ConvertToRGB32()
DeFlick(8, 0, 0, 10, 0)  #--window size, softening, interlaced, sc threshold, show sc
ConvertToYV12()
McTemporalDenoise(settings="very high")
AddBorders(8,2,8,2)

When running MCTD it takes several seconds for everything to load. MCTD at "High" or "very high" is very slow, slightly slower than NeatVideo. If you have a load of filters like these and you advance 1 frame, it takes a few seconds for each fame to advance. Try runnng it in VirtualDub just to see if the script is running, period. But give it time to load. Remember, effectively you're running a script that actually requires a big handful of powerful plugins and dll's.

[sanlyn]

actually, I should be a bit more specific:

I'm doing this with AvsPmod. When I try to call MC, I get a message that says:

FFTR3DFilter: Can not load FFTW3.Dll!

I never heard of "FFTR3Dfilter". FFT3D uses two dll's:
FFTW3.ddl - in system32
fft3dfilter.dll - in Avisynth/plugins

AvsPMod occasionally has a problem with some filters. Why not run the script the "old" way in VirtualDub?. Big plugins like these won't load any faster in AvsPmod anyway. In the script, FFT3D isn't called explicitly, it's loaded by MCTemporalDenoise depending on the MCTD parameter settings.

[unclescoob]

You know what, **** all of this.

This is so frustrating it's not even fun anymore. This filter requires that filter, that filter requires this dll, this is a script, but this is a function. Call this script, but mention the function. Paste this here, take this away from there, add it to your system 32, but make sure the damn hip bone is connected to the dick bone. I'm done. This is why I hate Avisynth. For all it's supposed limitless powers, it's a pain in the ass to get it to do what you want. The authors of these filters really need to get their shit together, and make this RELATIVELY user-friendly (hint, user friendly does not have to mean MORON friendly, as some may think).

I am not going to sit in front of a ******* screen all day (as I am ashamed to admit I have) playing 'cat and mouse' and 'where's waldo' with this shit. **** my video, and **** whatever I was going to do with it. I have better shit to do. This is just not fun anymore. It has become obnoxious and the pretentious mystery behind everything is not impressing me. MAKE FILTERS THAT ******* WORK FOR EVERYONE!

[Mephesto]

You know what, **** all of this.

This is so frustrating it's not even fun anymore. This filter requires that filter, that filter requires this dll, this is a script, but this is a function. Call this script, but mention the function. Paste this here, take this away from there, add it to your system 32, but make sure the damn hip bone is connected to the dick bone. I'm done. This is why I hate Avisynth. For all it's supposed limitless powers, it's a pain in the ass to get it to do what you want. The authors of these filters really need to get their shit together, and make this RELATIVELY user-friendly (hint, user friendly does not have to mean MORON friendly, as some may think).

I am not going to sit in front of a ******* screen all day (as I am ashamed to admit I have) playing 'cat and mouse' and 'where's waldo' with this shit. **** my video, and **** whatever I was going to do with it. I have better shit to do. This is just not fun anymore. It has become obnoxious and the pretentious mystery behind everything is not impressing me. MAKE FILTERS THAT ******* WORK FOR EVERYONE!

lol, true. You gotta remember that the avisynth-pimping crowd consists of overzealous fucktards with chronic fanboy syndrome who insist on obtuseness to forward their fanboy wet dreams. Video editting is difficult and tedious enough with visual control, let alone with a ******* command-line. Of course, we are just CLphobic newbs who just aren't dedicated enough.

However, understand that people who create Avisynth filters do it in a way that makes it easier and less tedious for them, which may result in it being less user-friendly for the end user. That we can't condemn them for. I would put far less effort.

Good luck on restoring your video sometime.

[unclescoob]

**** my video, and **** whatever I was going to do with it.

You know, in retrospect, this is the only thing I take back out of everything I said. I'm going to IVTC and YUV12 with Avisynth (as I still use HcEnc), and everything else can go piss off. Virtualdub, baby....I'm sorry I wronged you! I'm coming home, sweetheart!!

the avisynth-pimping crowd consists of overzealous fucktards with chronic fanboy syndrome who insist on obtuseness to forward their fanboy wet dreams. Video editting is difficult and tedious enough with visual control, let alone with a ******* command-line. Of course, we are just CLphobic newbs who just aren't dedicated enough.

ABSOLUTELY. And thank you for being the second person to remind me that I'm not the only one who thinks that.

people who create Avisynth filters do it in a way that makes it easier and less tedious for them, which may result in it being less user-friendly for the end user.

Oh, no I do understand. No doubt about that.

Good luck on restoring your video sometime.

Thanks. I have an idea.

[sanlyn]

I'm going to IVTC and YUV12 with Avisynth (as I still use HcEnc), and everything else can go piss off. Virtualdub, baby....I'm sorry I wronged you! I'm coming home, sweetheart!!

Although I'm running these scripts on your video all day long and even adding more cleanup plugins with no problem (unless I mistype something), I'll agree on the point that much Avisynth material is in a state of chaos. Waiting for some bright boy (not me, I'm not that bright) to get it altogether one of these days. However, even with VirtualDub's just-click-me interface, it still helps to spell correctly and keep some basic terms straight in your head. . .

YUV12 ? Good luck. I though DVD was YCbrCr, not YUV.

[unclescoob]

I uninstalled and re-installed Avisynth and AvsPmod in my system last night. I'm just trying to get the Mpeg2Source.dll (Sanlyn, if you can help me get that, it would help).

You're running scripts on my video? Look, I don't want your efforts to be in vain, so for the sake of it all, I'm going to try this ONE MORE TIME. Maybe I had missing dll's due to improperly installing one of the two. Who knows?

Sanlyn, can you please post a cleaned-up clip for me so that I can see if it's even worth the trouble?