Avisynth Plugins Pack Download
Pa Blood
Loads so-called AviSynth C-plugins. C-plugins are created in pure C (unlike most Avisynth plugins, which are created with MS C++), use a special C API, and must be loaded with LoadCPlugin.
It is possible to put all plugins and script files with user-defined functions or (global) variables in an autoload directory, from which all files with the extension .AVSI and .DLL are loaded at startup, then unloaded and reloaded dynamically as the script needs them.
A problem that may arise when multiple plugins have functions with the same name. You won't know which function will be called in your script, as this will depend on loading order. To call a particular function in this situation, AviSynth's DLLName_function() feature automatically creates prefix aliases; so for example, foo.dll's bar() function may be called as foo_bar(). This works both for auto-loaded plugins and for plugins loaded with LoadPlugin.
Starting from 5 August 2007 the documentation on this site (avisynth.org) is released under the CreativeCommons Attribution-ShareAlike 3.0 License (abbreviated by "CC BY-SA 3.0", see also full license terms). More information can be found here.
Technically, AviSynth constructs a filter graph (like Microsoft GraphEdit but with added capabilities),[4] controlled by scripts written in the AviSynth scripting language. Its functionality can be extended through the use of third-party filters known as plugins. An external plugin list is maintained at AviSynth Filter Collection.
Apologies for the late reply, and thanks for the shout out.
Basically, the 64 bit version is more stable and faster in most cases, but has less support for legacy plugins. I really hope that most of the major plugins get ported over to 64-bit in the near future, because I think it this point there would be very few systems that require it.
QTGMC has its issues, in particular when you're dealing with a really grainy image. If there were a better solution (ideally open-source) out there that didn't cost an obscenely large amount of money, I would promote and use it.
Running with your comment about FrameRateConverter: "32-bit version was exponentially slower than the 64-bit version", I installed Avisynth+ 3.6.1 and replaced Avisynth 2.6 32bit. The documentation on the web is poor. Nowhere does it say you need to run 64bit Virtualdub2 to use 64bit plugins in Avisynth+. It took several hours to figure that out. If Avisynth is presenting a virtual avi file via the avs script, why would it matter if the calling app is 32bit or 64bit?
The 1920x1080p video I'm working on, I'm trying to double the framerate. Only the "slowest" preset gives acceptable results (no blocking in video). I changed the script from single threaded to 4 threads (quad core Xeon CPU). I'm getting 1.06 sec/frame with all plugins 64bit. With everything 32bit, I was getting 0.96 sec/frame. That is not much difference, certainly not exponential. Once it's done (3 days from now), I'm uninstalling Avisynth+ and reinstalling Avisynth 2.6 32bit.
I'm also testing Svpflow on the same video to see how it compares. Svpflow is what Interframe uses. It's running at 2.5FPS on a different PC that has a GTX1080Ti.
To christina:
About QTGMC- used correctly, it dramatically improves the amount of detail in interlaced video, by properly (bobbing and motion compensation) changing it to progressive. Some videos have information in the double frames too. To determine if you want to keep or delete them, you have to step through the processed video frame by frame to see if they're duplicates or not.
IMO, live footage generally looks best with a high frame rate. And movies do not (IMO). I doubled the frame rate on one movie (with FRC) and didn't like the soap opera effect at all. You can control what to do with the extra frames. If you don't like them, add a SelectEven() after the QTGMC line (or use fpsdivisor=2). That will delete the double frames.
Here's what I typically use in QTGMC:
QTGMC( Preset="Slow" )
If noisy:
QTGMC( Preset="Slow", NoisePreset="Slower" )
If later feeding to Video Enhance AI for upscaling, you typically don't want to do much denoising:
QTGMC( Preset="Fast", TR0=1 )
Brandon,
I think that your settings must have a different bottleneck than the ones that I was using, because I can assure you that there was a *dramatic* difference between 32-bit and 64-bit renders in my case. My guess is that the "slowest" preset is the cause, but I'd have to test to be sure.
I agree that documentation for AVISynth is poor for new users (and even professionals) at this point, which is a big reason why I started making these tutorials. I'm not a programmer, but I assume that there's something about the instructions used in AVISynth's design that requires everything to be 64-bit all throughout the chain.
As to the 32-bit vs. 64-bit debate, at this point I've essentially switched over to using only 64-bit plugins whenever possible due to memory issues. There are still a few filters that haven't transitioned yet, but they're getting less and less as time goes on.
Regardless, thanks for the info about AI upscaling. I need to look into that at some point.
AviSynth+ is a fork of the well-known frameserver, but with community contributions that avoided mainline inclusion until now. In the hope of modernizing AviSynth to meet present day needs and expectations, the project encourages everybody to help reach our goals: add long-sought features, energize the community, and improve developer and user friendliness. AviSynth+ is fully compatible with plugins and scripts written for AviSynth.
df19127ead