Avisynth+ - Page 106

ultim · 13th July 2016, 08:38

Quote:

Originally Posted by TurboPascal7

Does it even have to do anything with the intrinsics there? Looks completely unnecessary (like most of the C++ duhuhu).

Those shuffles around line 458 need a compile-time constant expression, which is why lines 443-444 were made a constexpr, I suppose. Removing the constexpr needs different templating, different intrinsics, or a condition added in the depths of those loops...

TurboPascal7 · 13th July 2016, 08:42

Quote:

Originally Posted by ultim

Those shuffles around line 458 need a compile-time constant expression, which is why lines 443-444 were made a constexpr, I suppose. Removing the constexpr needs different templating, different intrinsics, or a condition added in the depths of those loops...

Welp. Imo just copypaste the whole function into three different functions for different sizeof(T) and the problem goes away on its own. The code will be better too.

ultim · 13th July 2016, 08:44

Quote:

Originally Posted by feisty2

Guess it's probably not a good idea to stay vs2010 or 2013, the latest c++ standard is c++14 so..
And vs2015 community is free anyways, what's the point of getting stuck at square one

Hopefully not for long.

VS2010-support is only for the public headers, not for compiling Avs+ core itself, so that you have a larger choice of compilers when writing your plugins.

VC2013 is the oldest supported compiler for compiling the core, and is only because of Wine, as apparently it still has some problems with the VC2015 runtimes. As soon as Wine gets with the times, I have no problem in dropping VC2013 support.

RazorBurn · 13th July 2016, 12:20

Does someone here have links to Avisynth+MT r2005?

fAy01 · 13th July 2016, 13:08

Quote:

Originally Posted by RazorBurn

Does someone here have links to Avisynth+MT r2005?

http://avs-plus.net/builds

2043 is the latest.

tormento · 13th July 2016, 20:10

Quote:

Originally Posted by fAy01

http://avs-plus.net/builds

2043 is the latest.

OMG... did not noticed it.

Changelog?

ryrynz · 13th July 2016, 23:42

Quote:

Originally Posted by tormento

Changelog?

https://github.com/AviSynth/AviSynthPlus/commits/MT

Will 1858 be the last unofficial build with legacy plugin compatibility?

MysteryX · 14th July 2016, 01:26

Quote:

Originally Posted by ryrynz

https://github.com/AviSynth/AviSynthPlus/commits/MT

Will 1858 be the last unofficial build with legacy plugin compatibility?

Just to be clear, the only plugins that are incompatible are those that used "env2" while ignoring the warning not to use it. Mostly to register their MT mode. Only a few plugins are doing that.

RazorBurn · 14th July 2016, 02:30

Quote:

Originally Posted by fAy01

http://avs-plus.net/builds

2043 is the latest.

Huge Thanks.. Bookmarked..!!

ryrynz · 14th July 2016, 03:44

Quote:

Originally Posted by fAy01

http://avs-plus.net/builds

If I install DirectShowSource.dll from link above to the latest build in my plugins folder I get a C++ exception when using avisynth+ffdshow.
I don't believe I'll use it anyway and have deleted it, but can someone quickly detail what features it provides?

Reel.Deel · 14th July 2016, 04:21

Quote:

Originally Posted by ryrynz

If I install DirectShowSource.dll from link above to the latest build in my plugins folder I get a C++ exception when using avisynth+ffdshow.
I don't believe I'll use it anyway and have deleted it, but can someone quickly detail what features it provides?

The latest AviSynth+ releases incorporate pinterf's changes, as well as some bugs fixes, and also introduced support for 16/32 bit YUV formats. High bit depth is still a work-in-progress but there's already a handful of internal filters that support the new formats. Ultim is working on a longstanding MT issue and also mentioned that some MT optimizations are coming.

Quote:

Originally Posted by ryrynz

Will 1858 be the last unofficial build with legacy plugin compatibility?

There's nothing to worry about here, AviSynth+ still supports all the plugins it always has. The issue that MysteryX mentioned has been taken care of, the few affected plugins have been fixed and are working correctly. The latest nnedi3 (v0.9.4.22) is the only plugin currently not working but a fix is coming soon. Use an older version for the mean time.

qyot27 · 14th July 2016, 05:13

