AviSynth 2.6.0 [May 31st, 2015] - Page 2

StainlessS · 12th June 2015, 08:12

Most informative, thanx innocenat

Wilbert · 13th June 2015, 14:02

Quote:

Originally Posted by StainlessS

Great stuff guys, lovely to have Officially stable v2.6

Is there a published machine minimum requirement for v2.6 (or v2.58 for that matter, on windows) ?

Also,

from v2.6 docs

Quote:

Future plans
AviSynth v2.61:
This version will use the free Microsoft compiler. It will be feature identical to 2.60 i.e. Source new syntax changes only!

Has it been decided yet which of the free compilers will be chosen (there are a few of them) ?

Thanxs

v2.61 will have the following features/updates:

support for 2K5, 2K8 and 2K10.
external libraries will be updated and converted to plugins.
convert_a.asm will be converted to softwire.
rewrite exception handling.
bugfixes.

As for your other question. What innocenat said. The resizers, but also layer and mask don't have c/c++ equivalents (they have minimal mmx).

StainlessS · 13th June 2015, 14:19

Dank u vel Wilbert

RRD · 18th June 2015, 10:25

Is it normal that Version() reports

Code:

AviSynth 2.60, build: Mar 31 2015 [16:38:54]
© 2000-2014 Ben Rudiak-Gould, et al.
http://www.avisynth.nl

? While I understand that no recent change was made to AviSynth, it can be very confusing for users who may think they downloaded an older version.

Groucho2004 · 18th June 2015, 10:54

Quote:

Originally Posted by RRD

Is it normal that Version() reports

Code:

AviSynth 2.60, build: Mar 31 2015 [16:38:54]
© 2000-2014 Ben Rudiak-Gould, et al.
http://www.avisynth.nl

? While I understand that no recent change was made to AviSynth, it can be very confusing for users who may think they downloaded an older version.

I'm not sure if it was an oversight or intentional to not rebuild avisynth.dll (and other components) for the release. The problem with the info from "Version()" is that it just uses a couple of compiler macros to reflect the build time and date. The version info is a bit ambiguous to some.

I think the copyright notice should also have been updated to "© 2000-2015 ...".

Wilbert · 18th June 2015, 18:54

It was intentional. I understand it might be confusing.

real.finder · 28th July 2015, 20:45

I note that DevIL.dll in AviSynth_260.exe is too old

Groucho2004 · 28th July 2015, 21:07

Quote:

Originally Posted by real.finder

I note that DevIL.dll in AviSynth_260.exe is too old

Too old for what? You're free to update to v1.78 from here, it should be compatible with AVS 2.6. If you do so, use the non-Unicode, 32 Bit version for Windows.

real.finder · 28th July 2015, 22:23

Quote:

Originally Posted by Groucho2004

Too old for what? You're free to update to v1.78 from here, it should be compatible with AVS 2.6. If you do so, use the non-Unicode, 32 Bit version for Windows.

I already did this from years, I mention this for upcoming releases

Groucho2004 · 28th July 2015, 23:06

Quote:

Originally Posted by real.finder

I already did this from years, I mention this for upcoming releases

From what I recall, DevIL 1.7.8 was not included because of its dependency on the dreaded msvc*80 DLLs.

Wilbert · 29th July 2015, 20:56

Quote:

Originally Posted by Groucho2004

From what I recall, DevIL 1.7.8 was not included because of its dependency on the dreaded msvc*80 DLLs.

That's indeed the reason.

Overdrive80 · 3rd August 2015, 16:58

Hey, I have installed win10 and autoload plugins in avisynth not working now, did you know?

Groucho2004 · 3rd August 2015, 17:49

Quote:

Originally Posted by Overdrive80

Hey, I have installed win10 and autoload plugins in avisynth not working now, did you know?

The detail in your bug report is staggering.

Clean Win10 install or upgrade? If upgrade, did you (have to) re-install Avisynth?
With which software are you testing this and are there any error messages? Did you check the registry for the auto-load directory pointer ("PluginDir2_5" in Software/Avisynth in HKCU or HKLM)?

Overdrive80 · 3rd August 2015, 21:35

Quote:

Originally Posted by Groucho2004

The detail in your bug report is staggering.

Clean Win10 install or upgrade? If upgrade, did you (have to) re-install Avisynth?
With which software are you testing this and are there any error messages? Did you check the registry for the auto-load directory pointer ("PluginDir2_5" in Software/Avisynth in HKCU or HKLM)?

Really its not bug report but you are right.

I upgrade from win7. I have reinstalled avisynth. I have testing with vdub. No, I dont check registry, could you put complete direction for creating reg file??

Thanks, bro.

Groucho2004 · 3rd August 2015, 21:45

Quote:

Originally Posted by Overdrive80

No, I dont check registry, could you put complete direction for creating reg file??

The installer is supposed to write the reg entry. Just check if it's there.

Overdrive80 · 4th August 2015, 07:52

Keys registry was missing. I solved with:

Code:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\AviSynth]
@="C:\\Program Files (x86)\\AviSynth 2.5\\plugins"
"plugindir2_5"="C:\\Program Files (x86)\\AviSynth 2.5\\plugins"

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\AviSynth]
@="C:\\Program Files (x86)\\AviSynth 2.5"
"plugindir2_5"="C:\\Program Files (x86)\\AviSynth 2.5\\plugins"

