Log in

View Full Version : AviSynth 2.6.0 RC3 [Apr 15th, 2015]


Wilbert
19th April 2015, 15:50
AviSynth 2.6.0 RC3 (https://sourceforge.net/projects/avisynth2/files/AviSynth_Alpha_Releases/) is released. Changelist with respect to RC1:

Additions
=========
* TCPDeliver, 2.6 plugin, support all pixel types. (Wilbert)

Bugfixes
========
* Fixed missing I420 in DirectShowSource pixel type error message.

Changes
=======
* New default directory, $PROGRAMFILES\AviSynth. But it will continue to default to the previous intall dir and will use the previously existing plugin dir.
* Do a full uninstall and answer YES to clearing the registry to reset to all the new defaults.
* Menu dir is now $SMPROGRAMS\AviSynth. Will rename "AviSynth 2.5" to "AviSynth".
* Cache only uses extended hints if rev 6 and above. Counter bad use in rev 5.

Please test the new color formats in tcpsource/tcpdeliver and the new install routines, and report your findings. If there are none we will do a final release.

As can be seen, the frame offsets and data sizes being size_t are not reverted. Ianb's response was

"We cannot do VFB per plane _AND_ do AVS64 without this change. The __int64's and double's in AVSValues break things worse.
Much bigger issue is official AVS64 is compiled with GCC. M$64 C++ dll's are incompatible with GCC64 C++ just like GCC32 dll's are incompatible with M$32 C++ dll's, hence Kevin Atkinson's C interface."

I want to leave this discussion at this.

manolito
19th April 2015, 17:54
Thanks a lot... :thanks:

Quick question: Does the RC3 incorporate the new TimeStretch version from the SoundTouch library (the version you added to a hotfix for RC2) ?


Cheers
manolito

Wilbert
19th April 2015, 18:12
No it doesn't. That's scheduled for 2.61. Release candidates are not meant for adding new functionality.

manolito
19th April 2015, 18:48
Thanks...
Can you compile another hotfix AviSynth.dll?

ChiDragon
21st April 2015, 02:32
Some time ago, I noticed that Tweak doesn't pop up any error if you use settings that are outside of the ranges listed in the doc. Bug or "feature"?

Ex: Tweak(hue=99999,sat=99999,bright=99999,cont=99999)

StainlessS
21st April 2015, 02:56
Some time ago, I noticed that Tweak doesn't pop up any error if you use settings that are outside of the ranges listed in the doc. Bug or "feature"?

Ex: Tweak(hue=99999,sat=99999,bright=99999,cont=99999)
Silently limiting is not so unusual (when the limiting is perhaps preferable to an error alert).
Where serious consequences could occur, might be more usual to produce alert and demand script edit.

Do you think it to be a bug (it will obviously be deliberate) ?

Wilbert
21st April 2015, 21:02
The parameters starthue, endhue, minsat, maxsat and p are checked for valid input.

The processed pixels are clamped to [0,255] for coring=false and to [16,235] for coring=true. No other limiting is done.

Motenai Yoda
24th April 2015, 15:48
as manolito wrote, can you update some external libs?
also I hope there will be enough room for some improvement/additions, ie gamma aware/dither for resizers.

Wilbert
27th April 2015, 18:05
as manolito wrote, can you update some external libs?
I will try to make a plugin out of it (for soundtouch) so that you don't have to wait for 2.61.
also I hope there will be enough room for some improvement/additions, ie gamma aware/dither for resizers.
Not sure what you are asking here. Gamma aware resizers will come when we will add 16 bit per color. It's a bit tricky though, i'm still not sure what an acceptable way is to do it directly in YCbCr (since it's an RGB concept).

manolito
27th April 2015, 22:21
I will try to make a plugin out of it (for soundtouch) so that you don't have to wait for 2.61.

That's very nice of you, thanks in advance... :thanks:

StainlessS
28th April 2015, 15:35
I added Tau() as a stir of a friend who is an avid Tau'ist, who I regularly poke with "The area of a circle is ∏rē". So I will take it out.

The ill fated Tau is now deceased, need remove from docs.

EDIT: Also, this is unclear

Ceil | | Ceil(float)
Converts from float to int (round up on any fractional amount).
Examples:
Ceil(1.2) = 2.0
Ceil(1.6) = 2.0
Ceil(-1.2) = -1 # -1.0
Ceil(-1.6) = -1 # -1.0

Returns non fractional type float.

StainlessS
29th April 2015, 22:21
@Wilbert, (just noticed your edit)
Tau, Avisynth Functions/ Internal Functions/ Numeric Functions.
(just after Pi)

luquinhas0021
16th May 2015, 01:47
The AviSynth 2.6 RC3 doesn't run the nnedi3 and Spline plug-ins. Both of two are, theoretically, compatible with it.

Groucho2004
16th May 2015, 09:45
The AviSynth 2.6 RC3 doesn't run the nnedi3 and Spline plug-ins. Both of two are, theoretically, compatible with it.
"doesn't run plugin" is useless and nobody can help you with a report like that.
What software do feed the script? Where did you download the plugins? If there is an error message, what is it?

manolito
16th May 2015, 10:24
Just tested under WinXP using AviSynth 2.60 RC3 (and also the ICL version of avisynth.dll). Nnedi3 version 0.9.4.0 downloaded from Tritical's site.

Simple deinterlacing script:
MPEG2Source("I:\Movies\test.D2V")
AssumeTFF()
ConvertToYV12(interlaced=true)
yadifmod(edeint=nnedi3())


No problems, works perfectly...


Cheers
manolito

Sparktank
16th May 2015, 16:33
I was going to ask more about this (spline plugin), too.

Spline100/Spline144 plugin works normally, on my end.
I use it all the time in AvsPmod and [MPC-HC+FFDShow/+SVP].

EDIT:
I've also uninstalled the old version before installing the RC versions to use the new directory path.
I moved all plugins to new directory and haven't found any plugins to be broken (yet; probably won't either).

Wilbert
16th May 2015, 16:52
EDIT:
I've also uninstalled the old version before installing the RC versions to use the new directory path.
I moved all plugins to new directory and haven't found any plugins to be broken (yet; probably won't either).
Of course it's always save to uninstall the old version, but it shouldn't be necessary.
It could be that we messed up, luquinhas0021 installed RC3 over the old one (but specifying a different plugin folder, that is supposed too work), and that is still looking at the old plugin folder. I hope it is clear what i mean. But i can't tell whether something like that is indeed the issue (of course he would have troubles loading all his plugins in his autoloading plugin folder).

