Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion.

Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules.

 

Go Back   Doom9's Forum > Capturing and Editing Video > Avisynth Development

Closed Thread
 
Thread Tools Search this Thread Display Modes
Old 30th July 2016, 09:08   #2221  |  Link
thescrapyard
Registered User
 
thescrapyard's Avatar
 
Join Date: Feb 2008
Posts: 59
Quote:
Originally Posted by thescrapyard View Post
I use AVStoDVD that won't run correctly unless it detects AviSynth 2.6.x.x

If I install AviSynth, then install the latest release of AviSynth+ it fails complaining that AviSynth 2.6.x.x is not installed BUT if I install the first release of AviSynth+ its fine

If I install the latest release of AviSynth+ (r2076) by copying over the binaries overwriting the original avisynth.dll it once again refuses to run due to incorrect versions


The version is being report as avisynth.dll 0.1.0, so I'm assuming its now to match the new releases of avisynth+ but anything that specifically looks for the avisynth.dll 2.6.x.x. is going to fail

Installed avisynth+ again, using the latest package installer for r2085, AVStoDVD still insists its version 0.1.0 and won't run the avisynth code as its looking for version 2.6.0 and above

I've directly edited the fileversion using FVIE I found trying to find a way to change just the version numbers

http://www.carifred.com/fvie/

All I changed was the version numbers in the avisynth.dll to show 2.6.0.0 and saved the modified .dll and this works, not ideal but now AVStoDVD is accepting the avisynth.dll as a legitimate version
thescrapyard is offline  
Old 30th July 2016, 09:42   #2222  |  Link
LigH
German doom9/Gleitz SuMo
 
LigH's Avatar
 
Join Date: Oct 2001
Location: Germany, rural Altmark
Posts: 6,753
The "DLL version" is an attribute in the "manifest" addendum (IIRC), read by the operating system.

But the "AviSynth version" will probably rather be the return value of an API function; this you can't patch with a PE patcher. I wonder if AviSynth+ would need an override feature to camouflage its own version and pretend a compatible one.
__________________

New German Gleitz board
MediaFire: x264 | x265 | VPx | AOM | Xvid
LigH is online now  
Old 30th July 2016, 10:03   #2223  |  Link
MysteryX
Soul Architect
 
MysteryX's Avatar
 
Join Date: Apr 2014
Posts: 2,559
Quote:
Originally Posted by thescrapyard View Post
All I changed was the version numbers in the avisynth.dll to show 2.6.0.0 and saved the modified .dll and this works, not ideal but now AVStoDVD is accepting the avisynth.dll as a legitimate version
Again, I was right
MysteryX is offline  
Old 30th July 2016, 10:10   #2224  |  Link
LigH
German doom9/Gleitz SuMo
 
LigH's Avatar
 
Join Date: Oct 2001
Location: Germany, rural Altmark
Posts: 6,753
Oh, then I misread this post, sorry.
__________________

New German Gleitz board
MediaFire: x264 | x265 | VPx | AOM | Xvid
LigH is online now  
Old 30th July 2016, 10:13   #2225  |  Link
Groucho2004
 
Join Date: Mar 2006
Location: Barcelona
Posts: 5,034
Quote:
Originally Posted by LigH View Post
The "DLL version" is an attribute in the "manifest" addendum (IIRC), read by the operating system.

But the "AviSynth version" will probably rather be the return value of an API function; this you can't patch with a PE patcher. I wonder if AviSynth+ would need an override feature to camouflage its own version and pretend a compatible one.
In case of AVS+, the FILEVERSION/PRODUCTVERSION (which are read by AVS2DVD) come from "version.h.in" (-> avisynth.rc -> avisynth.res -> link with avisynth.dll).

The Avisynth version string is indeed exported by IScriptEnvironment() ("VersionString").
__________________
Groucho's Avisynth Stuff
Groucho2004 is offline  
Old 30th July 2016, 10:18   #2226  |  Link
Groucho2004
 
