AviSynth+ thread Vol.2

[StainlessS]

Lovely, tanx P

[TR-7970X]

Surely it must be nearly time for 3.7.4....

[Emulgator]

Woohoo ! Donation on the way.
https://forum.doom9.org/showthread.p...28#post2014728
Still via this ?
https://buymeacoffee.com/pinterf
Or if paypal, PM me.

[pinterf]

Originally Posted by Emulgator

Woohoo ! Donation on the way.
https://forum.doom9.org/showthread.p...28#post2014728
Still via this ?
https://buymeacoffee.com/pinterf
Or if paypal, PM me.

Thanks , I tried to hide it well.

[real.finder]

Originally Posted by pinterf

Freshly built v4193.

- 32 and 64-bit XP compatible versions
- 64 bit Intel ICX compiled version (only Avisynth.dll, plugins were just copied)
May require Intel C++ 2025 redistributable: https://www.intel.com/content/www/us...y-version.html

Download Avisynth+ 3.7.3 r4193 test:
https://github.com/pinterf/AviSynthP...ag/v3.7.3.4193

Changes since official 3.7.3
https://avisynthplus.readthedocs.io/...gelist374.html
and
https://avisynthplus.readthedocs.io/...-v11-whats-new
and millions of updated documentation pages.

I did try it with last avspmod update and it work fine so far (its first time I did try the 64bit test update)

[tormento]

Originally Posted by pinterf

64 bit Intel ICX compiled version

Be my Valentine.

[FranceBB]

Who needs chocolate when we have a new Avisynth build to test!

[gispos]

Originally Posted by pinterf

Freshly built v4193.

- 32 and 64-bit XP compatible versions
- 64 bit Intel ICX compiled version (only Avisynth.dll, plugins were just copied)
May require Intel C++ 2025 redistributable: https://www.intel.com/content/www/us...y-version.html
.

AvsPmod runs with the Intel ICX build without problems, but I can't open a script with any other program.

Do I have to install the runtimes ?
Is the Intel build better (faster) on an Intel CPU ?

[tormento]

Originally Posted by gispos

AvsPmod runs with the Intel ICX build without problems, but I can't open a script with any other program.

Yes you have to. Read pinterf release post again.

I am using ICX build with AvsPmod with no problems here.

[tormento]

Originally Posted by FranceBB

Who needs chocolate when we have a new Avisynth build to test!

[pinterf]

Originally Posted by gispos

AvsPmod runs with the Intel ICX build without problems, but I can't open a script with any other program.

Do I have to install the runtimes ?
Is the Intel build better (faster) on an Intel CPU ?

Runtimes are probably needed, but I cannot check since I already have them on my machine because of the tests. The Intel build should be quicker. In this case, the XP builds are using the Visual Studio 2017 compiler, so they probably lack all the 2019 and 2022 Microsoft compiler optimizations. Even if the Intel build were equal to an MSVC 2022 build, the XP builds using 2017 technology are probably slower. However, this may be an urban legend. I guess, the actual speed gain is negligible unless you do synthetic tests using only internal Avisynth functions without using external scripts.

[TR-7970X]

Originally Posted by pinterf

Runtimes are probably needed, but I cannot check since I already have them on my machine because of the tests. The Intel build should be quicker. In this case, the XP builds are using the Visual Studio 2017 compiler, so they probably lack all the 2019 and 2022 Microsoft compiler optimizations. Even if the Intel build were equal to an MSVC 2022 build, the XP builds using 2017 technology are probably slower. However, this may be an urban legend. I guess, the actual speed gain is negligible unless you do synthetic tests using only internal Avisynth functions without using external scripts.

Possibly stupid question....

Why XP builds ?

What build should I use for Ryzen CPU's, using W11 Pro ?

[FranceBB]

Originally Posted by TR-7970X

Why XP builds ?

What build should I use for Ryzen CPU's, using W11 Pro ?

it's just a term to say that they were compiled using v141_xp which is the Microsoft compiler, MSVC. They run on all versions of Windows from Windows XP all the way up to Windows 11. You're gonna be fine.

As a bit of history, Avisynth has been supporting Windows 98SE and Windows 2000 since its inception on May 19th, 2000. The last Avisynth version, 2.6.1, from 2016, still supported them. When Avisynth+ arrived it brought plenty new things like high bit depth planar support (before we only had stacked and interleaved) and it was a major upgrade from the classic codebase. Support for Windows 98SE and Windows 2000 was dropped and the minimum requirement was bumped up to Windows XP which is still the case right now.

[TR-7970X]

Originally Posted by FranceBB

it's just a term to say that they were compiled using v141_xp which is the Microsoft compiler, MSVC. They run on all versions of Windows from Windows XP all the way up to Windows 11. You're gonna be fine.

As a bit of history, Avisynth kept supporting Windows 98SE and Windows 2000 since its Inception in April 2000 without dropping it. The last Avisynth version, 2.6.1, from 2016, still supported them. When Avisynth+ arrived it brought plenty new things like high bit depth planar support (before we only had stacked and interleaved) and it was a major upgrade from the classic codebase. Support for Windows 98SE and Windows 2000 was dropped and the minimum requirement was bumped up to Windows XP which is still the case right now.