If that is the case we need to know how to replicate this.

Sparktank
16th May 2015, 17:03
Of course it's always save to uninstall the old version, but it shouldn't be necessary.
It could be that we messed up, luquinhas0021 installed RC3 over the old one (but specifying a different plugin folder, that is supposed too work), and that is still looking at the old plugin folder. I hope it is clear what i mean. But i can't tell whether something like that is indeed the issue (of course he would have troubles loading all his plugins in his autoloading plugin folder).

If that is the case we need to know how to replicate this.

I get what you mean and was going to mention that but wasn't sure how to say it.

I think I'll give it a dry run. Been wanting to since I read about the new directory (but, as I had settled on uninstalling I felt it safe until someone else brings it up and goes throug the hassle first :devil:).
Uninstall RC3, install old one, install new over old and see what happens.
I'll plugins to separate folder that's not in system/variable path and keep only Spline since it would be easiest to run.
And try multiple scenarios.

...after coffee.


EDIT: Maybe I don't know what you mean. :confused:

I've tried installing over versions and uninstalling and reinstalling.
I've tried from 2.5.8 to Alpha 5 and then to RC1/2/3.
I've tried from 2.5.8 to RC3.
I even tried just RC3.
I've tried MT (2.6.0 MT [2015.02.20]).
I've even tried ICL (RC3 (ICL10) (2.6.0.6)).

Avisynth DLL location: C:\Windows\SysWOW64\avisynth.dll
Plugin directory: C:\Program Files (x86)\AviSynth 2.5\plugins

C:\Program Files (x86)\AviSynth 2.5\plugins\SplineResize.dll
C:\Program Files (x86)\AviSynth\plugins

Installing RC3 over old installs will just use old 2.5 directory.
Installing just RC3 creates/uses new directory.
I've moved the Spline plugin around and tried in AvsPmod and it all works.
Even when both directories were present, I tried moving plugin around and it still worked.

