Version() may not be correct

[TCmullet]

I've installed and have been using Avisynth+. But why doesn't version.avs show the "+"?

The jpg I attached shows the output of version() which reads:

AviSynth 2.60, build:Feb 20 2015 [03:16:45]
(c) 2000-2014 Ben Rudiak-Gould, et al.
http://www.avisynth.org

I've been running 32-bit Vdub 1.10.4 for years.

However, I just installed Vdub2 44282, and it's output is very different:

AviSynth+ 3.7.3 (r4003, 3.7,i386)
(c) 2000-2015 Ben Rudiak-Gould, et al.
http://www.avisynth.nl
(c) 2013-2023 AviSynth+ Project

If "version()" is supposed to read the avisynth version identifcation FROM THE COMPUTER, why two different versions of Virtualdub giving two totally different reports??? It's the same Avisynth.

[TCmullet]

In case anyone suspects I failed to install Avisynth+, here's my AVSMeter to show that I did:


D:\MyApplications\AVSMeter>avsmeter -avsinfo

AVSMeter 3.0.9.0 (x86), (c) Groucho2004, 2012-2021

VersionString: AviSynth+ 3.7.3 (r4003, 3.7, i386)
VersionNumber: 2.60
File / Product version: 3.7.3.0 / 3.7.3.0
Interface Version: 10
Multi-threading support: Yes
Avisynth.dll location: C:\WINDOWS\SysWOW64\avisynth.dll
Avisynth.dll time stamp: 2023-07-16, 04:00:38 (UTC)
PluginDir2_5 (HKLM, x86): C:\Program Files (x86)\AviSynth+\plugins
PluginDir+ (HKLM, x86): C:\Program Files (x86)\AviSynth+\plugins+


[C++ 2.5 Plugins (32 Bit)] [Version, Time stamp]
C:\Program Files (x86)\AviSynth+\plugins\avssr.dll [n/a, 2014-01-09]
C:\Program Files (x86)\AviSynth+\plugins\dgbob.dll [n/a, 2003-07-06]
C:\Program Files (x86)\AviSynth+\plugins\DGDecode.dll [1.5.8.0, 2015-12-26]
C:\Program Files (x86)\AviSynth+\plugins\NicAudio.dll [n/a, 2012-08-27]
C:\Program Files (x86)\AviSynth+\plugins\TIVTC.dll [1.0.5.0, 2017-12-18]

[C++ 2.6 Plugins (32 Bit)] [Version, Time stamp]
C:\Program Files (x86)\AviSynth+\plugins+\ConvertStacked.dll [n/a, 2023-07-16]
C:\Program Files (x86)\AviSynth+\plugins+\DirectShowSource.dll [n/a, 2023-07-16]
C:\Program Files (x86)\AviSynth+\plugins+\ImageSeq.dll [n/a, 2023-07-16]
C:\Program Files (x86)\AviSynth+\plugins+\Shibatch.dll [n/a, 2023-07-16]
C:\Program Files (x86)\AviSynth+\plugins+\TimeStretch.dll [n/a, 2023-07-16]
C:\Program Files (x86)\AviSynth+\plugins+\VDubFilter.dll [n/a, 2023-07-16]
C:\Program Files (x86)\AviSynth+\plugins\aWarpsharpMT.dll [2.1.9.0, 2023-11-19]
C:\Program Files (x86)\AviSynth+\plugins\DGDecodeNV.dll [0.0.0.2052, 2016-10-18]
C:\Program Files (x86)\AviSynth+\plugins\ffms2.dll [n/a, 2020-08-22]
C:\Program Files (x86)\AviSynth+\plugins\LSMASHSource.dll [1129.0.0.0, 2023-07-16]
C:\Program Files (x86)\AviSynth+\plugins\masktools2.dll [2.2.30.0, 2022-02-19]
C:\Program Files (x86)\AviSynth+\plugins\mvtools2.dll [2.7.45.0, 2021-06-08]
C:\Program Files (x86)\AviSynth+\plugins\Shader.dll [n/a, 2024-05-07]
C:\Program Files (x86)\AviSynth+\plugins\svpflow1.dll [4.0.0.132, 2016-12-21]
C:\Program Files (x86)\AviSynth+\plugins\svpflow2.dll [4.0.0.136, 2016-12-21]