Thanks and apologize for disturbing.

Groucho2004 · 4th August 2015, 08:06

Quote:

Originally Posted by Overdrive80

Keys registry was missing. I solved with:

Code:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\AviSynth]
@="C:\\Program Files (x86)\\AviSynth 2.5\\plugins"
"plugindir2_5"="C:\\Program Files (x86)\\AviSynth 2.5\\plugins"

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\AviSynth]
@="C:\\Program Files (x86)\\AviSynth 2.5"
"plugindir2_5"="C:\\Program Files (x86)\\AviSynth 2.5\\plugins"

Thanks and apologize for disturbing.

As I mentioned, the installer should have written this entry. It seems that you (or rather the installer) did not have sufficient rights to write it. I think you need admin rights to write to HKLM.

Overdrive80 · 4th August 2015, 08:19

Quote:

Originally Posted by Groucho2004

As I mentioned, the installer should have written this entry. It seems that you (or rather the installer) did not have sufficient rights to write it. I think you need admin rights to write to HKLM.

I ever execute with admin rights if fails. --

kuchikirukia · 9th August 2015, 03:36

Reasonable speedup in QTGMC. 12.23fps --> 13.03 in AVSMeter on this 480p source. Xeon X3450, Win10. Though I get exactly the same in 2.6MT single-threaded.

Groucho2004 · 9th August 2015, 08:11

Quote:

Originally Posted by kuchikirukia

Reasonable speedup in QTGMC. 12.23fps --> 13.03 in AVSMeter on this 480p source. Xeon X3450, Win10.

What exactly did you compare?

Quote:

Originally Posted by kuchikirukia

Though I get exactly the same in 2.6MT single-threaded.

Which is to be expected:

Quote:

Originally Posted by SEt

4. Short guide to SetMTMode
SetMTMode is the command that switches Avisynth into MT mode. Without it MT Avisynth works like the usual one.

12th June 2015, 08:12	#21 \| Link
StainlessS HeartlessS Usurer Join Date: Dec 2009 Location: Over the rainbow Posts: 10,980	Most informative, thanx innocenat __________________ 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 ???

13th June 2015, 14:19	#23 \| Link
StainlessS HeartlessS Usurer Join Date: Dec 2009 Location: Over the rainbow Posts: 10,980	Dank u vel Wilbert __________________ 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 ???

18th June 2015, 10:25	#24 \| Link
RRD Registered User Join Date: Nov 2009 Location: France Posts: 20	Is it normal that Version() reports Code: AviSynth 2.60, build: Mar 31 2015 [16:38:54] © 2000-2014 Ben Rudiak-Gould, et al. http://www.avisynth.nl ? While I understand that no recent change was made to AviSynth, it can be very confusing for users who may think they downloaded an older version.

28th July 2015, 20:45	#27 \| Link
real.finder Registered User Join Date: Jan 2012 Location: Mesopotamia Posts: 2,587	I note that DevIL.dll in AviSynth_260.exe is too old __________________ See My Avisynth Stuff

3rd August 2015, 16:58	#32 \| Link
Overdrive80 Anime addict Join Date: Feb 2009 Location: Spain Posts: 673	Hey, I have installed win10 and autoload plugins in avisynth not working now, did you know? __________________ Intel i7-6700K + Noctua NH-D15 + Z170A XPower G. Titanium + Kingston HyperX Savage DDR4 2x8GB + Radeon RX580 8GB DDR5 + ADATA SX8200 Pro 1 TB + Antec EDG750 80 Plus Gold Mod + Corsair 780T Graphite

18th June 2015, 18:54	#26 \| Link
Wilbert Moderator Join Date: Nov 2001 Location: Netherlands Posts: 6,364	It was intentional. I understand it might be confusing.

4th August 2015, 07:52	#36 \| Link
Overdrive80 Anime addict Join Date: Feb 2009 Location: Spain Posts: 673	Keys registry was missing. I solved with: Code: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\AviSynth] @="C:\\Program Files (x86)\\AviSynth 2.5\\plugins" "plugindir2_5"="C:\\Program Files (x86)\\AviSynth 2.5\\plugins" [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\AviSynth] @="C:\\Program Files (x86)\\AviSynth 2.5" "plugindir2_5"="C:\\Program Files (x86)\\AviSynth 2.5\\plugins" Thanks and apologize for disturbing. __________________ Intel i7-6700K + Noctua NH-D15 + Z170A XPower G. Titanium + Kingston HyperX Savage DDR4 2x8GB + Radeon RX580 8GB DDR5 + ADATA SX8200 Pro 1 TB + Antec EDG750 80 Plus Gold Mod + Corsair 780T Graphite

9th August 2015, 03:36	#39 \| Link
kuchikirukia Registered User Join Date: Oct 2014 Posts: 476	Reasonable speedup in QTGMC. 12.23fps --> 13.03 in AVSMeter on this 480p source. Xeon X3450, Win10. Though I get exactly the same in 2.6MT single-threaded. Last edited by kuchikirukia; 9th August 2015 at 03:44.