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. |
25th November 2016, 21:32 | #2621 | Link |
Registered User
Join Date: Nov 2014
Posts: 440
|
Oops, I really misunderstood.
__________________
github.com |
26th November 2016, 21:29 | #2622 | Link |
Registered User
Join Date: Jan 2014
Posts: 2,314
|
Do you usually do extreme sports?
Regarding avisynth things, I'm still waiting for more error reports. jpsdr already found two of them. The development version on my git contains the following changes:
Then there is a new RgTools (waiting for release), forked from tp7's repository. The new version supports 10,12,14,16 bit and float formats, and accepts planar RGB besides YUV (with all valid bit-depths of course) |
26th November 2016, 23:55 | #2623 | Link | |
HeartlessS Usurer
Join Date: Dec 2009
Location: Over the rainbow
Posts: 10,980
|
I have been known to have about 260 plugs in-situ, although more recently is limited to about 160 (+ specials on occasion)
Quote:
EDIT: (I'm still sticking currently with Standard AVS, but am quite excited because of all of your Good Stuff, will swap one day) Peace and Love
__________________
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 ??? Last edited by StainlessS; 26th November 2016 at 23:59. |
|
27th November 2016, 06:45 | #2624 | Link |
Registered User
Join Date: Nov 2016
Posts: 12
|
Hi there, I can finally post after one week…
Using NSIS, I've compiled an alternative avs+ installer based on the latest r2294 release. Basically this was for my personal use but maybe some people will find it interesting. Note : x64 systems only. Additional features
Optional :
Downloads Any feedback will be appreciated. Thanks. |
27th November 2016, 12:21 | #2625 | Link | |
Registered User
Join Date: Jan 2014
Posts: 2,314
|
Quote:
0.) Renaming the given dll to xx_100.DLL .. xx_600.dll 1.) Run a simple script using avsmeter 2.) Get avsmeter - avsinfo Summary - avsmeter -avsinfo has problems with too much DLLs - Loading DLL's consume memory, it depends on the plugin. e.g. I don't know why 500 pcs of RgTools eat a relatively large memory - nice to have feature from avsmeter: list approx idle memory consumption after DLL loading Test #1 (mvtools2.dll 2.7.5.22) 1.) avsmeter testscript.avs Memory consumption was 242MB with, 168 MB without the 500+ DLL's 2.) avsmeter -avsinfo Listed all CPP 26 plugins, even the last one ... C:\Program Files (x86)\AviSynth\plugins\xx_599.dll [2.7.5.22] C:\Program Files (x86)\AviSynth\plugins\xx_600.dll [2.7.5.22] Then Cannot load file 'C:/Program Files (x86)/AviSynth/plugins/xx_138.dll'. Platform returned code 1114: dynamic link library (DLL) intialization routine failed. Cannot load file 'C:/Program Files (x86)/AviSynth/plugins/xx_139.dll'. Platform returned code 1114: dynamic link library (DLL) intialization routine failed. Test #2 (rgtools.dll 0.93) 1.) avsmeter testscript.avs worked Memory consumption was 1045MB with, 168 MB without the 500+ DLL's 2.) avsmeter -avsinfo Listed all CPP 26 plugins, even the last one .. C:\Program Files (x86)\AviSynth\plugins\xx_599.dll [0.9.3.0] C:\Program Files (x86)\AviSynth\plugins\xx_600.dll [0.9.3.0] There were NO avsmeter error messages like with mvtools2 Test #3 (nnedi3.dll 0.9.4.30) 1.) avsmeter testscript.avs worked (but spent a few minutes in "Querying avisynth info") Memory consumption was 181MB with, 168 MB without the 500+ DLL's 2.) avsmeter -avsinfo It took some minutes until I got the list (that nnedi3 DLL is huge) Same, as with mvtools2, I got Cannot load file 'C:/Program Files (x86)/AviSynth/plugins/xx_138.dll'. Platform returned code 1114: dynamic link library (DLL) intialization routine failed. Cannot load file 'C:/Program Files (x86)/AviSynth/plugins/xx_139.dll'. Platform returned code 1114: dynamic link library (DLL) intialization routine failed. Test #4 (knlmeanscl.dll) 1.) avsmeter testscript.avs worked Memory consumption was 227MB with, 168 MB without the 500+ DLL's 2.) avsmeter -avsinfo There were NO avsmeter error messages like with mvtools2 and nnedi3 |
|
27th November 2016, 13:05 | #2626 | Link | |||
Join Date: Mar 2006
Location: Barcelona
Posts: 5,034
|
Quote:
Quote:
Quote:
__________________
Groucho's Avisynth Stuff Last edited by Groucho2004; 27th November 2016 at 13:43. |
|||
27th November 2016, 13:59 | #2627 | Link | |
Registered User
Join Date: Jan 2014
Posts: 2,314
|
Quote:
In this phase, only PluginInit is called, right? Functions implemented in the DLL are added to Avisynth's function list. Only 6 of them exist: Code:
env->AddFunction("RemoveGrain", "c[mode]i[modeU]i[modeV]i[planar]b", Create_RemoveGrain, 0); env->AddFunction("Repair", "cc[mode]i[modeU]i[modeV]i[planar]b", Create_Repair, 0); env->AddFunction("Clense", "c[previous]c[next]c[grey]b", Create_Clense, 0); env->AddFunction("ForwardClense", "c[grey]b", Create_ForwardClense, 0); env->AddFunction("BackwardClense", "c[grey]b", Create_BackwardClense, 0); env->AddFunction("VerticalCleaner", "c[mode]i[modeU]i[modeV]i[planar]b", Create_VerticalCleaner, 0); |
|
27th November 2016, 16:09 | #2628 | Link | |
Join Date: Mar 2006
Location: Barcelona
Posts: 5,034
|
Quote:
One explanation would be that the other two DLLs are statically linked and Avisynth stops enumerating after the first DLL initialization failure. Have you tried building mvtools2 with dynamic linking to the MS runtimes? It might turn out that it uses just as much memory as RGTools if the enumeration finishes.
__________________
Groucho's Avisynth Stuff |
|
28th November 2016, 10:24 | #2629 | Link |
Registered User
Join Date: Oct 2002
Location: France
Posts: 2,316
|
nnedi3 is build with runtime library option /MT, not /MD.
I must said that i don't realy know very precisely what's the difference, but i've read once that it would be better. I don't remember exactly what the "better" was, probably not having to install redistribuables, but not sure. Now, if you said that finaly /MD is better, i don't mind switching for the next releases. |
28th November 2016, 10:42 | #2630 | Link | |
Registered User
Join Date: Jan 2012
Location: Mesopotamia
Posts: 2,587
|
Quote:
in my opinion for icl make it MT and for msvc make it MD
__________________
See My Avisynth Stuff |
|
28th November 2016, 10:58 | #2631 | Link | ||
Join Date: Mar 2006
Location: Barcelona
Posts: 5,034
|
Quote:
1. It consumes less system resources when the DLL is loaded multiple times 2. See this article on MSDN, particularly these paragraphs: Quote:
__________________
Groucho's Avisynth Stuff Last edited by Groucho2004; 28th November 2016 at 11:49. Reason: Added more info |
||
28th November 2016, 11:14 | #2632 | Link |
Join Date: Mar 2006
Location: Barcelona
Posts: 5,034
|
I'd like to know how you came to that assessment. The Intel compiler uses the same libraries as the MS compiler and therefore requires the same runtimes (and additional Intel runtime libs).
__________________
Groucho's Avisynth Stuff |
28th November 2016, 12:45 | #2634 | Link | |
Registered User
Join Date: Oct 2014
Posts: 268
|
Quote:
Not always true these days with the side-by-side system. Look at the side of the WinSxS folder, a lot of versions of the same DLL files are kept there just to prevent the old Win95/98 DLL hell problem . |
|
28th November 2016, 14:06 | #2635 | Link |
Join Date: Mar 2006
Location: Barcelona
Posts: 5,034
|
That nightmare was abandoned by MS with the introduction of VS2010. It's only relevant for VS2005/8.
__________________
Groucho's Avisynth Stuff |
5th December 2016, 16:14 | #2636 | Link |
Registered User
Join Date: Jan 2014
Posts: 2,314
|
O.K., as we have MvTools 10-16 bit, RgTools 10-16bit + float + planar RGB, let's get back to Avisynth+.
For those who can't wait until I prepare a proper release and documentation, please find here a r2337 test build. edit: replaced the link to the latest dev version http://www.mediafire.com/file/h6nlac...splus-r2337.7z Changes since r2294: 20161208 r2337dev
20161207 r2333dev
20161206 r2331dev
20161205 r2327dev
20161201 r2322dev
20161120:
20161116
edit: test version updated Last edited by pinterf; 8th December 2016 at 18:24. Reason: new build, r2337 |
5th December 2016, 16:18 | #2637 | Link |
German doom9/Gleitz SuMo
Join Date: Oct 2001
Location: Germany, rural Altmark
Posts: 6,781
|
How much faster could "benchmark" scripts like QTGMC be when optimized for all these new features? Just starting with support of planar YUV with fine chroma subsampling...
|
6th December 2016, 09:11 | #2639 | Link | |
Registered User
Join Date: Jan 2014
Posts: 2,314
|
Quote:
http://forum.doom9.org/showpost.php?...postcount=1148 However there is an error window: Code:
Error parsing ArrayGet plugin parameters: unknown character 'a' Error parsing ArrayGet plugin parameters: unknown character 'a' Error parsing ArraySize plugin parameters: unknown character 'a' Error parsing BlankClip plugin parameters: unknown character 'a' Error parsing BlankClip plugin parameters: unknown character 'a' Exception WindowsError: 'exception: access violation reading 0x4049D7D0' in <bound method AVS_Value.__del__ of [None, None, None]> ignored Exception WindowsError: 'exception: access violation reading 0x4030FFF0' in <bound method AVS_Value.__del__ of [None, None, None]> ignored As for the exceptions, I cannot tell what they are meaning. Any other experiences? Edit: regarding the exceptions. it must be a C interface that may interfere with the array handling. Array-type AVSValue now copies all array elements when assigned to another AVSValue. The old AVSValue stores only a pointer on the child AVSValue elements. When AVSValue is free'd the elements are still held in memory and won't get freed. For the new behaviour, AVSValue can hold elements that can also be arrays, they can even be nested. All AVSValue elements of an array are copied, not just the reference. When a child element is array, it is also copied, etc.... What happens when an array-type AVSValue is freed? Avisynth core now resursively frees up all AVSValue within an array, because it can do it safely, as the array creation and copy ensures that the elements were really copied. I guess that when C Interface uses avs_release_value, this interferes with this logic. AvsPMod allocates the main array-type AVSValue, allocates array element AVSValues on its own. When avs_release_value is called, it tries to free up array elements that were not allocated by avs core. It's not clear for me, what happens, never used C interface, but this is my assumption, I have to investigate this. Last edited by pinterf; 6th December 2016 at 14:16. Reason: Was too wide |
|
6th December 2016, 14:15 | #2640 | Link |
Registered User
Join Date: Jan 2014
Posts: 2,314
|
Ok, let's try this one:
http://www.mediafire.com/file/90d7qa...splus-r2331.7z Changes since r2294: see above. Last change: 20161206 r2331dev
Last edited by pinterf; 7th December 2016 at 08:35. Reason: r2331 |
Thread Tools | Search this Thread |
Display Modes | |
|
|