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. |
3rd June 2017, 18:41 | #3441 | Link |
Registered User
Join Date: Jan 2014
Posts: 2,314
|
I'm on the XP problem, so far no success.
EDIT: Arggh. It was a compiler setting problem: /Zc:threadSafeInit- was missing. But now I see what happens. During autoload, these DLLs called GetCPUFlags in their Init, after AddFunction and caused Avisynth+ to crash. VerticalCleanerSSE2.dll RepairSSE2.dll RemoveGrainSSE2.dll RemoveDirtSSE2.dll SSE2Tools.dll e.g. in old RemoveGrain source Code:
extern "C" __declspec(dllexport) const char* __stdcall AvisynthPluginInit2(IScriptEnvironment* env) { #ifdef MODIFYPLUGIN env->AddFunction("Repair", "cc[mode]i[modeU]i[modeV]i[planar]b", CreateRemoveGrain, 0); env->AddFunction("TemporalRepair", "cc[smooth]i[grey]b[planar]b", CreateTemporalRepair, 0); #else // MODIFYPLUGIN env->AddFunction("RemoveGrain", "c[mode]i[modeU]i[modeV]i[planar]b", CreateRemoveGrain, 0); env->AddFunction("Clense", "c[grey]b[reduceflicker]b[planar]b[cache]i", CreateClense, 0); env->AddFunction("MCClense", "ccc[grey]b[planar]b", CreateMCClense, 0); env->AddFunction("BackwardClense", clenseargs, CreateBackwardClense, 0); env->AddFunction("ForwardClense", clenseargs, CreateForwardClense, 0); #endif // MODIFYPLUGIN AVSenvironment = env; if( (CPUFLAGS & env->GetCPUFlags()) != CPUFLAGS ) #if ISSE > 1 env->ThrowError("RemoveGrain needs an SSE2 capable cpu!\n"); #else env->ThrowError("RemoveGrain needs an SSE capable cpu!\n"); #endif #if 0 debug_printf(LOGO); #endif return "RemoveGrain: remove grain from film"; } From the two debug lines in GetCPUFlags, only the first one was displayed, seems that calling CPUCheckForExtensions gave an instant crash. In cpuid.cpp Code:
static int CPUCheckForExtensions() { ... } int GetCPUFlags() { _RPT0(0, "GetCPUFlags() called\n"); static int lCPUExtensionsAvailable = CPUCheckForExtensions(); _RPT0(0, "GetCPUFlags() called 2\n"); return lCPUExtensionsAvailable; } Rebuild later, it's already dark here, and I have get home w/o police affairs (forgot to put front lamp on my bike) Last edited by pinterf; 3rd June 2017 at 20:06. |
3rd June 2017, 22:26 | #3442 | Link |
Registered User
Join Date: Jan 2014
Posts: 2,314
|
Thank you for your patience, here come the fixed binaries
Download Avisynth+ r2504-MT (broken XP support hotfix) Last edited by pinterf; 3rd June 2017 at 22:37. Reason: typo |
3rd June 2017, 23:15 | #3444 | Link | |
Join Date: Mar 2006
Location: Barcelona
Posts: 5,034
|
Quote:
You should clean this up and re-install: - Delete "C:\Program Files (x86)\AviSynth+" and subdirs - Delete these registry keys: HKEY_CURRENT_USER\Software\Avisynth HKEY_LOCAL_MACHINE\SOFTWARE\Avisynth HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Avisynth Last edited by Groucho2004; 3rd June 2017 at 23:30. |
|
5th June 2017, 11:35 | #3446 | Link |
Registered User
Join Date: Oct 2002
Location: France
Posts: 2,316
|
@Pinterf : Are-you using VS2017 ? If i haven't try for now to update to VS2017, is that i don't know if XP is still supported. When your new version didn't work, i thought i was the case, i said to myself "No... He didn't forget the /Zc:threadSafeInit-, it's probably not so easy... ".
Another thing, i don't know if the it can be installed under a 32bits OS (bad surprise with last Intel Compiler which doesn't install under a 32bits OS... ). Last edited by jpsdr; 5th June 2017 at 11:38. |
5th June 2017, 12:38 | #3447 | Link |
HeartlessS Usurer
Join Date: Dec 2009
Location: Over the rainbow
Posts: 10,980
|
Jpsdr, see here:- https://www.visualstudio.com/en-us/p...mpatibility-vs
XP supported as target, but last VS to support compilation on XP was vs 2010. (Not sure, I think XP tool set was not provided until quite recently on vs 2017, I guess that they finally realized that not everyone was willing to drop support for some millions of the old OS users).
__________________
I sometimes post sober. StainlessS@MediaFire ::: AND/OR ::: StainlessS@SendSpace "Some infinities are bigger than other infinities", but how many of them are infinitely bigger ??? |
5th June 2017, 12:48 | #3448 | Link | |
...?
Join Date: Nov 2005
Location: Florida
Posts: 1,420
|
Quote:
But I installed it a couple months ago and don't remember too well. |
|
6th June 2017, 08:31 | #3449 | Link | |
Registered User
Join Date: Jan 2014
Posts: 2,314
|
Quote:
|
|
7th June 2017, 21:21 | #3450 | Link |
Registered User
Join Date: Jan 2016
Posts: 98
|
Problem with CombinePlanes?
Code:
FFmpegSource2(source="MVI_2038.avi") #ConvertToYV12() c0 = last Y8=ExtractY() U8=ExtractU() V8=ExtractV() Y8= <luma Separate filter(s)> U8= <chroma Separate filter(s)> V8= <chroma Separate filter(s)> CombinePlanes(Y8, U8, V8, planes="YUV", sample_clip=c0) #, pixel_type="YUV420P8" #, source_planes="YYY") Am I doing anything wrong? This is the error message I get when trying it with YUV422 material: "CombinePlanes: source and target plane dimensions are different" Last edited by VS_Fan; 7th June 2017 at 21:24. Reason: include error message |
7th June 2017, 23:58 | #3451 | Link | |
Retried Guesser
Join Date: Jun 2012
Posts: 1,373
|
Quote:
avs_core\filters\planeswap.cpp, Line 870 Code:
int target_plane_width = vi_default.width >> vi_default.GetPlaneWidthSubsampling(current_target_plane); int target_plane_height = vi_default.height >> vi_default.GetPlaneWidthSubsampling(current_target_plane); |
|
8th June 2017, 07:52 | #3452 | Link | |
Registered User
Join Date: Jan 2014
Posts: 2,314
|
Quote:
|
|
8th June 2017, 12:18 | #3453 | Link |
Registered User
Join Date: Jan 2014
Posts: 2,314
|
CombinePlanes fixed, thanks for the report.
Download Avisynth+ r2506 Code:
20170608 r2506 - Fix CombinePlanes: feeding YV16 or YV411 target with Y8 sources |
11th June 2017, 19:26 | #3455 | Link | |
Join Date: Mar 2006
Location: Barcelona
Posts: 5,034
|
Quote:
libfftw3f-3.dll is not a plugin, it's not supposed to be in the auto-load directory. It has to be either in the current directory, the same directory of the calling program or in a directory to which the "PATH" environment variable points. For simplicity, just put it in System32/SysWOW64. Last edited by Groucho2004; 12th June 2017 at 11:46. |
|
21st June 2017, 01:19 | #3458 | Link |
Soul Architect
Join Date: Apr 2014
Posts: 2,559
|
I'm running FrameRateConverter with 1 thread
Code:
FrameRateConverter(60, output="auto") Code:
FPS (min | max | average): 2.044 | 68778 | 12.90 Memory usage (phys | virt): 353 | 349 MiB Thread count: 21 CPU usage (average): 13% Code:
FPS (min | max | average): 2.332 | 129914 | 31.80 Memory usage (phys | virt): 785 | 784 MiB Thread count: 29 CPU usage (average): 42% |
Thread Tools | Search this Thread |
Display Modes | |
|
|