[Scripts (AVSI)] [Time stamp]
C:\Program Files (x86)\AviSynth+\plugins\colors_rgb.avsi [2022-10-06]
C:\Program Files (x86)\AviSynth+\plugins\FFMS2.avsi [2015-05-22]
C:\Program Files (x86)\AviSynth+\plugins\GameDropFixV5.avsi [2017-10-04]
C:\Program Files (x86)\AviSynth+\plugins\InterFrame2.avsi [2015-07-22]
C:\Program Files (x86)\AviSynth+\plugins\LimitedSharpenFaster.avsi [2017-01-03]
C:\Program Files (x86)\AviSynth+\plugins\Shader.avsi [2024-05-07]
C:\Program Files (x86)\AviSynth+\plugins\TCS-Video-Functions.avsi [2024-04-27]

[Uncategorized files] [Time stamp]
C:\Program Files (x86)\AviSynth+\plugins\AiUpscale - Copy.xxxavsi [2024-05-07]
C:\Program Files (x86)\AviSynth+\plugins\AiUpscale.xxxxavsi [2024-05-08]
C:\Program Files (x86)\AviSynth+\plugins\colors_rgb.txt [2022-10-06]
C:\Program Files (x86)\AviSynth+\plugins\ffms2.lib [2020-08-22]
C:\Program Files (x86)\AviSynth+\plugins\ffmsindex.exe [2020-08-22]

D:\MyApplications\AVSMeter>

[poisondeathray]

You have a "rogue" avisynth.dll in the search path

eg. I can reproduce that observed behaviour if I copy an old classic 2.6 avisynth.dll in the vdub classic (1.10.4 x86) folder . If I remove that .dll, it reads the installed avisynth version

[TCmullet]

You have a "rogue" avisynth.dll in the search path

eg. I can reproduce that observed behaviour if I copy an old classic 2.6 avisynth.dll in the vdub classic (1.10.4 x86) folder . If I remove that .dll, it reads the installed avisynth version
Thanks for saying that. I suspected something like that myself. But an Agent Ransack run shows I only have it in syswow64 and system32. Right-click properties and each shows it's +3.7.3.

I even just now looked in both for the case where I might have renamed it to Xavisynth.dll, but nothing in either place. Any ideas how a rogue copy could be hiding somewhere??

ALSO, why would Vdub 1.10.4 32b find the rogue one, yet Vdub2 (most recent) finds the +?

[poisondeathray]

Any ideas how a rogue copy could be hiding somewhere??


No, but it's the likely explanation


ALSO, why would Vdub 1.10.4 32b find the rogue one, yet Vdub2 (most recent) finds the +?
In my example, it was in the direct search path of vdub classic, but not vdub2 . vdub2 x86 does not parse the vdub classic directory , only it's own directory before other paths

Check each directory in your setup PATH in the system properties, environment variables

[TCmullet]

You forgot. I used Agent Ransack to search for the name (or wildcard) THROUGHOUT the drive. If one is out there, AR would find it, assuming I spelled the name or the wildcard correctly.

[poisondeathray]

As a workaround if you or Agent Ransack can't find it - if you place a new avisynth.dll into the vdub classic folder, it should take precendence over the the "rogue" 2.6 avisynth.dll , whereever it might be.

Other ways you can test avs x86/x64 are mpchc x86/x64 , and avspmod x86/x64 - In theory you should get the same results as mpchc x86 and avspmod x86 in terms of version() as vdub x86 ; that is unless there is a rogue avisynth.dll x86 somewhere in their paths that you or Agent Ransack couldn't find

[TCmullet]

I FOUND it! It wasn't on C: drive. On a whim, I ran Ransack on D:. It found THIS:
D:\MyApplications\VirtualDub\1.10.4\UnzipArea\avisynth.dll

This is where I might have copied it YEARS ago! (9 to be exact.) It makes sense that Vdub will look FIRST in the folder where itself is! Upon deleting it, Vdub 1.10.4 worked with AiUpscale (and any script) just fine, as Vdub no longer saw that rogue 2.6 Avisynth, but instead used the correct one, which is Avisynth+.

[guest]

I FOUND it! It wasn't on C: drive. On a whim, I ran Ransack on D:. It found THIS:
D:\MyApplications\VirtualDub\1.10.4\UnzipArea\avisynth.dll

This is where I might have copied it YEARS ago! (9 to be exact.) It makes sense that Vdub will look FIRST in the folder where itself is! Upon deleting it, Vdub 1.10.4 worked with AiUpscale (and any script) just fine, as Vdub no longer saw that rogue 2.6 Avisynth, but instead used the correct one, which is Avisynth+.

And now you should go here, and get the latest build...

https://gitlab.com/uvz/AviSynthPlus-Builds