Join Date: Mar 2006
Location: Barcelona
Posts: 5,034
Quote:
Originally Posted by thescrapyard View Post
All I changed was the version numbers in the avisynth.dll to show 2.6.0.0 and saved the modified .dll and this works, not ideal but now AVStoDVD is accepting the avisynth.dll as a legitimate version
I'm glad it worked for you. Still, hacking the version info this way is generally a bad idea. There may be some scenarios where it will crash since the 2.6 and AVS+ APIs are not the same.
So, do it at your own risk and don't blame the developers if something goes wrong.
__________________
Groucho's Avisynth Stuff
Groucho2004 is offline  
Old 30th July 2016, 10:26   #2227  |  Link
Groucho2004
 
Join Date: Mar 2006
Location: Barcelona
Posts: 5,034
Quote:
Originally Posted by MysteryX View Post
Again, I was right
Yes, you were right. Giving terrible hacking advice is a great idea.
__________________
Groucho's Avisynth Stuff

Last edited by Groucho2004; 30th July 2016 at 13:01.
Groucho2004 is offline  
Old 30th July 2016, 10:58   #2228  |  Link
ryrynz
Registered User
 
ryrynz's Avatar
 
Join Date: Mar 2009
Posts: 3,646
Oi.. ಠ_ಠ
ryrynz is offline  
Old 30th July 2016, 15:33   #2229  |  Link
MysteryX
Soul Architect
 
MysteryX's Avatar
 
Join Date: Apr 2014
Posts: 2,559
Quote:
Originally Posted by Groucho2004 View Post
I'm glad it worked for you. Still, hacking the version info this way is generally a bad idea. There may be some scenarios where it will crash since the 2.6 and AVS+ APIs are not the same.
So, do it at your own risk and don't blame the developers if something goes wrong.
AviSynth+ is designed to be compatible with AviSynth 2.6, that's its principal selling point.

Quote:
Originally Posted by Groucho2004 View Post
Yes, you were right. Giving terrible hacking advice is a great idea.
A better idea is for the software developer to update its software, and until that's done, some temporary "hack" has to be applied. Not ideal, but it's just temporary. The idea is to get it working for now. It needs to be hacked some way or the other anyway.

Do you realize that for almost everything you insulted me on, it turns out that what you said was false and I was right?

You did give me great answers and feedback to various questions too, so I thank you for that. You make great contributions. Just a little bit of respect would be appreciated.

Last edited by MysteryX; 30th July 2016 at 15:36.
MysteryX is offline  
Old 30th July 2016, 16:52   #2230  |  Link
qyot27
...?
 
qyot27's Avatar
 
Join Date: Nov 2005
Location: Florida
Posts: 1,419
Except that AVStoDVD has no problems using AviSynth+. thescrapyard isn't complaining about a fatal error, it's just a warning. MrC told them the exact same thing:
Quote:
@thescrapyard

wait, if the AviSynth release check routine reports "0.1.0", then A2D will give you just a warning. Just ignore the warning and go ahead. Instead there is a show stop when AviSynth.dll is not found from the path taken from "HKEY_LOCAL_MACHINE\SOFTWARE\AviSynth" registy key.

Which is your case?
If it's a fatal error, then it's not the version check doing it. There's something else wrong.


And I also just independently verified this with AVStoDVD 2.8.4. It has no problem:
Code:
<7/30/2016 11:41:20 AM>
START PROCESS
<>

<7/30/2016 11:41:20 AM>
PROJECT SETTINGS

DVD Video Standard: NTSC
DVD Titles number: 1
DVD Size: 159/4450 MB (4%)
DVD Output Setup: DVD Folder
DVD Label: DVD
DVD Menu: No Menu
Output Folder: C:\Users\Stephen\Documents
Delete Temp Assets Files: Yes
Delete Temp Working Files: Yes
Edit Command Parameters: No
Post Process Task: Show Progress Status window

