AviSynth+ thread Vol.2

[pinterf]

Originally Posted by TomArrow

Any clues on the "Device unmatch: ConvertToRGB48[CPU] does not support [CUDA] frame" problem?

Way to reproduce:

1. Get newest AVISynth+ release.

2. Grab CoronaSequence plugin from http://avisynth.nl/index.php/ImageSequence

3. Load image sequence with CoronaSequence command.

4. Add ConvertToRGB64() at the end.

Being a 64 bit plugin from 2010, when no 64 bit Avisynth+ existed, it is pure luck if it works or not. Plus: maybe it is a 2.5-style plugin which can be an additional pain. If so, the plugin must be first recompiled with a 2.6 / Avisynth+ header.

[Reel.Deel]

Originally Posted by pinterf

Being a 64 bit plugin from 2010, when no 64 bit Avisynth+ existed, it is pure luck if it works or not. Plus: maybe it is a 2.5-style plugin which can be an additional pain. If so, the plugin must be first recompiled with a 2.6 / Avisynth+ header.

It seems Tom is using the Avisynth+ header but with AvisynthPluginInit2: https://github.com/TomArrow/CoronaSe...uence.cpp#L446

[kedautinh12]

Latest ver
https://github.com/TomArrow/CoronaSe...64mod/releases

[TomArrow]

Originally Posted by Reel.Deel

It seems Tom is using the Avisynth+ header but with AvisynthPluginInit2: https://github.com/TomArrow/CoronaSe...uence.cpp#L446

Yeah I think I use the modern SDK.

Is this wrong? Either way I think this CUDA/whatever problem is not intended behavior so a fix would probably be nice to have.

I guess it's possible that the problem is in some of the plugin code elsewhere, like accidentally overwriting some property due to overflow or bad pointer handling, but I wouldn't even know where to start looking since I don't understand the feature. I'm also not the original author of the plugin, I just made changes.

[Reel.Deel]

Originally Posted by TomArrow

Yeah I think I use the modern SDK.

Is this wrong?

Probably best to use AvisynthPluginInit3 when using AviSynth 2.6/AviSynth+ headers.

See here: https://github.com/pinterf/TNLMeans/...1556f25441502a

[kedautinh12]

Originally Posted by pinterf

Avisynth 3.7.3 test 2
Avisynth+ 3.7.3 test 2 (20221114)

