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. |
|
|
Thread Tools | Search this Thread | Display Modes |
25th June 2019, 09:28 | #41 | Link |
Registered User
Join Date: Jan 2014
Posts: 2,314
|
Moved to git, real release:
AvsInPaint v1.1 (20190624) https://github.com/pinterf/AvsInpaint/releases Code:
- Fix crash in AVSInpaint-2008.02.23, when using mode "Deblend" or "Both" (double frame release, revealed when using Avisynth+) - Add version resource - Visual Studio 2019 solution - Moved to Avisynth C 2.5 interface - x64 version - (no new colorspaces) |
25th June 2019, 14:36 | #42 | Link |
Banana User
Join Date: Sep 2008
Posts: 989
|
I updated wiki of http://avisynth.nl/index.php/InpaintFunc with newer versions of InpaintFunc and requirements.
|
26th June 2019, 23:53 | #43 | Link | |
Registered User
Join Date: Jun 2010
Posts: 91
|
Quote:
Is 2.5 a typo? |
|
27th June 2019, 00:35 | #44 | Link |
Join Date: Mar 2006
Location: Barcelona
Posts: 5,034
|
No, C 2.5 interface is the latest. You may be thinking of the C++ interface.
__________________
Groucho's Avisynth Stuff |
27th June 2019, 07:42 | #46 | Link |
Registered User
Join Date: Mar 2011
Posts: 4,829
|
I probably should have checked before assuming, but I didn't test the new AVSInPaint build with Avisynth 2.6. It may be an XP-only issue, however it's working with Avisynth+, but not Avisynth 2.6. It applies to version 1.1 Beta and version 1.1.
I can't imagine why I wouldn't have checked the beta version with Avisynth 2.6, but obviously I didn't as it prevents Avisynth 2.6 from loading. I didn't have VS 2019 installed, but installing it didn't change anything. Rebooting didn't help. Unless it's more than an XP problem, I can probably load the appropriate dll as required (the old version for Avisynth 2.6 and the new version for Avisynth+). I have the following script in the Avisynth 2.6 auto-loading folder, and the result is below. I've also tried LoadCPlugin and LoadPlugin. Anyone else tested with Avisynh 2.6? AVSInpaint = "C:\Program Files\AviSynth\C Plugins\AvsInPaint.dll" exist(AVSInpaint) ? Load_Stdcall_Plugin(AVSInpaint) : nop() Edit: For anyone else who may need it, I'm currently making AVSInPaint work for the installed Avisynth 2.6 and MeGUI's Avisynth+ by adding the following avsi script to the installed Avisynth/plugins folder. No need to manually load ImageSeq.dll for Avisynth+ either. Edit the file paths and dll names to suite. Code:
IsAvisynthPlus = (FindStr(LCase(VersionString), "avisynth+") > 0) ImageSeq = "C:\Program Files\MeGUI\tools\avs\plugins\ImageSeq.dll" IsAvisynthPlus && exist(ImageSeq) ? LoadPlugin(ImageSeq) : nop() AVSInPaintNew = "C:\Program Files\AviSynth\C Plugins\AVSInPaint 1.1.dll" IsAvisynthPlus && exist(AVSInPaintNew) ? LoadCPlugin(AVSInPaintNew) : nop() AVSInPaintOld = "C:\Program Files\AviSynth\C Plugins\AVSInPaint 2008-02-23.dll" !IsAvisynthPlus && exist(AVSInPaintOld) ? Load_Stdcall_Plugin(AVSInPaintOld) : nop() Last edited by hello_hello; 27th June 2019 at 08:36. |
27th June 2019, 07:46 | #47 | Link |
Join Date: Mar 2006
Location: Barcelona
Posts: 5,034
|
Why are you loading it as a 2.0 plugin? Did you miss that the C interface has been updated to 2.5? Change Load_Stdcall_Plugin() to LoadCPlugin() and it should work.
__________________
Groucho's Avisynth Stuff |
27th June 2019, 08:19 | #48 | Link | |
Registered User
Join Date: Mar 2011
Posts: 4,829
|
Quote:
Load_Stdcall_Plugin() works with Avisynth+. |
|
27th June 2019, 08:35 | #49 | Link | |
Join Date: Mar 2006
Location: Barcelona
Posts: 5,034
|
Quote:
__________________
Groucho's Avisynth Stuff |
|
27th June 2019, 09:24 | #50 | Link | |
Registered User
Join Date: Mar 2011
Posts: 4,829
|
There's no avisynth_c.dll.
If by "post the log file" you mean use the "Save Info" button, this is everything when I use the script I posted earlier to try and auto-load the new AVSInPaint: Quote:
When I don't try to load it there's no errors except one. Edit: See the next post for the "full" log. As a side note, when I prevent Avisynth 2.6 from trying to load the new AVSInPaint, this is the single error. LoadPlugin: unable to load "C:\Program Files\AviSynth\plugins\VSFilter 3.1.0.801.dll", error=0x3e6 Any idea what error 0x3e6 means? I ask because it's an odd one. If I remember correctly, VSFilter will load when opening scripts with MPC-HC, but not MeGUI (even with Avisynth 2.6). If I remember correctly, I have to manually load an old version for MeGUI. It won't even manually load the new one from the plugins folder. It seems a bit odd and I've never discovered why, but it's been a while so I'd have to check all that. I did remove VSFilter 3.1.0.801.dll from the plugins folder and ran Info Tool again, just in case it was causing oddness, but nothing changed, except then no there were no errors (unless I tried to load AVSInPaint). Last edited by hello_hello; 27th June 2019 at 09:43. |
|
27th June 2019, 09:42 | #51 | Link | ||
Registered User
Join Date: Mar 2011
Posts: 4,829
|
Here's the entire Info Tool log when I delete everything from the auto-loading plugins folder except for the script loading (mostly) C-Plugins, while preventing the script from loading the new AVSInPaint:
Quote:
Quote:
|
||
27th June 2019, 09:48 | #52 | Link |
Registered User
Join Date: Jan 2014
Posts: 2,314
|
I'm seeing the problem. I'll have to look into it.
(And I confused you, the old dll was a 2.5 C DLL as well, avsinfo is listing it as such) EDIT Seems, my build has _avisynth_c_plugin_init@4 while the old dll exports avisynth_c_plugin_init@4 Last edited by pinterf; 27th June 2019 at 09:56. |
27th June 2019, 10:56 | #54 | Link |
Registered User
Join Date: Jan 2014
Posts: 2,314
|
Test build for avs 2.6, 32 bit-only, please try if it works and do further test with it.
https://drive.google.com/open?id=1PJ...fzuX984OJBDQ_M |
27th June 2019, 11:51 | #55 | Link | |
Registered User
Join Date: Mar 2011
Posts: 4,829
|
Quote:
Avisynth 2.6.... I haven't run any full encodes, but it's working with my test script. The three InPaintFunc modes seem fine (no crashes or errors so far, anyway). Cheers. PS Tested on XP. Last edited by hello_hello; 27th June 2019 at 11:59. |
|
27th June 2019, 12:22 | #56 | Link | |
Registered User
Join Date: Jan 2014
Posts: 2,314
|
Quote:
What is searched for when establishing from a DLL if it is a C plugin? AVS+ x64: avisynth_c_plugin_init _avisynth_c_plugin_init@4 AVS+ Win32 _avisynth_c_plugin_init@4 avisynth_c_plugin_init@4 AVS 2.6 Win32 avisynth_c_plugin_init@4 avisynth_c_plugin_init So the winner is: avisynth_c_plugin_init@4 that works for both Avs+ and Avs 2.6 Since the old AvsInpaint.dll exports avisynth_c_plugin_init@4 there is no problem. Now my question: how on Earth can I remove the underscore and keep the parameter length (@4) in a Visual Studio build? |
|
27th June 2019, 12:59 | #57 | Link | |
Registered User
Join Date: Apr 2008
Posts: 418
|
Quote:
|
|
27th June 2019, 15:50 | #59 | Link | |
...?
Join Date: Nov 2005
Location: Florida
Posts: 1,420
|
Quote:
https://social.msdn.microsoft.com/Fo...rum=vclanguage |
|
27th June 2019, 16:02 | #60 | Link | |
Registered User
Join Date: Jan 2014
Posts: 2,314
|
Quote:
EDIT: perhaps with gcc. Or I make next Avs+ to search for a fully undecorated name when it checks for avisynth_c_plugin_init Last edited by pinterf; 27th June 2019 at 16:08. |
|
|
|