AviSynth+ thread Vol.2

[MeteorRain]

There was already C++AMP. I used that a few years ago but it's still not popular till today.

[pinterf]

Originally Posted by kedautinh12

I find out a fork from maki's MPEG2DecPlus 0.1.1 on github, is it added v8 interface or not??
https://github.com/299792458m/DGIndex_mod

Note that v8 update will only be necessary if plugin is using the non-finalized IScriptEnvironment2 Avisynth+ interface calls.

Plugins which were not relying on IScriptEnvironment2 will be working fine.

[jpsdr]

Originally Posted by FranceBB

And... sure, you could have just been sitting on the couch watching TV all day like many people are doing during this pandemic...

Yes i did... A lot of animes, some old 80's SF/Heroic Fantasy cheaped movies, and also reading manga and comics...

[pinterf]

My today's recommendation: The Plague by Albert Camus. I've read it in last November, pandemic started in December.

[StainlessS]

Dont blame your self P, you can in no way be held responsible for this bloody lockdown, coincidence only, really.

EDIT: to below.
David Attenborough, yep, on much safer ground there

[pinterf]

Originally Posted by StainlessS

Dont blame your self P, you can in no way be held responsible for this bloody lockdown, coincidence only, really.

Yep, though my currently finished book is neutral, I hope (Zoo Quest by David Attenborough)

[Reel.Deel]

Originally Posted by pinterf

I wonder if they are simply recompiled or adaptively using the frame-property preserving NewVideoFrameP as well. So are they are good only for the new v8 or can work with any former avs versions?

Yes, git is a must have. On one hand now we have to download them and make manual source-code comparison to see what has been changed.

When they are getting new features (such as 10+ bits) in the future the sources have to be put back to git. And because of the credits and source history they have to be forked from the original repository and the new developer must either forget or reinvent these "offline" changes.

I'd encourage everyone to use github in order not to break development history.

Fork, modify, commit, document, release.

Ask, and you shall receive: https://github.com/Asd-g?tab=repositories

asd created a GitHub account, the modified plugins from chickuzen are there. by looking at the commits I don't think they are just recompiled, then again I am no programmer .


******
asd: if you are reading this, I just want to say thank you for all of the plugins you've uploaded on the wiki. Please check the wiki talk page in the coming days, I have a question for you. Thanks again

[pinterf]

Originally Posted by Reel.Deel

Ask, and you shall receive: https://github.com/Asd-g?tab=repositories

asd created a GitHub account, the modified plugins from chickuzen are there. by looking at the commits I don't think they are just recompiled, then again I am no programmer .

Great, thank you, Asd-g, you spent quite a few hours with the updates.

[kedautinh12]

Asd-g, if you are reading this post, can port back there plugins from vapoursynth
https://forum.doom9.org/showpost.php...&postcount=841

[tormento]

Originally Posted by kedautinh12

I find out a fork from maki's MPEG2DecPlus 0.1.1 on github, is it added v8 interface or not??
https://github.com/299792458m/DGIndex_mod

This for sure is, looking at sources.

[videoh]

What is this "v8 interface" you are talking about?

[pinterf]

Originally Posted by videoh

What is this "v8 interface" you are talking about?

It's still in a development branch called neo.

IScriptEnvironment has been extended with some new functions which broke those plugins which were using avs+ specific IScriptEnvironment2. So such plugins have to be rebuilt with adaptively using new IScriptEnvironment functions.

The biggest change is the frame property support.
Just like in VS.
It is only the framework. Interface support and fp passing throughout all internal Avisynth+ plugins.

Ideally every filter in the filter chain has to able to pass frame properties on. Such plugins should use a V8 interface NewVideoFrameP instead of NewVideoFrame. But only if V8 host is detected.

Like this:

Technique is very simple.

Read about the changes:
https://github.com/AviSynth/AviSynth...me_history.txt

Grab new Avisynth headers (at the moment from here):
https://github.com/AviSynth/AviSynthPlus/tree/neo

Check V8 availability on create:
https://github.com/pinterf/TIVTC/blo...rlace.cpp#L261

Use the new feature adaptively
https://github.com/pinterf/TIVTC/blo...lanar.cpp#L169

Or when you have a source filter you can add frame properties just like in VapourSynth.

Obviously it is just a framework it will require many more steps later to use this feature properly and along with specific convertions and rules.

[Myrsloik]

Interesting and familiar looking stuff. What happens with plugins that don't pass along properties? They all just disappear or you use some simple rule to try to pass them along anyway?

[kedautinh12]

Originally Posted by tormento

This for sure is, looking at sources.

I already seen it, thanks

[videoh]

Originally Posted by pinterf

It's still in a development branch called neo.
...
Obviously it is just a framework it will require many more steps later to use this feature properly and along with specific convertions and rules.

Thank you for the explanation. I suppose then it's not something to worry about quite yet as a filter author.

[pinterf]

Originally Posted by Myrsloik

Interesting and familiar looking stuff. What happens with plugins that don't pass along properties? They all just disappear or you use some simple rule to try to pass them along anyway?

Familiar, yes. Thank you in advance, I've never thought that the concept would work in any Avisynth without breaking everything.

Plugins which do not pass properties will unfortunately break the chain.

[videoh]

Is there any documentation of the properties and how to use them? Couldn't make much sense out of it from looking at avisynth.h. Thank you.

[tormento]

Originally Posted by Reel.Deel

asd created a GitHub account, the modified plugins from chickuzen are there. by looking at the commits I don't think they are just recompiled, then again I am no programmer .

How I wish everybody put dll version too in the compiled build.

[Myrsloik]

Originally Posted by pinterf

Familiar, yes. Thank you in advance, I've never thought that the concept would work in any Avisynth without breaking everything.

Plugins which do not pass properties will unfortunately break the chain.

You can't do something like my avisynth compatibility layer? Copy the properties from the input frame in secret?

(of course this in some cases need plugin parameter parsing and a deep knowledge of framerate modifications for plugins that do such things)

[pinterf]

Originally Posted by Myrsloik

You can't do something like my avisynth compatibility layer? Copy the properties from the input frame in secret?

(of course this in some cases need plugin parameter parsing and a deep knowledge of framerate modifications for plugins that do such things)

At the moment I cannot imagine how could I do that in a consistent way with parameter parsing.

Anyway when things are settling down I'd like to reproduce an issue with VapourSynth with which I had troubles and had to fix.

But probably you can answer it right now.

I added property "X" to a frame.
Then later (in another "ScriptClip") I added property "X" index #1 (2nd array element).

This array addition was not thread safe, second addition appeared multiple times in propShow when used in an MT environment. So the container was not detached in this case.

The fix was in this commit
https://github.com/AviSynth/AviSynth...48e05c60117290

Probably this one has no proper use case but I encountered the issue during my mt stress tests.