PREFERENCES

MultiThread: 1
AVS Video Source Filter: A2DSource
AVS Audio Source Filter: A2DSource
AVS UpSize/DownSize Filter: Lanczos4Resize/Spline16Resize
Frame Adjust Strategy: 0
FPS Hard Conversion: 0
PAL SpeedUp: 0
NTSC SlowDown: 0
Video Resolution: 0
Video Encoder: 0
Video BitRate Min: 2500
Video BitRate Max: 8500
Keep DVD Compliant Video: 1
AC3 Audio Encoder: 0
Force FFmpeg for Long Audio: 1
DVD Audio Format: 0
DVD Audio BitRate: 192
Keep DVD Compliant Audio: 1
Normalize Audio: 0
Auto Delay Audio: 1
DVD Audio Language (Primary): EN - English
DVD Audio Language (Secondary): EN - English
DVD Subs Language (Primary): EN - English
DVD Subs Language (Secondary): EN - English
DVD Subs Font: Tahoma 16pt (255,255,255)
Chapters Interval: 5
Use Source Chapters: 1
DVD Burning Drive: 
DVD Burning Speed: 4x
Auto Erase DVD RW: 1
Execute with Elevated Privileges: 0
Unload ActiveMovie Library: 1
Adjust DirectShow Filters at runtime: 1
Save General Settings: 0

SYSTEM INFO

Processor Name: Intel(R) Atom(TM) CPU  Z3735F @ 1.33GHz
Operating System: Windows 10 (10.0.10586) 32 bit
User has Admin Rights: YES
Running with Elevated Privileges: NO (3)
Available Output Disc Space: 4 GB
AviSynth is installed: YES (release 0.1.0)
LAV Filters is installed: YES (release 0.68.1)
ffdshow is installed: YES (release 1.3.4515)

CODECS REPORT

H.264/AVC: Enhanced Video Renderer {FA10746C-9B63-4B6C-BC49-FC300EA5F256}
Xvid: Enhanced Video Renderer {FA10746C-9B63-4B6C-BC49-FC300EA5F256}
DivX 4/5/6: Enhanced Video Renderer {FA10746C-9B63-4B6C-BC49-FC300EA5F256}
Other MPG4: Enhanced Video Renderer {FA10746C-9B63-4B6C-BC49-FC300EA5F256}
DV: Enhanced Video Renderer {FA10746C-9B63-4B6C-BC49-FC300EA5F256}
MPEG1: Enhanced Video Renderer {FA10746C-9B63-4B6C-BC49-FC300EA5F256}
MPEG2: Enhanced Video Renderer {FA10746C-9B63-4B6C-BC49-FC300EA5F256}
MP2: Microsoft DTV-DVD Audio Decoder {E1F1A0B8-BEEE-490D-BA7C-066C40B5E2B9}
MP3: MP3 Decoder DMO {BBEEA841-0A63-4F52-A7AB-A9B3A84ED38A}
AAC: Microsoft DTV-DVD Audio Decoder {E1F1A0B8-BEEE-490D-BA7C-066C40B5E2B9}
AC3: No Preferred Filter set

<>

<7/30/2016 11:41:20 AM>
TITLE 1 SOURCE FILES
Video: D:\test.avs
Info: AviSynth - 0 kbps - 1920x816 - DAR 2.353 - 23.976 fps (CFR) - 2:31 minutes - 3630 frames
Audio 1: D:\test.avs
Info: AviSynth - 0 kbps - CBR - 2 ch - 44100 Hz - 16 bit - 2:31 minutes (0 ms delay)
[AVSMeter.exe]
<>

<7/30/2016 11:41:20 AM>
AVISYNTH SCRIPT
Video = Import("D:\test.avs")
Audio = Import("D:\test.avs")

Video = Video.ConvertToYV12()
Video = Video.AddBorders(0,132,0,132)
Video = Video.Spline16Resize(720,480)
#PullDown: using DGPulldown/HCenc to upsize FPS

