Avisynth+

[yup]

Hi all!
Where can load last version Devil.dll?
I am try registering on SF, but can not access to files.
yup.

[pinterf]

https://sourceforge.net/projects/ope...20and%20Win64/
But 1.78 is included in the usual avisynth+ binary package.

[pinterf]

Originally Posted by Myrsloik

Find a slightly older tivtc version if tou want c code for everything. That's what I did. Obviously the c code doesn't match the asm because real men don't test things.

Thanks, I will do a post-check I think.

[tormento]

I have formatted PC after infinite inline updates of Win10 previews.

Is too much to ask for a installer with latest version?

[ajp_anton]

Just a thought... why not have the Info() function return everything as a string instead of overlaying it onto a clip, with potential problems involving the clip resolution and text size. The user could then modify it and manually subtitle it into the video using more easily visible styling or colors.
You could add a bool parameter "return_string" or something, false by default.

[yup]

Originally Posted by pinterf

https://sourceforge.net/projects/ope...20and%20Win64/
But 1.78 is included in the usual avisynth+ binary package.

This package support high bit depth image? Y16 for example?
yup.

[pinterf]

Originally Posted by yup

This package support high bit depth image? Y16 for example?
yup.

DevIL DLL itself is capable to do that, but you need a new ImageSeq.dll which I have not released yet.

[StainlessS]

Originally Posted by ajp_anton

Just a thought... why not have the Info() function return everything as a string instead of overlaying it onto a clip, with potential problems involving the clip resolution and text size. The user could then modify it and manually subtitle it into the video using more easily visible styling or colors.
You could add a bool parameter "return_string" or something, false by default.

That was requested about a year or so ago.

EDIT: Further request, how about allowing YUV color of eg $008080 for both LetterBox and Addborders. (for masks)

[yup]

Originally Posted by pinterf

DevIL DLL itself is capable to do that, but you need a new ImageSeq.dll which I have not released yet.

Will be waiting.
yup.

[qyot27]

Originally Posted by ajp_anton

Just a thought... why not have the Info() function return everything as a string instead of overlaying it onto a clip, with potential problems involving the clip resolution and text size. The user could then modify it and manually subtitle it into the video using more easily visible styling or colors.
You could add a bool parameter "return_string" or something, false by default.

Styling...you mean like the font, size, text_color, and halo_color parameters that were added to Info() back in August before the in-between bit depths were?

[Yanak]

Originally Posted by StainlessS

AviSource("F:movie.avi", audio = false)
ConvertToYV24() # NOTE 24

# Fail, logo only asigned to AFTER whole line is processed, ie you try to use logo before assinging a value to it.
# logo=ImageSource("F:\logo.png").Overlay(logo, x = 3, y=3, opacity=0.45, mode="luma") 

logo=ImageSource("F:\logo.png") # Logo now exist, has been assigned to
Overlay(logo, x = 3, y=3, opacity=0.45, mode="luma") # OK logo exists

# SomeClip.SomeFilter().Crop() works because you are not referenceing a clip that does not yet exist, assuming SomeClip exists.
# Someclip is passed through SomeFilter and on to Crop.

I hope some of that makes sense, was in a hurry to catch my bus, I missed it.

Sorry for the late reply and thank you,

ConvertToYV24() works with the old logo size of 90x 55px, perfect.

For the rest I don't know what what happened, feeling silly, probably mixed up some stuff or messed up somewhere when copying old avs parts of code i used before, had in mind it always worked before but nope, don't know what happened with my brain.

Thanks again.

[ajp_anton]

Originally Posted by qyot27

Styling...you mean like the font, size, text_color, and halo_color parameters that were added to Info() back in August before the in-between bit depths were?

Sorry, is there an updated wiki/manual somewhere that includes all the new stuff?
Also, it still doesn't let you modify the info string, which I find unnecessary and feels like an easy fix (could be wrong, not a programming guru).

[raffriff42]

Originally Posted by ajp_anton

