let’s start a vote, should I rename the blog “TheFluff’s list of things you shouldn’t be doing”? yes/no/maybe
- Since the entire point of Avisynth is to load Avisynth plugins, and most Avisynth plugins sure as heck aren’t threadsafe, the efforts to try to make Avisynth-MT itself threadsafe are sort of meaningless. Not to mention they’ve failed spectacularly so far.
- Nobody wants to have anything to do with the 64-bit version (or even make a trivial 64-bit wrapper) despite lots of threads requiring hilarious amounts of RAM.
- Avisynth-MT uses Avisynth 2.5.6’s infamously memory leaking frame cache. Running out of memory is a Bad Thing, mmkay?
- Avisynth-MT doesn’t handle system exceptions because someone commented out the original Avisynth code that did that forever ago and never replaced it.
- In short, Avisynth-MT developers have no clue about what they’re doing.
Stop getting fooled by the ~blazing~ FPS numbers. An encode that crashes halfway through is effectively encoding at a negative FPS.
TL;DR: Pain is nature’s way of telling us “hey, stop fucking doing that, retard”. When nature does this, it usually has a good reason for doing so, and if you don’t listen, Bad Things will happen to you. Similarly, random crashes in a computer program are sorta your computer’s way of telling you “hey, stop fucking using that broken program, retard”.