20221114 3.7.3 WIP
------------------
- Fix (#304): ColorYUV analyze=true was displaying wrong min-max values for YUY2
- Fix: C API undefined behavior when upstream throw runtime error
- Mute compilation warnings in avisynth.h
- CMakeLists.txt: fix clang-cl/intel with ninja generator
- Fix (#293): "Text" to throw proper error message if the specified font name (e.g. Arial) is not found among internal bitmap fonts.
- Fix (#293): "Subtitle" and "Text" filter to respect the explicitely given coorditanes for y=-1 or x=-1, 
  instead of applying vertical/horizontal center alignment.
- Fix: C interface crash when using avs_new_video_frame_p(_a)
- Fix (#283): broken runtime functions min/max/minmaxdifference when threshold is not 0 (returned -1). Regression in 3.7.2
- New: add a sixth array element to PlaneMinMaxStats: average. Defines variable "PlaneStats_average" as well if setting variables is required.
- Fix (#282): ConvertToRGB
  - do check for exact 8 or 16 bit input, because packed RGB formats exist only for 8 and 16 bits
  - keep alpha for RGBA planar - convert RGBAP8/16 to RGB32/64, while RGBP8/16 is still RGB24/48

Clang build
https://gitlab.com/uvz/AviSynthPlus-Builds

[gispos]

Since Avisynth 3.7.3 or the extra builds from GS (https://gitlab.com/uvz/AviSynthPlus-Builds) I get error messages every now and then that are not present in Avisynth 3.7.2

Either no clip can be created (without error message) or the error message 'Function not found' appears (v3.7.3).
And in both cases: If the same script is loaded again, no error occurs.

If I go back to 3.7.2 everything is fine again.

I load some dll's and scripts via an avsi, has anything changed in the plugin loading order?

[ryrynz]

Yeah I decided to test the test build as well and just got nothing out the other end, I don't think test builds should be that broken
Basically an alpha, so I wasn't concerned and just went back to 3.7.2 as well, figuring something so broken would be identified soon enough.
Clang build wasn't any better either.

[gispos]

Originally Posted by ryrynz

...so I wasn't concerned and just went back to 3.7.2 as well, figuring something so broken would be identified soon enough.
Clang build wasn't any better either.

If no one reports it, it cannot be identified.
I would like to provide more detailed information, but it is completely random and also not so often.

[VoodooFX]

Report: I still had no issues with Avisynth+ 3.7.3 test 2 (20221114)

[poisondeathray]

Originally Posted by VoodooFX

Report: I still had no issues with Avisynth+ 3.7.3 test 2 (20221114)

No problems either;

For the people having issues, post your script(s) maybe some clues there

[gispos]

Since I changed my avsi file to load my filters and dll's, there have been no problems with Avisynth 3.73 so far.

Before everything was listed randomly, now I load all dll's first and only then the scripts.

Something must have changed because 3.72 had no problems with the mixed loading order.

As long as it works now all is good.

[pinterf]

Happy New Year!

Let's start the year with some cosmetic and other changes and fixes in "Text" filter:
Avisynth+ 3.7.3 test 3 (20230118)

- Fix: "Text" filter negative x or y coordinates (e.g. 0 instead of -1)
- Fix: "Text" filter would omit last character when x<0
- Fix: "Text" halo_color needs only MSB=$FF and not the exact $FF000000 constant for fade
- "Text" ``halo_color`` allows to have both halo and shaded background
- "Text" much nicer rendering of subsampled formats

[FranceBB]

Happy New Year to you too, Master Ferenc!
Thanks for the new build! I'll definitely test!

[Reel.Deel]

Also, 32-bit AviSynth+ now supports non-decorated export names in C-plugins. This is something that was missing since the beginning of avs+.

By the way, this is how the Text filter on YUV420 looks like now, and how it used to look.

New


Old

[Emulgator]

Ah, welcome back, Ferenc !
(Was trying uvx 3825 and both 32 and 64 bit failed instantly...)

[StainlessS]

Welcome home P, and Happy New Year to U 2.

[Dogway]

Where is the Text filter in wiki?
I get error trying to use "Arial" as the font.

SimpleText: internal font name Arial in size 18 not found.

[Reel.Deel]

Originally Posted by Dogway

Where is the Text filter in wiki?
I get error trying to use "Arial" as the font.

It's not documented in the wiki. That is why there's a note at the top of the page with the link to the readthedocs documentation which is up-to-date. See here: https://avisynthplus.readthedocs.io/...itle.html#text

Text, is meant for bdf fonts. It comes with "Terminus" (available in different sizes) and "Info.h" that is a fixed dimension.

---

PS, if someone wants to update the wiki, go for it. Updating the actual avs docs was a large task, and I don't feel like doing double work .

[kedautinh12]

Originally Posted by pinterf

Happy New Year!

Let's start the year with some cosmetic and other changes and fixes in "Text" filter:
Avisynth+ 3.7.3 test 3 (20230118)

- Fix: "Text" filter negative x or y coordinates (e.g. 0 instead of -1)
- Fix: "Text" filter would omit last character when x<0
- Fix: "Text" halo_color needs only MSB=$FF and not the exact $FF000000 constant for fade
- "Text" ``halo_color`` allows to have both halo and shaded background
- "Text" much nicer rendering of subsampled formats

Some new 32-bit plugin don't support XP anymore. So next update can you add x86 for win 7 and up beside x86-xp??