Things missing in Vapoursynth,....

[Selur]

Here are a few things I miss in Vapoursynth:

• RemoveDirt port where RestoreMotionBlocks works (without this, a bunch of script using RemoveDirt can't really be ported); seems to work for some resolutions mods (https://forum.doom9.org/showthread.php?t=185121)
• DeSpot filter (lostfuncs DeSpot simple isn't the same and lacks tons of options)
• sRestore port as a filter (since the script doesn't work as intended, unless you limit the thread count of Vapoursynth to 1 )
• AnimeIVTC port
• ColorYUV, SmoothTweak, SmoothCurve, AutoAdjust, HDRAGC port
• amDCT port
• Waveform filter to see audio wave
• Exblend port
• An option to disable autoloading for a script.
• Waveform port
• TDecimate which works with mode=2 (https://github.com/dubhater/vapoursynth-tivtc/issues/4)
• InpaintDelogo port

Cu Selur

[ChaosKing]

Cdeblend suffers from the same problem as srestore (linear cache)

[Selur]

Added DeScratch which I really like.

[Myrsloik]

Originally Posted by Selur

Added DeScratch which I really like.

Is this the most recent version of the source code? Should be a quick port
http://www.avisynth.nl/index.php/DeScratch

[Selur]

I think so, at least that is the latest version I know of.
A port would be nice.

Cu Selur

[Myrsloik]

Originally Posted by Selur

I think so, at least that is the latest version I know of.
A port would be nice.

Cu Selur

Would you happen to have a small test clip and some reasonable settings so I can verify that my port works?

[Selur]

Not so small clip example: https://forum.videohelp.com/threads/...if-possible%29
usually, I takes multiple calls:

f = f.DeScratch(maxgap=5,minlen=30,maxangle=55)
f = f.DeScratch(maxgap=25,minlen=25,maxangle=30)

to remove static scratches, but it's really helpful with scratches in old captures.
(+ you often use it scene by scene)

Cu Selur

[Myrsloik]

Please test and report your findings before I make a proper release. See it as the one true successor fork since I support both avs and vs and cleaned up the code quite a bit.
https://github.com/vapoursynth/descr...ases/tag/Test1

[poisondeathray]

Thanks, DeScratch appears to work ok (same results as v1.1.0 avs version). Is it possible to support other pixel formats than YV12 ?

[Selur]

Will do some test later today and report back.

[Myrsloik]

Originally Posted by poisondeathray

Thanks, DeScratch appears to work ok (same results as v1.1.0 avs version). Is it possible to support other pixel formats than YV12 ?

Sure, YV16 and YV24 added and appear to work since the planes are separately processed anyway.

Higher bitdepths is probably just a waste of time anyway. It's also somewhat annoying since the code mixes up row size and width.

[Selur]

Works fine here too. YV16 and YV24 would be nice. I agree, high bit depth should not be really needed since I have never used this on anything but old tape scans or similar.
Thanks for porting this!

Cu Selur

[Myrsloik]

Originally Posted by Selur

Works fine here too. YV16 and YV24 would be nice. I agree, high bit depth should not be really needed since I have never used this on anything but old tape scans or similar.
Thanks for porting this!

Cu Selur

First and probably only release is up. Would be great if someone edits the avisynth wiki so more people can find it.

[Reel.Deel]

Originally Posted by Myrsloik

First and probably only release is up. Would be great if someone edits the avisynth wiki so more people can find it.

Will do. Thanks for the update!

[Myrsloik]

This is the most recent source and the correct despot version?
http://avisynth.nl/index.php/DeSpot

Looks like YV24 support and YV16 is easily doable as improvement (only has the ancient YUY2 planar hack and nobody likes that).

[Selur]

Yes, v3.6.3.1 is the latest version.

[Selur]

@myrsloik: seeing that you started to do a proper port of Despot over at https://github.com/vapoursynth/despot I just wanted to know if there is hope for a release?

[Myrsloik]

Originally Posted by Selur

@myrsloik: seeing that you started to do a proper port of Despot over at https://github.com/vapoursynth/despot I just wanted to know if there is hope for a release?

My time ran out before I could add VS support. At the moment it's just a cleaned up avs+ version if you bother to compile it.

The main problem is that the code uses convoluted ways to avoid memory allocation and is by modern standards quite insane. Except in some modes where it forgets all about it and allocates like crazy. Maybe I'll have time to poke it again in a few weeks. Code archeology at its finest...

[Selur]

Thanks for the info!

[juanitogan]

Originally Posted by Myrsloik

Please test and report your findings before I make a proper release. See it as the one true successor fork since I support both avs and vs and cleaned up the code quite a bit.
https://github.com/vapoursynth/descr...ases/tag/Test1

Has anyone completed filtering a full-length HD film with DeScratch V2.0 in VS?

I've tried several times with Hybrid and it keeps failing after a few minutes. Never on the same frame. Have tried two different films with the same results. The older AS version of this filter in Hybrid works fine on the same content.

To me, it looks like a memory leak. I start the job with about 5GB of mem full, out of 12GB. It creeps up to 12GB, bounces around up there for a few minutes, until, presumably, DeScratch steals it all and crashes. It encodes about 2-3 minutes of HD material before it quits. I can get it to go a bit longer if I turn off Hybrid's built-in feature and add DeScratch as a custom command with YUV422P8 color instead of YUV444P8. And another bit longer with YUV420P8.

Another observation is that this new VS version of DeScratch is better at avoiding false positives between the characters in overlay text (or the text itself), versus the AS version (with the same settings, of course). With the AS version, I have to set the minlen 2 or 3 times taller than the text (red text, btw). This version simply ignores the text regardless of how low I set minlen. I had a hunch this was due to YUV444P8 and, sure enough, when I set it to YUV420P8, the VS version runs just like the AS version on this front. Thus, it would be extra nice to run on YUV444P8, assuming that's not a glitch.