Audio = Audio.SSRC(48000)

AudioDub(Video, Audio)
<>

<7/30/2016 11:41:20 AM>
DIRECTSHOW AUDIO MIXER OPERATIONS:
No ffdshow mixer ON/OFF adjustment required at runtime
No ffdshow mixer SETTING adjustment required at runtime
No LAV Filters mixer ON/OFF adjustment required at runtime
<>

<7/30/2016 11:41:20 AM>
START VIDEO ENCODING OPERATIONS
Video Encoding Profile: FFmpeg CBR 1-pass
Target Video FileSize: 153 MB
Encoding Parameters: -i "C:\Users\Stephen\AppData\Local\Temp\DVD_test_1.avs" -threads 4 -aspect 16:9 -c:v mpeg2video -b:v 8500k -minrate 8500k -maxrate 8500k -bufsize 2000k -dc 10 -y "C:\Users\Stephen\Videos\DVD_test.m2v"
<>

<7/30/2016 11:43:06 AM>
END VIDEO ENCODING OPERATIONS
Created File: C:\Users\Stephen\Videos\DVD_test.m2v (153.4 MB)
OUTPUT VIDEO INFO: MPEG-2 Video - 8500 kbps - 720x480 - DAR 16:9 - 23.976 fps - Progressive - 2:31 minutes - 3630 frames
<>

<7/30/2016 11:43:06 AM>
START PULLDOWN OPERATIONS
DGPulldown Parameters: "C:\Users\Stephen\Videos\DVD_test.m2v" -srcfps 23.976 -destfps 29.97 -inplace -tff
<>

<7/30/2016 11:43:17 AM>
END PULLDOWN OPERATIONS
DGPulldown executed on File: C:\Users\Stephen\Videos\DVD_test.m2v (153.4 MB)
OUTPUT VIDEO INFO: MPEG-2 Video - 8500 kbps - 720x480 - DAR 16:9 - 23.976 fps - Progressive (2:3 Pulldown) - 2:31 minutes - 4534 frames
<>

<7/30/2016 11:43:17 AM>
START AUDIO ENCODING OPERATIONS (Track 1)
Wavi+Aften Parameters: "C:\Users\Stephen\AppData\Local\Temp\DVD_test_1.avs" - | "C:\Users\Stephen\Documents\AVStoDVD_284_NoInstall\Aften\aften.exe" -b 192 -pad 0 -dynrng 5 -bwfilter 0 - "C:\Users\Stephen\Videos\DVD_test_1.ac3"
<>

<7/30/2016 11:43:41 AM>
END AUDIO ENCODING OPERATIONS (Track 1)
Created File: C:\Users\Stephen\Videos\DVD_test_1.ac3 (3.5 MB)
OUTPUT AUDIO INFO: AC3 - 192 kbps - CBR - 2 ch - 48000 Hz - 2:31 minutes (0 ms delay)
<>

<7/30/2016 11:43:41 AM>
START DVD AUTHORING OPERATIONS
BatchMux Parameters: -arglist "C:\Users\Stephen\AppData\Local\Temp\DVD_BatchMux.ini"
BatchMux ini file:
-bmlog "C:\Users\Stephen\AppData\Local\Temp\DVD_BatchMux.log"
-d "C:\Users\Stephen\Documents\DVD\VIDEO_TS"
-mxp "C:\Users\Stephen\AppData\Local\Temp\DVD_MuxMan.mxp"
-l "C:\Users\Stephen\AppData\Local\Temp\DVD_MuxMan.log"
-muxman "C:\Users\Stephen\Documents\AVStoDVD_284_NoInstall\MuxMan"
-prio LOW
-palette "C:\Users\Stephen\AppData\Local\Temp\DVD_Palette.txt"
-v "C:\Users\Stephen\Videos\DVD_test.m2v"
-vidmode LB
-a1 "C:\Users\Stephen\Videos\DVD_test_1.ac3"
-a1lang en

