AviSynth+ thread Vol.2

[pinterf]

That's too old, see alsk the so-called mutex-crash, which I mentioned earlier, in 2024 the mutex ABI has been changed, but I expected it that the 14.38 was also crashing on that reason.
EDIT: my earlier finding on mutex crash incompatibility": machines with old redistibutable before 14.39.32551.0 would crash if VS is later than ~July 2024
Based on this: FranceBB had pre-14.39.32551 redist and when using 14.44 compiled avisynth dll --> crash (I bet it crashed on the infamous mutex lock).

[FranceBB]

yeah I saw the posts, but I thought that installing Windows6.1-KB2999226-x64.msu from the link you were suggesting was gonna be enough.

Originally Posted by pinterf

- Redistributable 14.44.35211 does work on Windows 7 if KB2999226 is installed:
https://support.microsoft.com/en-us/...5-287930f3560c

Unfortunately it wasn't. I'll try the AIO package from here https://github.com/abbodi1406/vcredist/releases on Windows Server 2008 R2 Standard x64 and see whether it actually updates the file in System32. If it does, I'll try again x64-win7-19.44.35221-17.14. In any case, x64-win7-19.38.33145-17.8 works even with an older version of the redistributable.


In the meantime, I've tested Avisynth_3.7.6_20260105_VS2026tst_r4430 on Windows XP Professional x86 and it works like a charm on the usual XP build.

[FranceBB]

Alright, so, take 2.
I've installed VisualCppRedist_AIO_x86_x64.exe which updated msvcp140.dll to 14.44.35211.0 on Windows Server 2008 R2.



I then tried Avisynth_3.7.6_20260105_VS2026tst_r4430 version x64-win7-19.44.35221-17.14

And sure enough this time it worked with this new version as well.

Log file created with: AVSMeter 3.0.9.0 (x64)
Command line switches: -Avsinfo -lf -log

[OS/Hardware info]
Operating system: Windows Server 2008 R2 (x64) Service Pack 1.0 (Build 7601)

CPU: Intel(R) Xeon(R) CPU X5570 @ 2.93GHz / Gainestown 8M (Xeon)
MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2
4 physical cores / 8 logical cores


[Avisynth info]
VersionString: AviSynth+ 3.7.5 (r4430, master, x86_64)
VersionNumber: 3.75
File / Product version: 3.7.5.0 / 3.7.5.0
Interface Version: 12
Multi-threading support: Yes
Avisynth.dll location: C:\windows\system32\avisynth.dll
Avisynth.dll time stamp: 2026-01-05, 12:26:24 (UTC)
PluginDir2_5 (HKLM, x64): C:\Program Files (x86)\AviSynth+\plugins64
PluginDir+ (HKLM, x64): C:\Program Files (x86)\AviSynth+\plugins64+

Originally Posted by pinterf

FranceBB had pre-14.39.32551 redist and when using 14.44 compiled avisynth dll --> crash (I bet it crashed on the infamous mutex lock).

Yep. Bingo. Now it works.

[pinterf]

FranceBB, thanks for testing it.

New build: Avisynth r4439
https://github.com/pinterf/AviSynthP...3.7.6pre-r4439

We have even more AVX512 resampler specializations, big thanks to DTL2020's innovation.

As usual, I include two main build types. Now the pack comes with a Win7 compatible build as well.

1.) XP builds (v141_xp toolset + special compile flags)
2.) modern (clang-cl - LLVM 20.1.8) well optimized builds. VS2026 v145 toolset
3.) a Windows 7 compatible - medium-modern build (x64 only) v143 toolset

Note for Windows 7 compatibility build:

- I used the usual VS2022 v143 toolset: 14.44.35221. (v143 is selectable from Visual Studio 2026 as well)
- Avisynth.dll requires an up-to-date Win7 compatible Visual C++ redistributable pack.
Pre-14.39 VC redistributable versions will crash with Access Violation ("mutex-lock" issue)
When in doubt which version you have, check your c:\windows\system32\msvcp140.dll properties.
Download 14.44.35221 from: https://github.com/abbodi1406/vcredi...es/tag/v0.92.0
- Redistributable 14.44.35211 does work on Windows 7 if KB2999226 is installed:
Get the update from:
https://support.microsoft.com/en-us/...5-287930f3560c

20260107 3.7.5.r4439 (pre 3.7.6)
--------------------------------
  * add AVX512 code path (tuning by DTL2020)
  
    - 32-bit float resamplers, verticals; horizontals up to kernel size 16.
    - 8-16-bit horizontal resamplers,

      - kernel size <= 4 and specific ratios; 300%+ !!
      - kernel sizes up to 8 and 16 and specific ratios.
    - 8-16-bit vertical resamplers

