On Thu, Jan 16, 2014 at 5:52 AM, Vittorio Giovara <[email protected]> wrote: > > What is avisynth+? A brief description in the windows paragraph before > listing it here would be nice. >
The Doom9 thread is here: http://forum.doom9.org/showthread.php?t=168856 AviSynth+ is a fork of 2.6 that originated out of a disagreement in the Doom9 thread for alpha 4 (some of the content of which can be seen on the first page there since the thread was split). Basically, IanB, the single dev still working on AviSynth 2.6, didn't want to change the directory structure or integrate the patchset proposed by ultim because of what boils down to not wanting to change the dev environment, and because there was a misunderstanding due to version control (AviSynth uses CVS, the patchset actually originated under Git because it was tracked against the Github mirror that jeeb set up). The patchset (which was something like 56 patches) was intended to make the source more developer-friendly, move to modern compilers, and spur contributions and general refactoring. That was in September. By now, there have been more unique commits to github.com/AviSynth/AviSynthPlus than there have been to AviSynth's CVS repository since the early-mid part of 2008. In essence, it's pretty much the active development branch of AviSynth now. It does have cross-platform support in the long-term forecast, so it'll also immediately deprecate AvxSynth the second that actually happens. It's still too new to just say 'this is the only supported version', but it definitely is already preferable to 2.6. >> +For 64-bit builds of Libav on Windows, the only version that can be used >> +is AviSynth+, since classic AviSynth doesn't support 64-bit. > > I remember seeing 64bit avisynth builds, official for 2.5 and > unofficial for 2.6. Are you sure the 2.6 64bit builds do not work at all? > AviSynth64 (as well as AviSynth MT, more questionably) was never official, they were essentially single-issue forks of their own. Even at that, the 64-bit builds had a reputation of being pretty unstable - I wouldn't know personally, since I've never had access to a Win64 setup that I could have tested them on. But from what I've seen others say on Doom9 and the a-m-v.org forum, Avs64 was often more trouble than it was worth to get working correctly. AviSynth+'s support for 64-bit (multithreading will apparently hit the git repo this week) is a part of the refactoring effort, as was removing the SoftWire library and replacing all the inline asm with standard C/C++ versions and intrinsics (which, because the SoftWire and inline stuff was so bad, means that in many/most? cases it gets better performance than original AviSynth). That said, I'm not aware of a 64-bit build of 2.6 surfacing (a cursory Googling doesn't seem to turn up anything either). The ones by squid_80 and JoshyD were 2.5-based. Since Libav stops if 2.5 is detected and tells the user to upgrade, it won't work with Libav (FFmpeg still supports 2.5, and yes, it is possible to use the 64-bit builds of 2.5 with it). _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
