AviSynth+ thread Vol.2

[kedautinh12]

AviSynthPlus r3877 clang build
https://gitlab.com/uvz/AviSynthPlus-Builds

[ryrynz]

Gave that clang build a shot & Test build 3 and both just freeze when I change to one of my avisynth scripts., so no change from build 2.
Maybe a filter isn't up to date or something, I'll report back when I look into it.

[kedautinh12]

You need report here:
https://github.com/AviSynth/AviSynthPlus/issues

[Emulgator]

I had no luck with uvz builds either.

[kedautinh12]

You can report uvz's build issues here:
https://gitlab.com/uvz/AviSynthPlus-Builds/-/issues

[Fjord]

It would be handy to be able to specify multiple arguments to the propDelete() function, to get rid of several properties in one call.

propDelete(clip, "MyProp1", "MyProp2", "MyProp3")

An inverse of that could be a new function "propKeep()" that would delete any properties not named as arguments to the function.

propKeep(clip, "MyKeep1", "MyKeep2", "MyKeep3")

This would be handy for filtering properties to a fixed set, rather than clearing all, and restoring only the ones that are wanted.

What do you think?

EDIT: I see in the change log from 3.7.1 to 3.7.2 that:

• PropCopy: new string parameter "props": list of property names to copy (or ignore)
• PropCopy: new bool parameter "exclude": whether property list is positive (copy) or negative (do not copy; blacklist)
• PropDelete: accept an array string parameter as list of property names to remove

and a bit more detailed in the github readme_history.txt:

- propCopy: able to specify that the property list is negative.
    bool "exclude" = false # default: "props" is positive list
    
    propCopy(org,true,props=["_Matrix", "_ColorRange"], exclude=false) # merge only two properties
    propCopy(org,true,props=["_Matrix", "_ColorRange"], exclude=true) # merge all, except listed ones
    propCopy(org,props=["_Matrix", "_ColorRange"]) # erase all then copy only selected
    propCopy(org,props=["_Matrix", "_ColorRange"], exclude = true) # erase all, then copy all, except listed ones
...
- PropDelete: accept a non-empty array string as list of property names to remove
  Parameter is not optional, and has no name. It can be either a string (as before) or an array of strings
    propDelete("_Matrix") # old syntax, still accepted
    propDelete(["_Matrix", "_ColorRange"])
- PropCopy: new string parameter "props" as list of property names to remove
    "props": a non-empty array of strings
    
    old syntax, still accepted:
      propCopy(org,true) # merge from all org's properties
      propCopy(org,false) # erase all then copy all org's properties (exact copy)
    new syntax
      propCopy(org,true,props=["_Matrix", "_ColorRange"]) # merge
      propCopy(org,props=["_Matrix", "_ColorRange"]) # erase all then copy only selected

which means my request is already implemented (in another way), although this hasn't yet made it to the wiki regarding propCopy (which is current for 3.7.1).

[Reel.Deel]

Originally Posted by Fjord

although this hasn't yet made it to the wiki regarding propCopy (which is current for 3.7.1).

Wiki probably will not be updated (at least by me or pinterf) but there will be a link to the corresponding readthedocs page when ever it becomes available. I have 50% of the syntax pages done and includes up-to-date docs.

[Fjord]

Originally Posted by Reel.Deel

... but there will be a link to the corresponding readthedocs page when ever it becomes available. I have 50% of the syntax pages done and includes up-to-date docs.

Thanks Reel.Deel. Your revisions and editing of readthedocs are terrific and is greatly appreciated.

[Fjord]

@Reel.Deel, does Sphinx have a "history" or "recent changes" function, to show what the latest updates are to readthedocs?