Thanks for that, but to be pedantic, would the Intel build be suitable for Ryzen's, as it seems they might be optimised for Intel CPU's ?

[FranceBB]

Originally Posted by TR-7970X

Thanks for that, but to be pedantic, would the Intel build be suitable for Ryzen's, as it seems they might be optimised for Intel CPU's ?

The intel builds are created with ICC, the Intel compiler that used to be shipped with Intel Parallel Studio. They're gonna work on the Ryzen as well, but they were originally optimized with Intel Xeon in mind. As for the speed compared to MSVC, they're probably faster even if they're being used on an AMD CPU, but I don't know for sure. You should really try and test yourself with AVSMeter. I only really have an Intel i7 at home and several Intel Xeon at work, so I can't test it for you.

Full disclosure: I've been an AMD fanboy since birth, I owned plenty of CPUs the likes of AMD Athlon 1600, AMD Athlon 3200, AMD Athlon 3800, those were great monocore CPUs. Unfortunately, when multi core were introduced, I had one heartbreak after another, starting with the AMD Athlon 64 X2 but the one that made me draw the line was when my AMD Phoenom II X6 1100T, a 6c/6th at 3.3GHz (with boost to 3.7GHz) was being beaten by 4c/8th Intel i7 and was struggling even against 4c/4th Intel i5 of the time. Three years later, in 2013, I moved to Intel and I've never looked back.

[pinterf]

Originally Posted by TR-7970X

Thanks for that, but to be pedantic, would the Intel build be suitable for Ryzen's, as it seems they might be optimised for Intel CPU's ?

Suitable.

The optimizations applied in our builds are generic "optimize for speed" settings, making them suitable for any processor architecture. It's a one-size-fits-all approach. Even Intel processor generations vary, so if someone wants a finely tuned version for their specific processor type, they would need to do it themselves.

Most of the internal optimizations in Avisynth are handcrafted for SSE2, SSSE3, SSE4.1, AVX2, etc. While not all are implemented, SSE2 and AVX2 are generally covered. Only a few areas have versions written solely in C. Compilers can further optimize our already SIMD-optimized versions, which is where different compilers like Intel C++ Compiler, LLVM, GCC, and MSVC can excel or fall short.

In general, they all do excellent jobs.

[TR-7970X]

Originally Posted by FranceBB

The intel builds are created with ICC, the Intel compiler that used to be shipped with Intel Parallel Studio. They're gonna work on the Ryzen as well, but they were originally optimized with Intel Xeon in mind. As for the speed compared to MSVC, they're probably faster even if they're being used on an AMD CPU, but I don't know for sure. You should really try and test yourself with AVSMeter. I only really have an Intel i7 at home and several Intel Xeon at work, so I can't test it for you.

Full disclosure: I've been an AMD fanboy since birth, I owned plenty of CPUs the likes of AMD Athlon 1600, AMD Athlon 3200, AMD Athlon 3800, those were great monocore CPUs. Unfortunately, when multi core were introduced, I had one heartbreak after another, starting with the AMD Athlon 64 X2 but the one that made me draw the line was when my AMD Phoenom II X6 1100T, a 6c/6th at 3.3GHz (with boost to 3.7GHz) was being beaten by 4c/8th Intel i7 and was struggling even against 4c/4th Intel i5 of the time. Three years later, in 2013, I moved to Intel and I've never looked back.

Nice, thanks again.

I have a majority of Ryzen's, but I do have a 13900KF, which is only a little "slower" than my 7950X.

I recently built a 32C Thread Ripper system, but haven't really done anything with it yet.

[TR-7970X]

Originally Posted by pinterf

Suitable.

The optimizations applied in our builds are generic "optimize for speed" settings, making them suitable for any processor architecture. It's a one-size-fits-all approach. Even Intel processor generations vary, so if someone wants a finely tuned version for their specific processor type, they would need to do it themselves.

Most of the internal optimizations in Avisynth are handcrafted for SSE2, SSSE3, SSE4.1, AVX2, etc. While not all are implemented, SSE2 and AVX2 are generally covered. Only a few areas have versions written solely in C. Compilers can further optimize our already SIMD-optimized versions, which is where different compilers like Intel C++ Compiler, LLVM, GCC, and MSVC can excel or fall short.

In general, they all do excellent jobs.

[LeXXuz]

I just updated AVS+ from an older build, 4066 IIRC, to the latest version.

Now I get an error in of my scripts saying "There is no function named 'ConvertToDoubleWidth' ".

Would appreciate some help on how to fix this.

[pinterf]

Originally Posted by LeXXuz

I just updated AVS+ from an older build, 4066 IIRC, to the latest version.

Now I get an error in of my scripts saying "There is no function named 'ConvertToDoubleWidth' ".

Would appreciate some help on how to fix this.

There must be a ConvertStacked.DLL in your Program Files (x86)/Avisynth+/plugins64+ (or plugins+ on 32-bit) folder