Spot/scratch removal

[Mephesto]

The video has already been denoised, so I don't need those combo filters that claim to denoise/degrain in addition to removing spots.

What is a recommended filter? RemoveDirtMC_SE looked sweet but I had no idea what to input for any of the parameters as the help file offered no explanation. What the hell is clmode and repmode? How many repmodes are there?

[dragonkeeper]

I'm also interested in this in the past I have used would use Cinepaint for scratch removal and restoration. While it gets the job done on a frame by frame bases its very tedious work to do so.

[sanlyn]

What is a recommended filter?

Depends on what you what you want a filter to do. Can you supply a sample of what you're trying to remove?

[Mephesto]

k.

[sanlyn]

I think that's more like a spot than a scratch.

Try the RemoveSpots() function mentioned in this thread: https://forum.videohelp.com/threads/341188-Still-have-flicker-after-Denoising-with-AviS...=1#post2129254

Note that RermoveSpots works far better if your video is IVTC'd as in the script in the above link. All most all scratch and spot filters require IVTC, deinterlace/reinterlace, or at least SeparateFields() to work properly.

[Mephesto]

Why should a spatio-temporal filter's efficacy depend on whether or not the picture is interlaced? I tried RemoveSpots() and it blurs motion unacceptably during movement.

Does anyone know how to properly work RemoveDirtMC?

[sanlyn]

Most filters of the type you're looking for require working with separated fields or deinterlaced (you can always rejoin frames or fields afterwards). Even some VirtualDub filters require you to designate whether a video is interlaced or not. They will either temporarily deinterlace or separate fields internally (DeFlicker, NeatVideo, and many VDub resizers, for instance). Many Avisynth denoisers that are motion-vector based (like, for instance, some of the plugins called by MCTemportalDenoise) suggest it as well. Perhaps you'd get better results if you use MCTD the way many of its called plugins suggest. RemoveDirtMC doesn't work well on interlaced video.

[Mephesto]

My video is progressive. I was wondering why RemoveSpots would work better on interlaced frames than progressive. The trick merely involves temporal displacement, not exactly a revolutionary trick. The motion-compensated ones are quite advanced, however. Unfortunately, I don't get the RemoveDirtMC parameters and the filter fails to load. I lost my copy of the original non-SE one.

Perhaps you'd get better results if you use MCTD the way many of its called plugins suggest.

?

[sanlyn]

My video is progressive. I was wondering why RemoveSpots would work better on interlaced frames than progressive.

Just the opposite, as stated earlier. Having no sample of your actual video, it's structure is unknown.

The trick merely involves temporal displacement, not exactly a revolutionary trick.

Some deinterlacers work well, some not so well.

The motion-compensated ones are quite advanced, however. Unfortunately, I don't get the RemoveDirtMC parameters and the filter fails to load. I lost my copy of the original non-SE one.

If you refer to RemoveSpots(), it doesn't use RemoveDirtMC. It uses the simpler version of RemoveDirt() which is a script, a dll, and several support plugins similar to MCTD. The "MC" version requires users to get fancy with some Microsoft .Net support files that are almost impossible to get straight, which is why it doesn't load for many users.

I haven't known RemoveDirt() (aka "RemoveSpots()") to blur. If you don't want any softening in your video (the captures look pretty soft already), you'd also avoid too many smoothers such as FluxSmooth.

RemoveSpots() uses v0.9 of RemoveDirt() available here: http://home.arcor.de/kassandro/RemoveDirt/RemoveDirt.zip
It also requires elements of RemoveGrain v.09 or later

[Mephesto]

Just the opposite, as stated earlier. Having no sample of your actual video, it's structure is unknown.

My bad, I misinterpreted your post and thought you said that it works better on interlaced material.

Some deinterlacers work well, some not so well.

I was referring to the spot remover.

If you refer to RemoveSpots(), it doesn't use RemoveDirtMC. It uses the simpler version of RemoveDirt() which is a script, a dll, and several support files, some of them also used by MCTD. The "MC" version requires users to get fancy with some Microsoft .Net support files that are almost impossible to get straight, which is why it doesn't load for many users.

I believe I acquired all dependencies, but I'll let the error speak for itself. See attachment.

I haven't known RemoveDirt() (aka "RemoveSpots()") to blur. If you don't want any softening in your video (the captures look pretty soft already), you'd also avoid too many smoothers such as FluxSmooth.

That video isn't the one I'm working with, I just picked it to highlight the kind of spots I'm dealing with as I was too lazy to find one on my video (there aren't too many.) My video is a cartoon and RemoveSpots() wrecks the hell out of moving backgrounds.

RemoveSpots() uses v0.9 of RemoveDirt() available here: http://home.arcor.de/kassandro/RemoveDirt/RemoveDirt.zip
It also requires elements of RemoveGrain v.09 or later

I see.

[sanlyn]

NLMeansCL is the problem for everyone. Everything I've read sez Avisynth doesn't recognize the commands that load some .Net support files. If anyone has a solution for it, I've never found it. Avisynth can't load AvsFilterNet.dll, or its partner NLmeansCL .net plugin. The author's official command for loading this stuff is:

LoadPlugin("[path to Avisynth plugins]\AvsFilterNet.dll") 
LoadNetPlugin("[path to Avisynth plugins]\NLMeansCL_netautoload.dll")

The plugins aren't your usual .ddl. They were written with .net c+ and require special loaders. I have yet to see anyone make it work. I'd like to see the solution myself. As far as I can tell, the only users who can make this thing work are those who have the full and latest Microsoft .Net development package on their 'puters.

As for RemoveSpots: it works on spots, freckles, sometimes scratches or "strings". It doesn't work on anything else. You should do your other denoising first, before using it.