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. |
28th May 2020, 00:26 | #261 | Link |
Registered User
Join Date: Sep 2003
Location: Berlin, Germany
Posts: 3,078
|
@FranceBB
I tried to reproduce your issues using C-Plugins with the latest test build by pinterf. But I couldn't... What is this error about ScriptEnvironment? I do not understand. I have GrunT.dll in my autoload folder, and it does not interfere with anything. Do you autoload any GScript stuff? The only C-Plugins I use are the old original YADIF plugin and the ffms2 C-plugin. And both work just fine under this latest pinterf test build. AVS+ autoloads these C-Plugins just fine, and under AVStoDVD (which does not use the VfW interface) both work without any issues. This is under AVS+ 32-bit, Win7-64 . Last edited by manolito; 28th May 2020 at 00:36. |
28th May 2020, 01:40 | #262 | Link | |
...?
Join Date: Nov 2005
Location: Florida
Posts: 1,419
|
Quote:
It's really not a whole lot of energy at all. Oh, copy-paste line 1 instead of line 2. Go fix some coffee. |
|
28th May 2020, 02:09 | #263 | Link | |
Registered User
Join Date: Jan 2018
Posts: 2,153
|
Quote:
|
|
28th May 2020, 02:25 | #264 | Link | |
Broadcast Encoder
Join Date: Nov 2013
Location: Royal Borough of Kensington & Chelsea, UK
Posts: 2,883
|
Quote:
You see, just like you have Win7 and WinXP and you wanna keep one version of every plugin on both to keep everything in the two machines consistent, I have the very same setup on Win10 and WinXP where I keep everything the same (except for the x64 version which is Win10 only for me), however with Avisynth 3.6.x on XP x86 I can't use programs that call the frameserver using the C interface like AVSPmod, AVSMeter etc. On Win10 it works like a charm now, though... So it must be something in the C interface to call Avisynth that makes XP misbehave. Solving your problem in AVS 3.6.1 actually partially solved mine too, 'cause before, with AVS 3.6.0, not even the VfW interface was working, so we made progress. I'm sure Ferenc or qyot27 will come up with a solution. Last edited by FranceBB; 28th May 2020 at 02:28. |
|
28th May 2020, 08:39 | #265 | Link |
Join Date: Mar 2006
Location: Barcelona
Posts: 5,034
|
AVSMeter uses the C++ API to interface with Avisynth.
__________________
Groucho's Avisynth Stuff |
28th May 2020, 08:41 | #266 | Link |
Registered User
Join Date: Jan 2014
Posts: 2,309
|
AvsMeter has no C interface.
And unfortunately for me all tools are working properly (Win10 with avs+ 32 or 64 bits), Avspmod, x264 versions, AvsMeter (32 and 64 bits) But the problem needs to be investigated. Not because of XP support but it can be a hidden bug which later can occur on other systems as well. No crash occurs without a good reason. |
28th May 2020, 09:18 | #268 | Link |
Join Date: Mar 2006
Location: Barcelona
Posts: 5,034
|
@FranceBB
You're testing this on a vanilla XP, not the one with modified kernel, right?
__________________
Groucho's Avisynth Stuff |
28th May 2020, 10:37 | #269 | Link |
Registered User
Join Date: Jan 2014
Posts: 2,309
|
As a small step, if you need, you can open scripts from an unicode path, no need for ansi conversion.
https://github.com/staxrip/staxrip/b...Server.cpp#L72 Code:
AVSValue args[2] = { utf8file.c_str(), true }; const char* const arg_names[2] = { 0, "utf8" }; env->Invoke("Import", AVSValue(args, 2), arg_names); |
28th May 2020, 11:29 | #270 | Link | |
Broadcast Encoder
Join Date: Nov 2013
Location: Royal Borough of Kensington & Chelsea, UK
Posts: 2,883
|
Quote:
SP4 with Microsoft Extended Updates 'till July 2019, custom kernel with Win Vista and a bit of 7 backported APIs, unlocked PAE, DirectX 11 on my real PC. They both behave the same in this case. As a matter of fact, they've always behaved the same for Avisynth. The custom kernel did the trick by implementing kernel calls necessary to run things like Audacity, Blender, Adobe Acrobat Reader DC and other things. Last edited by FranceBB; 28th May 2020 at 11:41. |
|
28th May 2020, 11:41 | #272 | Link |
Join Date: Mar 2006
Location: Barcelona
Posts: 5,034
|
OK, just checking.
__________________
Groucho's Avisynth Stuff |
28th May 2020, 12:41 | #276 | Link | |
Registered User
Join Date: Jun 2002
Location: On thin ice
Posts: 6,837
|
Quote:
__________________
https://github.com/stax76/software-list https://www.youtube.com/@stax76/playlists Last edited by stax76; 28th May 2020 at 12:47. |
|
29th May 2020, 01:15 | #277 | Link | |
Registered User
Join Date: Sep 2003
Location: Berlin, Germany
Posts: 3,078
|
Quote:
My tests were under Win7-64, not under WinXP. My XP computer has a single core CPU and only 576 MB of RAM. So using AVS+ with multithreading would not make sense. I tried it with a previous AVS+ version, but soon went back to classic AVS because it was faster. After your issues I installed the current 3.61 test version under XP, but I could not get it working at all. The version() call returned the correct version, but neither AVStoDVD nor StaxRip were able to load any source files. AVStoDVD could not even detect an installed AviSynth version and gave me a non-fatal warning at startup. No crashes, though. I never tried AVS+ 3.5.1 on the XP machine, but I suppose that it would work. //EDIT// Being curious and not tired yet I just did install the 3.5.1 XP version on my WinXP machine. And just as I suspected this version works fine under XP. Overinstalling the latest test version again broke it completely. So for me this 3.6.1 test version fixes all previous 3.6 issues under Win7, but it sure does not deserve the label "XP version". Last edited by manolito; 29th May 2020 at 01:52. |
|
29th May 2020, 01:53 | #278 | Link | ||
Broadcast Encoder
Join Date: Nov 2013
Location: Royal Borough of Kensington & Chelsea, UK
Posts: 2,883
|
Quote:
In other words: 3.6.0 - nothing works. 3.6.1 - Programs accessing Avisynth directly don't work, but those who use VfW like virtual dub do. Quote:
Thank you for testing it on your system, though, it makes 2 out of 2 so I'm sure it's not related to my configuration. Last edited by FranceBB; 29th May 2020 at 01:56. |
||
29th May 2020, 02:59 | #279 | Link |
Registered User
Join Date: Sep 2003
Location: Berlin, Germany
Posts: 3,078
|
Right, I did not test VDub, just forgot about it. But I did test StaxRip 1.1.9.0 which also uses the VfW interface. Not good, it was unable to open any source file regardless of the source format. All source filters (DSS2Mod, ffms2, LSmash and DirectShowSource) quit with an error.
|
29th May 2020, 07:28 | #280 | Link | |
Registered User
Join Date: Jul 2003
Location: India
Posts: 890
|
Quote:
Is there a problem if I look for fftw3.dll first or is there an advantage of looking for libfftw3f-3? There is some discussion on why MakeWritable was discouraged earlier. Then it was mentioned(if I remember correctly) that for this call avisynth has to anyway create a new frame, copy old frame and change/ set some flags while if its done in plugin by calling newvideoframe and copy using BitBlt its less work. |
|
Thread Tools | Search this Thread |
Display Modes | |
|
|