Why? Basically, VapourSynth scripts use Python, and Python is case-sensitive. Also, you'll need to pay attention to the documentation for the various options, as they sometimes use different capitalization than on AVISynth. There, you're more likely to be able to squeeze in 3 passes, but it'll be excruciatingly slow if you do that, and can end up overprocessing the image. Yes, SMDegrain is available in 64-bit for VapourSynth (via havsfunc, which also contains a port of QTGMC).You can do multiple passes, but since SMDegrain is 32-bit only, you're realistically limited to 2 passes without render freezes/crashes due to memory issues.Either use it after QTGMC, or use it before and accept that the motion may not always look quite right. You could use SeparateFields() first and AssumeFieldBased() plus Weave() after to try to preserve the interlacing while reducing the amount of time it takes to denoise, but in my experience, that makes the processing look crappier/lower resolution. If you use the interlaced option it'll distort, so don't do that.
However, you should know some things about the Kitchen Sink method: Personally, I wish I could go 100% 64-bit at this point, but there's still a few important 32-bit AVISynth plugins that I need to use, So until those either get updated or become obsolete, that's going to be the situation. Going forward, I'm going to recommend binaries from the official FFMPEG Windows binary maintainers for 64-bit, and building from source for 32-bit.
AVISYNTH DENOISE UPDATE
It also means that I'm probably going to have to go back and update several of my tutorials, which I don't have a lot of time to do these days. It'll mean a little extra complexity, but gains the benefit of being able to control what's compiled into FFMPEG. Since everything involved with MABS is open source and well tested, I'm going to be using this solution for 32-bit from now on unless it absolutely breaks down on me. In particular, commenters there suggest using a set of scripts called media-autobuild_suite. As this thread on Doom9 suggests, the latter seems to be the more popular choice:
AVISYNTH DENOISE CODE
This leaves those of us who rely on FFMPEG for AVISynth processing with a choice: trust less popular/probably not vetted sources for new 32-bit versions of FFMPEG, or build the source code ourselves.
AVISYNTH DENOISE 32 BIT
Two other sites have stepped up to become the official FFMPEG Windows binary maintainers, but neither of them builds 32 bit versions. As of the 18th of this month, Zeranoe, the best source for Windows binaries of FFMPEG, has shut down.
0 kommentar(er)