<>

<7/30/2016 11:44:00 AM>
END DVD AUTHORING OPERATIONS
Created Folder: C:\Users\Stephen\Documents\DVD (159.5 MB)

CHECK DVD SIZE
DVD Folder (actual) Size: 159.5 MB
vs Assets Size: 156.8 MB -> OK
vs Estimated Size: 159 MB -> 0.3% oversize
<>

<7/30/2016 11:44:00 AM>
AVStoDVD Project ended successfully.
<>

<7/30/2016 11:44:00 AM>
Log file created by AVStoDVD Release 2.8.4
<>
qyot27 is offline  
Old 30th July 2016, 17:22   #2231  |  Link
Groucho2004
 
Join Date: Mar 2006
Location: Barcelona
Posts: 5,034
Quote:
Originally Posted by MysteryX View Post
Do you realize that for almost everything you insulted me on, it turns out that what you said was false and I was right?
Do you realize that your opinions don't turn into facts just because you think you're always right?
__________________
Groucho's Avisynth Stuff

Last edited by Groucho2004; 30th July 2016 at 19:11.
Groucho2004 is offline  
Old 31st July 2016, 03:56   #2232  |  Link
MysteryX
Soul Architect
 
MysteryX's Avatar
 
Join Date: Apr 2014
Posts: 2,559
Quote:
Originally Posted by Groucho2004 View Post
Do you realize that your opinions don't turn into facts just because you think you're always right?
From now on I won't reply to any junk you throw at me; I'll leave your gifts to you.

I'm not here to argue as to who's right and who's wrong, and who's better than who. I'm here to contribute in what I can and share ideas. Taking other people's junk is not part of it.

Do whatever you want. I'll keep my center and focus. This is the last comment regarding any of your junk unless you really cross the line.

Quote:
Originally Posted by thescrapyard View Post
now AVStoDVD is accepting the avisynth.dll as a legitimate version
and there's no point in talking about a temporary problem that is already solved. At some point AVStoDVD will update their software. I certainly wouldn't hack AviSynth+'s source code to fix this.

Last edited by MysteryX; 31st July 2016 at 04:04.
MysteryX is offline  
Old 31st July 2016, 04:31   #2233  |  Link
qyot27
...?
 
qyot27's Avatar
 
Join Date: Nov 2005
Location: Florida
Posts: 1,419
Quote:
Originally Posted by MysteryX View Post
and there's no point in talking about a temporary problem that is already solved. At some point AVStoDVD will update their software. I certainly wouldn't hack AviSynth+'s source code to fix this.
There was no problem, temporary or otherwise, to 'solve' in the first place. What was being asked for was a frivolous revert of AviSynth+'s DLL versioning so that a harmless yellow warning sign and its corresponding warning message in AVStoDVD's GUI log widget would go away. A harmless warning sign/message that in no way stopped/stops the '0.1.0' versioned AviSynth+ from being used by AVStoDVD.
qyot27 is offline  
Old 31st July 2016, 15:38   #2234  |  Link
thescrapyard
Registered User
 
thescrapyard's Avatar
 
Join Date: Feb 2008
Posts: 59
Quote:
Originally Posted by qyot27 View Post
There was no problem, temporary or otherwise, to 'solve' in the first place. What was being asked for was a frivolous revert of AviSynth+'s DLL versioning so that a harmless yellow warning sign and its corresponding warning message in AVStoDVD's GUI log widget would go away. A harmless warning sign/message that in no way stopped/stops the '0.1.0' versioned AviSynth+ from being used by AVStoDVD.
Sorry, but on my version of AVStoDVD 2.8.4 (very latest portable release) it was stopping me doing anything. All I hacked was the version being reported. It worked for me until things get updated or altered