For online documentation, please check https://avisynthplus.readthedocs.io/en/latest/

Full change log:
https://avisynthplus.readthedocs.io/...gelist376.html

[FranceBB]

Originally Posted by pinterf

FranceBB, thanks for testing it.

No problem, it's literally the least I can do, master Ferenc.

Originally Posted by pinterf

New build: Avisynth r4439

1.) XP builds (v141_xp toolset + special compile flags)

Works on Windows XP Professional x86

Originally Posted by pinterf

3.) a Windows 7 compatible - medium-modern build (x64 only) v143 toolset

Works on Windows Server 2008 R2 Standard x64

[Emulgator]

jpsdr, many thanks ! Your builds saved the day for my Win7 rigs.

I've added Avs+ on my github with Windows 7 compatible builds.

The oldest Win7U64 i940XM 8GB from 2010:
Both your builds r4449 x86 and x64 run well, just a quick test. AvsPmod 2.7.9.5 with the christmas script.

Two newer Win7U64 i7-4960X 32GB from 2014 are in the dock under repair, to be tested later.

[manolito]

1.) XP builds (v141_xp toolset + special compile flags)
2.) modern (clang-cl - LLVM 20.1.8) well optimized builds. VS2026 v145 toolset
3.) a Windows 7 compatible - medium-modern build (x64 only) v143 toolset

Quick request for clarification:

I am under Win7 64, so far I use the latest stable version of AVS+ Avisynth 3.7.5 (20250420)
I only use the 32bit version of AVS+, I have no use for the 64bit version. This probably means that Option 3.) will not work for me, because I only use 32bit plagins. Is this assumption correct?


Cheers
manolto

[pinterf]

Originally Posted by manolito

1.) XP builds (v141_xp toolset + special compile flags)
2.) modern (clang-cl - LLVM 20.1.8) well optimized builds. VS2026 v145 toolset
3.) a Windows 7 compatible - medium-modern build (x64 only) v143 toolset

Quick request for clarification:

I am under Win7 64, so far I use the latest stable version of AVS+ Avisynth 3.7.5 (20250420)
I only use the 32bit version of AVS+, I have no use for the 64bit version. This probably means that Option 3.) will not work for me, because I only use 32bit plagins. Is this assumption correct?


Cheers
manolto

Omitting the win7 32-bit was just a time-saving option for me, since assembling such a release pack is ~3 hours, I was in short of time.

At least it turned out that someone is still using 32 bit. Next time, you can expect such a test build.

[jpsdr]

Originally Posted by Emulgator

jpsdr, many thanks ! Your builds saved the day for my Win7 rigs.

Nice it was usefull for someone.
As it takes hours for me to make all these builds, don't expect frequent updates...

[FranceBB]

Originally Posted by manolito

Is this assumption correct?

option 1 will work just fine as the XP x86 builds work on everything else as well, so Vista, 7, 8, 8.1 and 10 x86 will all happily run those.

[manolito]

I am under Win7 64, so far I use the latest stable version of AVS+ Avisynth 3.7.5 (20250420)

Thanks FranceBB, this makes it perfectly clear...

OTOH I am unsure why I should upgrade from version 3.7.5 at all. I will certainly not abandon Win7 64, so I wonder which real advantages the upcoming new version will offer under Win7 for the 32bit version of AVS+. Let's wait and see...


Cheers
manolito

[FranceBB]

Originally Posted by manolito

I wonder which real advantages the upcoming new version will offer

Well, the changelog is currently here https://avisynthplus.readthedocs.io/...gelist376.html

I still think you should keep it updated once it comes out as "Stable" and is released by Stephen and Master Ferenc as it's always a nice thing.

Sure, older systems and CPUs won't benefit from things like the AVX512 assembly speed bump for the resizers (and the same goes for other architectures like ARM which have their own intrinsics in NEON, DOTPROD and CPUF), but every system still benefits from the updated core and the improvements and fixes the come with it.

I'm talking about things like "add" and "subtract" in Overlay to support 32bit float, utf8 parameter for AddAutoLoadDir, AddAutoLoadDir, LoadPlugin, DumpFilterGraph, L2 cache size being displayed when using Info(), as well as a bunch of bug fixes like "reverse" properly handling 24bit audio or the one for Animate and 64bit double that caused StainlessS Christmas celebration to be ruined (I'm joking, I'm joking XD) and so on.

In other words, it's always a nice thing to keep the frameserver updated, but ultimately it's for you to decide, just look at the changelogs and see if there's something that makes you consider the release worth upgrading once the stable version is available.