DirectShowSource is a source filter of last resort, because DirectShow support of X or Y format is often unstable (and the filter isn't frame accurate in general). Pretty much every other source filter does a better job for whatever format(s) they're designed to open, leaving DSS for extreme edge cases.

It was the only general-purpose source filter prior to 2007, but ever since FFmpegSource (and especially since FFMS2 and LSMASHSource/LwLibavSource), its importance has shrunk to a minimum.

Because it was one of the few plugins that had used IScriptEnv2, newer versions can only be used by newer versions of the AviSynth+ core. Pairing DirectShowSource.dll from AviSynth+ r2022 or r2043 with the core AviSynth.dll from r1858 or prior will, of course, fail spectacularly.

pinterf · 18th July 2016, 20:46

Good evening.
New functions ported to 16 bit/float.

Info
ShowFrameNumber / ShowSMPTE / ShowTime
Subtitle

Info() additions:

display the name of the high bit-depth color spaces instead of Unknown color space.
display AVX CPU flag if detected.

LigH · 18th July 2016, 23:26

Indeed, a good evening!

real.finder · 19th July 2016, 09:44

does avs+ has same avs limit of 50 active plugins at one time?

Chikuzen · 19th July 2016, 12:52

Quote:

Originally Posted by real.finder

does avs+ has same avs limit of 50 active plugins at one time?

IIRC, the limit was gone after 2.57.
Both avs2.6 and avs+ has no imit of number of loading plugins.

real.finder · 19th July 2016, 13:11

Quote:

Originally Posted by Chikuzen

IIRC, the limit was gone after 2.57.
Both avs2.6 and avs+ has no imit of number of loading plugins.

it still existing in 2.6, I see it in some of my tests in complex script

Groucho2004 · 19th July 2016, 13:34

Quote:

Originally Posted by real.finder

it still existing in 2.6, I see it in some of my tests in complex script

Indeed. In plugin.cpp (2.6 and also 2.6.1):

Code:

enum { max_plugins=50 };

The plugin loading in AVS+ is quite different and from what I've seen, there's no plugin limit in the code (or maybe I didn't look thoroughly).

Myrsloik · 19th July 2016, 14:00

I will just put this link here. Dlls are fun.

ultim · 19th July 2016, 20:58

Quote:

Originally Posted by Groucho2004

Indeed. In plugin.cpp (2.6 and also 2.6.1):

Code:

enum { max_plugins=50 };

The plugin loading in AVS+ is quite different and from what I've seen, there's no plugin limit in the code (or maybe I didn't look thoroughly).

In Avs+ there's no limit.

18th July 2016, 20:46	#2113 \| Link
pinterf Registered User Join Date: Jan 2014 Posts: 2,314	Good evening. New functions ported to 16 bit/float. Info ShowFrameNumber / ShowSMPTE / ShowTime Subtitle Info() additions: display the name of the high bit-depth color spaces instead of Unknown color space. display AVX CPU flag if detected. __________________ AviSynth+ on github, Other repos: RgTools, Masktools2, MvTools2, TIVTC, Average

18th July 2016, 23:26	#2114 \| Link
LigH German doom9/Gleitz SuMo Join Date: Oct 2001 Location: Germany, rural Altmark Posts: 6,783	Indeed, a good evening! __________________ New German Gleitz board MediaFire: x264 \| x265 \| VPx \| AOM \| Xvid

19th July 2016, 09:44	#2115 \| Link
real.finder Registered User Join Date: Jan 2012 Location: Mesopotamia Posts: 2,587	does avs+ has same avs limit of 50 active plugins at one time? __________________ See My Avisynth Stuff

19th July 2016, 14:00	#2119 \| Link
Myrsloik Professional Code Monkey Join Date: Jun 2003 Location: Kinnarps Chair Posts: 2,555	I will just put this link here. Dlls are fun. __________________ VapourSynth - proving that scripting languages and video processing isn't dead yet

13th July 2016, 12:20	#2104 \| Link
RazorBurn Registered User Join Date: Aug 2014 Posts: 14	Does someone here have links to Avisynth+MT r2005?

14th July 2016, 05:13	#2112 \| Link
qyot27 ...? Join Date: Nov 2005 Location: Florida Posts: 1,420	DirectShowSource is a source filter of last resort, because DirectShow support of X or Y format is often unstable (and the filter isn't frame accurate in general). Pretty much every other source filter does a better job for whatever format(s) they're designed to open, leaving DSS for extreme edge cases. It was the only general-purpose source filter prior to 2007, but ever since FFmpegSource (and especially since FFMS2 and LSMASHSource/LwLibavSource), its importance has shrunk to a minimum. Because it was one of the few plugins that had used IScriptEnv2, newer versions can only be used by newer versions of the AviSynth+ core. Pairing DirectShowSource.dll from AviSynth+ r2022 or r2043 with the core AviSynth.dll from r1858 or prior will, of course, fail spectacularly.