Script:
SetMemoryMax(512)
#SetMTMode(2)
LoadPlugin("C:\AVS\dgdecnv2049\DGDecodeNV.dll")
DGSource("E:\MakeMKV\Sherlock_Holmes_A_Game_of_Shadows.dgi", crop_b=148, crop_t=140)
Spline144Resize(1296, 540)
#SetMTmode(1)
#Distributor()

AvsPmod, MPC-HC, VirtualDub.

Every scenario I tried worked as it should.
Could not get Spline plugin to not work.

I'll sit by and see what happens next.

Wilbert
16th May 2015, 21:28
Yes, i was wrong above. The bevaviour you say is correct:
Installing RC3 over old installs will just use old 2.5 directory.
Installing just RC3 creates/uses new directory.
So installing RC3 won't change an existing plugin folder (the reg value; you can find the path in the menu > AviSynth > Plugin Directory). When there is no plugin folder (because you start from scratch or you deleted the registery pointer upon uninstall) it will point to the new install folder.

@luquinhas0021, what is the path of the trouble plugins? Which folder is 'menu > AviSynth > Plugin Directory' pointing to?

Aktan
17th May 2015, 23:51
Maybe I'm doing something wrong, but I did Version() on this and it says it's still the March 31th 2015 version. Same goes with the DLL itself. I've redownloaded and it's still the same. Did I miss something?

Edit: To clarify, I downloaded it here: http://sourceforge.net/projects/avisynth2/files/AviSynth_Alpha_Releases/AVS%202.6.0%20RC%203%20%5B150419%5D/AviSynth_150419.exe/download

foxyshadis
18th May 2015, 04:11
There is no change to avisynth at all, the only change since RC2 was in the installer. You have the latest. (In fact, no one with RC2 needs RC3.)

Aktan
18th May 2015, 04:27
There is no change to avisynth at all, the only change since RC2 was in the installer. You have the latest. (In fact, no one with RC2 needs RC3.)

Thanks for the info!

LigH
31st May 2015, 08:26
Now that AviSynth 2.60 went "final" (hooray!), new thread by Wilbert?

Seedmanc
31st May 2015, 10:47
Where's the changelog?

Reel.Deel
31st May 2015, 11:04
Where's the changelog?

Here: http://sourceforge.net/projects/avisynth2/files/AviSynth%202.6/AviSynth%202.6.0/

It's also included in the download.

stax76
31st May 2015, 11:13
is AviSynth_260.exe x86 only or does it contain a x64 version?

Patman
31st May 2015, 11:21
@stax
I think avisynth 2.6 is x86 only

l33tmeatwad
2nd June 2015, 17:40
Uhh, so are they ever gonna fix the summary page to show the latest download on sourceforge?

Groucho2004
2nd June 2015, 18:19
Uhh, so are they ever gonna fix the summary page to show the latest download on sourceforge?
The SF summary page does list the 2.6 release.

l33tmeatwad
2nd June 2015, 19:55
The SF summary page does list the 2.6 release.Yeah...that's pretty much what I said.

Groucho2004
2nd June 2015, 21:11
Yeah...that's pretty much what I said.
Something must have been lost in translation then...

l33tmeatwad
2nd June 2015, 22:23
I guess to clarify, when you visit this page:

https://sourceforge.net/projects/avisynth2/

The main download link is still to AviSynth 2.6 Alpha 3 and not to the latest release.

Wilbert
2nd June 2015, 22:27
It says AviSynth_260.exe now (at least for me). Yes a few hours ago it said something else, but i don't know how it got updated since i didn't do anything.

Groucho2004
2nd June 2015, 22:34
I guess to clarify, when you visit this page:

https://sourceforge.net/projects/avisynth2/

The main download link is still to AviSynth 2.6 Alpha 3 and not to the latest release.
It reads "AviSynth_260.exe" for me (and has for several hours). It's your browser. Empty browser cache, reload page.

l33tmeatwad
2nd June 2015, 22:48
It reads "AviSynth_260.exe" for me (and has for several hours). It's your browser. Empty browser cache, reload page.One of the servers where I'm at must have that page cached, I just wanted to make sure it was updated and apparently it is.