SpotLess - Temporal denoise

[coolgit]

Originally Posted by VoodooFX

You are trying to return "last" when not doing anything in your script.

Maybe this you want:
output=SpotLess(source)
return output

I tried that but the left viewer and right viewer of vdub is the same. Is it possible to have
return source output etc or does return only has 1 expression.

[StainlessS]

Vdub2 is not part of nor related to avisynth, it is a stand alone editor, with its own input and output viewing windows.
You can turn off VD2 windows, either input or output [it calls them panes I think], in the view menu, [again I think, I'm not on windows].
Avs users may use VD2 as a viewer for avs files, but you can view the output of AVS via eg PotPlayer, or MPC-HC, or in the AVS
dedicated GUI AvsPMod, your choice.

EDIT: VD2 does have an AVS script editor, added because I asked for it, by that nice guy "Shekh The Magnificent",.

EDIT: Unless you've done some filtering in VD2 of input Avisynth script or other video input,
both input and output panes will be exactly the same.
If avisynth outputs a stacked clip, then the stacked output will show in both VD2 panes.
As I said earlier, I usually make the output pane in VD2 as small as possible and only view a single pane. [or you can turn it off].

EDIT: Kinda nifty name, CoolGit, I'm sorta wishin' I'de gone with Ol'Fart, or I knida gotta hankering for BogBlocker too

[coolgit]

I do get the above but avisynth doesn't make it easy to work with.

So i can compare using StackHorizontal then when i am happy put a # before StackHorizontal then refresh then save new file. Next time i've got to remember to remove the #. Back and forth.

Surely avisynth can do better at outputting.

Is there not a save command for script? Use StackHorizontal for comparison then type save(newfilename) in script.

It's all working now. Is there a way of increasing threshold or whatever in spotless to increase effectiveness. Sometime the spot replacing pixels are a bit too light. ThSAD,10000 what does this do? I tried playing around with the numbers but couldn't see any effects.

[StainlessS]

Avisynth is video editing frameserver, it takes in some video clip, edits in some way and then produces an output video clip.
Thats all it does, thats all its meant to ever do.
I think that you originally used it with MeGUI, if avisynth were as you suggest, it would not be usable with MeGUI.
The purpose behind its use was to be able to eg feed into an encoder without saving the edited file to disk,
and the massive amount of disk space required to do that. [originated in about 2002 when hard drives were much smaller].

[EDIT: my 1st hard drive was 20MB and cost aboout £400.00, in late 80's, early 90's]

Maybe you would be happier with a more traditional video editor, you dont sound like you feel cut out for it.

Current beta of Spotless, with docs.
http://forum.doom9.org/showpost.php?...4&postcount=69

If you need further background, you could read MvTools2 docs too.

EDIT: VirtualDub can [or older versons of it used to, probably still can] act as a FrameServer,
but with large fast disks that ability becomes maybe obsolete.
Avisynth has a pretty big bank of plugins and scripts, that can and are being used by many open source
projects, nobody wants to throw that in the bin. If you need an avs specific gui, try AvsPmod, thats what its for.

[some people use a text editor (me included) and some viewer eg MPC-HC player, that is their choice, you also have yours]

[coolgit]

Originally Posted by StainlessS

[EDIT: my 1st hard drive was 20MB and cost aboout £400.00, in late 80's, early 90's]

Maybe you would be happier with a more traditional video editor, you dont sound like you feel cut out for it.

105mb approx £200 1991. A friend and I spent days deliberating between 105 and 115mb - costing £40 more.

Nowadays looking back it sound pathetic.

I do use video editor, a fair few according to tasks. But dust, scratches, spots, scene changes, all are pretty poor. Even pro software costing zillions are crap.

[StainlessS]

Not sure, maybe mine was more expensive than for typical PC, was for Atari-ST, and more specific interface, ACSI rather SCSI, I think,
but I guess coulda been as early as about 86. [EDIT: Actually, I still got it]
My [first] Sinclair QL 'Floppy' drive was about £150.00 - £200.00, [with some special interface, about 256KB (perhaps 128KB) RAM and maybe some toolkit], and I bought from the firm I worked for at the time [bit cheaper].

[VoodooFX]

Originally Posted by coolgit

I tried that but the left viewer and right viewer of vdub is the same. Is it possible to have
return source output etc or does return only has 1 expression.

AvS is not vdub's filter, output of AvS is input for vdub, you can run two instances of vdub and do compare switching between them.

[coolgit]

StainlessS

Tm       = Default(tm,True)       # TrueMotion, Some folk swear MAnalyse(truemotion=false) is better.

True works better. It took a nice longish scratchy defect and replaced it 99%. I tried false and the replacement was 60%.

[StainlessS]

True works better.

And there was me considering making false the default, guess I maybe leave as it is.

[coolgit]

Rendering spotless is 20 fps. Any way to make it faster?

Default(ThSAD,10000) - what does the number do? Tried playing with and couldn't see any effects.

[johnmeyer]

Are you using multi-threading? Set Prefetch() to use multiple cores.

[coolgit]

Originally Posted by johnmeyer

Are you using multi-threading? Set Prefetch() to use multiple cores.

Using vdub2 script for spotless. Is set prefetch suppose to go in the script?

[coolgit]

Had some fun yesterday/today using spotless on some Laurel and Hardy films. Those great B&W films had too many (5 to 20 per frame) flickering. Claims by various film restoration companies are outrageous. How they claim to have restore the film and not remove one flicker is beyond me. It takes no more than 10 minutes or less per film.

I improved the quality by 1000% simply by removing all the flickering. Some were the size of 2 pence coin. In some case I ran spotless twice on the same film.

All is great. Film Dirt Cleaner consigned to the recycle bin and eradicated forever.

[StainlessS]

I'm guessin' that some love the flicker. [There's nowt so queer as folk. https://en.wiktionary.org/wiki/there..._queer_as_folk ]

[StainlessS]

CoolGit,

Maybe try this out, could be useful in B&W restoration. [selective processing]

ColorBars(pixel_type="YV12").ShowFramenumber.KillAudio

# Need the latest Beta Spotless for DC clip.
DC_Radius=7 # Frames to average
DC_SC=25    # Scene change detect
DC=TemporalSoften(DC_Radius,255,255,DC_SC,2).Blur(0.6,0.6)  # Detect clip for Spotless, hopefully less prone to be fooled by flickering [untested, tweak DC_Radius]

#DC = Blur(0.6,0.6) # Alternative prefiltered analysis clip, without TemporalSoften, or Roll-Your-Own DC.

V1 = SelectEvery(1,-1)                                     # CopyFromPreviousFrame [replace current frame with its predecessor]
V2 = SelectEvery(1, 1)                                     # CopyFromNextFrame [replace current frame with its successor]
V3 = Spotless(RadT=1,BlkSz=16,TM=False,Glob=true,dc=DC)    # Un-spot Single frame spots. DC prefiltered clip for motion analysis.
V4 = Spotless(RadT=2,BlkSz=16,TM=False,Glob=true,dc=DC)    # Un-spot Double frame spots. DC prefiltered clip for motion analysis.
V5 = Spotless(RadT=3,BlkSz=16,TM=False,Glob=true,dc=DC)    # Un-spot Triple frame spots. DC prefiltered clip for motion analysis.
V6 = FlipVertical
V7 = Invert
# Etc

Nicks = """ # NickNames (pseudonyms) for use in SCMD or CMD file.
    CP  = 1 # CopyFromPreviousFrame ::: 1st replacement Clip V1 in clipclop args
    CN  = 2 # CopyFromNextFrame     ::: 2nd replacement Clip V2
    DS1 = 3 # DeSpot single spots   ::: 3rd replacement Clip V3
    DS2 = 4 # DeSpot double spots   ::: etc
    DS3 = 5 # DeSpot triple spots
    FV  = 6 # FlipVertical
    INV = 7 # Invert
"""

SCMD = """ # ClipClop Commands given in SCMD string [can supply in CMD file too], can use Nickname or replacement clip index to specify clip.
    CP   10     # Replace bad frame at 10 with frame before it [Maybe bad End Of Scene frame - glue @ Splice]
    CN   20     # Replace bad frame at 20 with frame after it [Maybe bad Start Of Scene frame]
    DS1  30     # Spot at 30
    DS2  40,-2  # Double Spot at 40 [-2 = 2 frames replaced]
    DS3  50,52  # Triple Spot at 50 [range 50->52 replaced]
    1    60     # CopyFromPreviousFrame frame 60, we used clip replacment index 1 [ie V1] instead of nickname CP.
    FV   70,75  # FlipVertical 70->75
    INV  80,0   # Invert 80 -> End Of Clip
"""

CMD = ""    # Not Used, Maybe eg CMD=".\ClipClopCommand.txt"

SHOW=True # Show ClipClop metrics

ClipClop(Last,  V1,V2,V3,V4,V5,V6,V7, scmd=SCMD, cmd=CMD, NickName=Nicks, show=SHOW)

You can define up to 255 replacement clips in ClipClop.

EDIT: There is a Donald Graft plugin called DeFlick, I think, maybe use before Spotless for B&W.
EDIT: Maybe forget DeFlick before spotless, it would likely spread spots over multiple frames making them harder to remove. [could try after spotless though]

External Filters:- http://avisynth.nl/index.php/External_filters
and Internal filters:- http://avisynth.nl/index.php/Internal_filters

[coolgit]

Regarding your pal hybrid script, I am getting no function McDeGrainSharp. I got it and created a McDeGrainSharp.avs file and put it in avisynth 32/64 and vdub 32 and not working.

[StainlessS]

I is guessin you is usin v2.6, avs 2.6 requires .avsi extension, avs+ requires *.avs or *.avsi
mobile in public house

[coolgit]

using avs+ 3.7

[kedautinh12]

Originally Posted by coolgit

using avs+ 3.7

You need use AVSMeter or Avisynth Info Tool to check your AVS plugins and scripts. After you share your log here
https://forum.doom9.org/showthread.php?t=173259

[coolgit]

Log file created with: AVSMeter 3.0.9.0 (x64)
Command line switches: -avsinfo

[OS/Hardware info]
Operating system: Windows 7 (x64) Service Pack 1.0 (Build 7601)

CPU: Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz / Coffee Lake (Core i7)
MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, FMA3, RDSEED, ADX, AVX, AVX2
6 physical cores / 12 logical cores


[Avisynth info]
VersionString: AviSynth+ 3.7.0 (r3382, 3.7, x86_64)
VersionNumber: 2.60
File / Product version: 3.7.0.0 / 3.7.0.0
Interface Version: 8
Multi-threading support: Yes
Avisynth.dll location: C:\Windows\System32\avisynth.dll
Avisynth.dll time stamp: 2021-01-11, 15:47:06 (UTC)
PluginDir2_5 (HKLM, x64): C:\Program Files (x86)\AviSynth\plugins64
PluginDir+ (HKLM, x64): C:\Program Files (x86)\AviSynth\plugins64+


[C++ 2.5 Plugins (64 Bit)] [Version, Time stamp]
C:\Program Files (x86)\AviSynth\plugins64+\Decomb.dll [n/a, 2013-12-01]

[C++ 2.6 Plugins (64 Bit)] [Version, Time stamp]
C:\Program Files (x86)\AviSynth\plugins64+\AutoAdjust.dll [2.6.0.0, 2016-01-05]
C:\Program Files (x86)\AviSynth\plugins64+\ClipClop_x64.dll [1.27.0.0, 2021-07-27]
C:\Program Files (x86)\AviSynth\plugins64+\ConvertStacked.dll [n/a, 2021-01-11]
C:\Program Files (x86)\AviSynth\plugins64+\DelogoHD.dll [1.0.0.0, 2019-12-09]
C:\Program Files (x86)\AviSynth\plugins64+\DePan.dll [2.13.1.6, 2020-05-22]
C:\Program Files (x86)\AviSynth\plugins64+\DePanEstimate.dll [2.10.0.4, 2020-05-22]
C:\Program Files (x86)\AviSynth\plugins64+\DeScratch64.dll [1.1.0.0, 2018-09-07]
C:\Program Files (x86)\AviSynth\plugins64+\DirectShowSource.dll [n/a, 2021-01-11]
C:\Program Files (x86)\AviSynth\plugins64+\ffms2.dll [n/a, 2020-08-22]
C:\Program Files (x86)\AviSynth\plugins64+\FrameSel_x64.dll [2.21.0.0, 2021-07-27]
C:\Program Files (x86)\AviSynth\plugins64+\ImageSeq.dll [n/a, 2021-01-11]
C:\Program Files (x86)\AviSynth\plugins64+\KNLMeansCL.dll [n/a, 2020-11-12]
C:\Program Files (x86)\AviSynth\plugins64+\LSMASHSource.dll [n/a, 2021-07-28]
C:\Program Files (x86)\AviSynth\plugins64+\MedianBlur2.dll [1.1.0.0, 2021-01-30]
C:\Program Files (x86)\AviSynth\plugins64+\mvtools2.dll [2.7.45.0, 2021-06-08]
C:\Program Files (x86)\AviSynth\plugins64+\neo-f3kdb.dll [1.0.0.0, 2021-07-05]
C:\Program Files (x86)\AviSynth\plugins64+\nnedi3.dll [0.9.4.59, 2021-07-19]
C:\Program Files (x86)\AviSynth\plugins64+\RemoveDirt.dll [0.9.3.0, 2021-02-23]
C:\Program Files (x86)\AviSynth\plugins64+\RoboCrop_x64.dll [1.13.0.0, 2020-02-07]
C:\Program Files (x86)\AviSynth\plugins64+\RT_Stats_x64.dll [2.0.13.0, 2020-12-29]
C:\Program Files (x86)\AviSynth\plugins64+\Shibatch.dll [n/a, 2021-01-11]
C:\Program Files (x86)\AviSynth\plugins64+\TDeint.dll [1.8.0.0, 2020-12-14]
C:\Program Files (x86)\AviSynth\plugins64+\TimeStretch.dll [n/a, 2021-01-11]
C:\Program Files (x86)\AviSynth\plugins64+\TIVTC.dll [1.0.26.0, 2021-02-22]
C:\Program Files (x86)\AviSynth\plugins64+\VDubFilter.dll [n/a, 2021-01-11]
C:\Program Files (x86)\AviSynth\plugins64+\yadifmod2.dll [0.2.7.0, 2021-02-07]

[Scripts (AVSI)] [Time stamp]
C:\Program Files (x86)\AviSynth\plugins64+\colors_rgb.avsi [2021-01-11]
C:\Program Files (x86)\AviSynth\plugins64+\FFMS2.avsi [2015-05-22]

[Uncategorized files] [Time stamp]
C:\Program Files (x86)\AviSynth\plugins64+\colors_rgb.txt [2021-01-11]
C:\Program Files (x86)\AviSynth\plugins64+\ffmsindex.exe [2020-08-22]
C:\Program Files (x86)\AviSynth\plugins64+\McDegrain.avs [2021-08-05]
C:\Program Files (x86)\AviSynth\plugins64+\McDegrainSharp.avs [2021-08-05]