The question should be why is avisynth+ version being reported as 0.1.0 and not 2.6.x if its based on avisynth. Without starting a slanging match .... if its to avoid confusion between avisynth and avisynth+ I understand that but why is there not something that reports it as avisynth 2.6.x so other software recognises it as such. Either the avisynth+.dll is at fault or the software trying to read the version coding is at fault
thescrapyard is offline  
Old 31st July 2016, 15:59   #2235  |  Link
Reel.Deel
Registered User
 
Join Date: Mar 2012
Location: Texas
Posts: 1,664
@thescrapyard

Maybe you should of posted these links ([1], [2]) in the AVSToDVD thread.
Reel.Deel is offline  
Old 31st July 2016, 16:06   #2236  |  Link
Chikuzen
typo lover
 
Chikuzen's Avatar
 
Join Date: May 2009
Posts: 595
Quote:
Originally Posted by thescrapyard View Post
The question should be why is avisynth+ version being reported as 0.1.0 and not 2.6.x if its based on avisynth. Without starting a slanging match .... if its to avoid confusion between avisynth and avisynth+ I understand that but why is there not something that reports it as avisynth 2.6.x so other software recognises it as such. Either the avisynth+.dll is at fault or the software trying to read the version coding is at fault
avisynth and avs+ have three value about version.

1. AVISYNTH_INTERFACE_VERSION
This can access by plugins or applications which operates avisynth.dll directly.

2. VersionNumber
This is the float value you can access by VersionNumber().
avs+ always returns 2.6000.

3. VersionString
This is the string you will see with Version().

It seems that AVS2DVD using VersionString to recognize dll version.
I don't know why that author using not VersionNumber but VersionString.
__________________
my repositories
Chikuzen is offline  
Old 31st July 2016, 17:22   #2237  |  Link
Groucho2004
 
Join Date: Mar 2006
Location: Barcelona
Posts: 5,034
Quote:
Originally Posted by Chikuzen View Post
avisynth and avs+ have three value about version.

1. AVISYNTH_INTERFACE_VERSION
This can access by plugins or applications which operates avisynth.dll directly.

2. VersionNumber
This is the float value you can access by VersionNumber().
avs+ always returns 2.6000.

3. VersionString
This is the string you will see with Version().

It seems that AVS2DVD using VersionString to recognize dll version.
I don't know why that author using not VersionNumber but VersionString.
You forgot the FILEVERSION/PRODUCTVERSION that is stored in the DLL version resource. This is for example "2.6.0.6" for 2.6 release and "0.1.0.0" for AVS+.
This is also what AVS2DVD checks since it does not use the Avisynth API.
__________________
Groucho's Avisynth Stuff
Groucho2004 is offline  
Old 31st July 2016, 21:31   #2238  |  Link
qyot27
...?
 
qyot27's Avatar
 
Join Date: Nov 2005
Location: Florida
Posts: 1,419
Quote:
Originally Posted by thescrapyard View Post
Sorry, but on my version of AVStoDVD 2.8.4 (very latest portable release) it was stopping me doing anything. All I hacked was the version being reported. It worked for me until things get updated or altered

The question should be why is avisynth+ version being reported as 0.1.0 and not 2.6.x if its based on avisynth. Without starting a slanging match .... if its to avoid confusion between avisynth and avisynth+ I understand that but why is there not something that reports it as avisynth 2.6.x so other software recognises it as such. Either the avisynth+.dll is at fault or the software trying to read the version coding is at fault
As I demonstrated above with the NoInstall package of AVStoDVD 2.8.4, it could recognize and use AviSynth+ (I was using a personal build ca. r2067) without any problem. Windows 10 Home 32-bit, with AviSynth+ installed in Program Files and AVStoDVD unpacked to a folder in Documents. So neither AVStoDVD's version detection nor AviSynth+'s change of versioning are at fault there. Version checks don't spontaneously work on one setup and fail on another in a case like this, unless there's something else in your personal configuration causing a problem, and it's whatever that problem is that's the real issue.