Sorry, is there an updated wiki/manual somewhere that includes all the new stuff?

For now, see:
Oct 2016 Avisynth Plus Quick reference guide
Nov 2016 New functions
Apr 2017 AVS 2.60 vs. AVS+ r2455
(Are there other good resources? I'd like to know about them.)

Reel.Deel said he was starting a new documentation site; I don't know what's happening with it.

Originally Posted by raffriff42

Sounds great! I'll note any changes in the wiki for you.

Originally Posted by Reel.Deel

...I don't know if listing all AVS+ changes alongside the 'official' documentation is a good idea. Might be a tad confusing.

[MysteryX]

There isn't just an issue with ScriptClip, but also with ConditionalFilter

vid = AviSource("file")
vid_blur = vid.Blur(1.5)
ConditionalFilter(vid, vid_blur, vid, "AverageLuma()", "lessthan", "20")
Prefetch(2)

This results in a message showing up in the video: "Average Plane: this filter can only be used within run-time filters". Without prefetch, it works fine.

Since these are purely internal filters, nothing prevents you from having AverageLuma as a local function called by ConditionalFilter instead of trying to handle it as a separate special plugin.

[pinterf]

Originally Posted by raffriff42

(Are there other good resources? I'd like to know about them.)

Check the readme.txt in the binary package.

I was already practicing a bit on editing things on avisynth wiki pages, I have updated the masktools sections, worked a bit on mvtools and other references of my plugin updates.

But I still need help on the new function pages, at least to have a good hierarchy and dummy skeleton article pages to be fill up.
At the moment Avisynth+ has only one dedicated page on wiki. I'd better not put all the readme stuff there as a flat section. Nor I want to edit the filter section of the classic Avisynth pages.
If someone would create a good (even dummy) layout for the new functions, it would help a lot on bringing the knowledge base online.

[raffriff42]

Personally, I'd like to see an AVS+ Infobox on each classic filter page, explaining the differences in some standardized form. Something similar in appearance to the "Abstract" box currently seen on external filter pages like MaskTools2.

>If someone would create a good (even dummy) layout for the new functions, it would help a lot on bringing the knowledge base online.
I really don't feel like working on a site that is about to be made obsolescent by a fork site.
(If you didn't know, I have been one of the very few active content contributors there - I have made hundreds of edits, maybe thousands. The only other users that active are Reel.Deel and Wilbert, the administrator of the site. So that 'someone' would probably be me.)

EDIT okay, I'm reconsidering my position. Whatever Reel.Deal does or doesn't do, I will begin (oh god) the rather large task of documenting AVS+ on the mainstream Avisynth wiki, as time permits. Crudely at first, as you describe. And as always, subject to Wilbert's approval.

[MysteryX]

When I build Avisynth+ from the Pinterf's source, I get this error when opening a script:

Avisynth open failure:
Script error: There is no function named 'Prefetch'.

What's going on here?

btw, there is code here that doesn't compile (Visual Studio 2017) because of 'y' being defined several times. It's easy to fix, you just have to rename the 2nd 'y'.
focus.cpp - af_horizontal_yuy2_c

[qyot27]

git checkout MT

[pinterf]

Originally Posted by raffriff42

EDIT okay, I'm reconsidering my position. Whatever Reel.Deal does or doesn't do, I will begin (oh god) the rather large task of documenting AVS+ on the mainstream Avisynth wiki, as time permits. Crudely at first, as you describe. And as always, subject to Wilbert's approval.

Thank you "someone" It's really not too much people who keep this documentation site live, I appreciate your efforts.

[pinterf]

Originally Posted by qyot27

git checkout MT

Btw, I have to mention another news from the past weeks; with the patient help of qyot27, we were able to successfully compile the project with gcc (under Linux but not for Linux, which was a nightmare and a hard learning curve for me, thanks again qyot27). I don't know if this is good or not, we are by far not on par with Vapoursynth's multiplatform design and I guess we'll never be.