I cannot find your above update of the propCopy documentation in readthedocs (https://avisynthplus.readthedocs.io/...est/index.html). Where should I be looking? Or is this an offline change, yet to be merged into the online version?

[Reel.Deel]

It's on my hard drive ... The readthedocs automatically updates anytime there are changes so if you don't see a particular page there, it's yet to be finished. Hopefully I'll finish it in the coming week or so.

[kedautinh12]

AviSynthPlus r3912 clang build
https://gitlab.com/uvz/AviSynthPlus-Builds

[jpsdr]

This r3912 version broke high bit format, the following script:

SetMemoryMax(192)
AviSource("Dark_Crystal_HDR_16b.avi")
ConverttoYUV444()

doesn't work anymore , my avi file is utvideo yuv422p10le.

The AvisynthPlus_3.7.3_20230118_test3 is working.

[kedautinh12]

Originally Posted by jpsdr

This r3912 version broke high bit format, the following script:

SetMemoryMax(192)
AviSource("Dark_Crystal_HDR_16b.avi")
ConverttoYUV444()

doesn't work anymore , my avi file is utvideo yuv422p10le.

The AvisynthPlus_3.7.3_20230118_test3 is working.

You can create issue here:
https://gitlab.com/uvz/AviSynthPlus-Builds/-/issues

[Reel.Deel]

Originally Posted by jpsdr

This r3912 version broke high bit format, the following script:

SetMemoryMax(192)
AviSource("Dark_Crystal_HDR_16b.avi")
ConverttoYUV444()

doesn't work anymore , my avi file is utvideo yuv422p10le.

The AvisynthPlus_3.7.3_20230118_test3 is working.

In what way did it break? What is the error message?

Just 3 hours ago pinterf merged this PR: https://github.com/AviSynth/AviSynthPlus/pull/332

All of that has been a work-in-progress in the last few weeks. There has not been any user related changes added ever since pinterf's test release (aside from "Text"). All has been internal API stuff and documentation.

I guess wait for a new release that includes the changes from today. If the problem still continues then open up an issue on Github.

[Fjord]

I was having difficulty with array arguments to a user function I was working on. So I tried the demo script showing an example use of array arguments in a user function. No wonder I was having issues - the demo script throws an error on the example for array arguments! (I am running v3.7.3 test3 r3835 in latest AvsPMod).

The demo script comes from the 9 feb 2023 readme_history.txt, lines 1841-1886, at
https://github.com/AviSynth/AviSynth...me_history.txt
The same demo script is used in the 4th Example section in readthedocs page on Arrays:
https://avisynthplus.readthedocs.io/...ef_arrays.html

The error message (in AvsPMod) is:
Script error: Invalid arguments to function 'FirstNSum'
(C:\Users\...\...\test Array examples.avs, line 25)

The error is fixed by putting quotes on the argument names in the function definition, and using the parameter names in the function call.

In my own code, I experienced weird errors when trying array arguments to a user function for the first time -- they were named arguments, but I omitted the names= in the function call. It took quite a while to debug -- which was just to use all argument names in the function call, which included an array argument.

If this is not a bug, then the requirement to always use argument names when calling functions with array arguments needs to be highlighted in the Array documentation.

Here is the demo script from readme_history.txt, with comments showing the necessary corrections on two lines - call to FirstNSum() function, and the function definition.

ColorBars()
clip=last
a = [[1,2],[3,4]]
aa = [1]
b = a[1,1] + ArrayGet(a, 1,0) + aa[0]

empty_array = []
empty_array_2 = empty_array
#n3 = empty_array_2.ArrayGet(0) # array index out out range error!

black_yuv_16 = [0,32768,32768]
grey_yuv_16 = [32768,32768,32768]
white_yuv_16 = [65535,32768,32768]
aSelectColors = [\
  ["black", black_yuv_16],\
  ["grey", grey_yuv_16],\
  ["white",white_yuv_16],\
  ["empty",empty_array]\
]
test_array = [99, 1.0, "this is a string"] # mixed types
test_array2 = [199, 2.0, "This is a string"]

n = ArraySize(test_array) # 3
n2 = ArraySize(empty_array_2) # 0
sum = FirstNSum(grey_yuv_16,2)	# --> sum = FirstNSum(x=grey_yuv_16,n=2)
b = b

clip = clip.Text(e"Array size = " + String(n) +\
 e"\n Empty array size = " + String(n2) +\
 e"\n sum = " + String(sum) +\
 e"\n b = " + String(b) +\
 e"\n white_yuv_16[1]=" + String(aSelectColors["white"][1]) + \
 e"\n [0]=" + String(ArrayGet(test_array,0)) + \
 e"\n [1]=" + String(ArrayGet(test_array,1)) + \
 e"\n [2]=" + ArrayGet(test_array,2), lsp=0, bold=true, font="info_h")

return clip

function FirstNSum(array x, int n) {	# --> function FirstNSum(array "x", int "n") {
  a = 0
  for (i=0, x.ArraySize()-1) {
    a = a + x[i]
  }
  return a
}

[jpsdr]

Originally Posted by Reel.Deel

In what way did it break?

I can't open the avs file in Virtualdub2 anymore.

Originally Posted by Reel.Deel

What is the error message?

Unknow or unsupported video format.

[pinterf]

Without being able to test jpsdr's issue:
Test build 4:
Avisynth+ 3.7.3 test 4 (20230216)

[FranceBB]

Just like Test3, Test4 also doesn't work on Windows XP x86 due to 2 missing functions in the kernel: GetLocaleInfoEx and GetFileInformationByHandleEx

[pinterf]

Originally Posted by FranceBB

Just like Test3, Test4 also doesn't work on Windows XP x86 due to 2 missing functions in the kernel: GetLocaleInfoEx and GetFileInformationByHandleEx

I have double checked the option now. I don't know what happens.

[pinterf]

Test2 is still running fine for you?