When reporting bugs, report everything about your setup, no matter how trivial you think it might be. Windows version, AviSynth+ build version (the revision number reported by Version(), not the stable release number), version of AVStoDVD if relevant. Whether you're using Administrator or User restricted privileges, where the programs are installed. If you've troubleshooted by moving the contents of AviSynth's plugins away from the autoload folder to ensure any one of those aren't causing an issue.


AviSynth+ changed its versioning during the early stages of the forking process because it had added so many new things that it no longer counted as merely a superset of AviSynth 2.6 but increasingly as its own project. Since the approved methods of checking the version number do not include the DLL versioning metadata, that was eventually also changed to match the canonical AviSynth+ versioning as well.
qyot27 is offline  
Old 31st July 2016, 21:54   #2239  |  Link
Groucho2004
 
Join Date: Mar 2006
Location: Barcelona
Posts: 5,034
Quote:
Originally Posted by qyot27 View Post
As I demonstrated above with the NoInstall package of AVStoDVD 2.8.4, it could recognize and use AviSynth+ (I was using a personal build ca. r2067) without any problem. Windows 10 Home 32-bit, with AviSynth+ installed in Program Files and AVStoDVD unpacked to a folder in Documents. So neither AVStoDVD's version detection nor AviSynth+'s change of versioning are at fault there. Version checks don't spontaneously work on one setup and fail on another in a case like this, unless there's something else in your personal configuration causing a problem, and it's whatever that problem is that's the real issue.
I finally figured why AVS2DVD always complained that Avisynth is not installed. It checks the existence of this registry key:
[HKEY_LOCAL_MACHINE\SOFTWARE\AviSynth]

I'm using my Avisynth switcher which writes this key:
[HKEY_LOCAL_MACHINE\SOFTWARE\Avisynth]

See the difference? The check is case sensitive and therefore fails. I still stand by what I wrote in this post about how to properly validate an Avisynth install.
__________________
Groucho's Avisynth Stuff
Groucho2004 is offline  
Old 1st August 2016, 08:17   #2240  |  Link
MysteryX
Soul Architect
 
MysteryX's Avatar
 
Join Date: Apr 2014
Posts: 2,559
Quote:
Originally Posted by Chikuzen View Post
avisynth and avs+ have three value about version.

1. AVISYNTH_INTERFACE_VERSION
This can access by plugins or applications which operates avisynth.dll directly.

2. VersionNumber
This is the float value you can access by VersionNumber().
avs+ always returns 2.6000.

3. VersionString
This is the string you will see with Version().

It seems that AVS2DVD using VersionString to recognize dll version.
I don't know why that author using not VersionNumber but VersionString.
In my own software, I also have a AVS version check and I implemented it the same way as AVStoDVD: check the DLL version. Why? Because it's much simpler than referencing the DLL and calling its API, and it gives me what I want.

As for what value it returns, it's doing what it should: returning its version number. It may have the AviSynth 2.6 interface, but it's AviSynth+, and that's what I wanted to know.

If a software is specifically checking for an AviSynth version and it's not what it expects, then it's that software that must be udpated.

Quote:
Originally Posted by Groucho2004 View Post
I finally figured why AVS2DVD always complained that Avisynth is not installed. It checks the existence of this registry key:
[HKEY_LOCAL_MACHINE\SOFTWARE\AviSynth]

I'm using my Avisynth switcher which writes this key:
[HKEY_LOCAL_MACHINE\SOFTWARE\Avisynth]

See the difference? The check is case sensitive and therefore fails. I still stand by what I wrote in this post about how to properly validate an Avisynth install.
I personally wouldn't use this because AviSynth.dll can work as a stand-alone DLL. But if one wants to know if it's "installed", which is different than "whether an AviSynth DLL is available", then yes that's the way to do it.
MysteryX is offline  
Closed Thread

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT +1. The time now is 13:25.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.