View Full Version : Avisynth+ (HELP)
frank_zappa1
14th September 2017, 05:12
i have this script , but cant make it work in avisynth+
everything else works but that part selected is the problem
can you help me please .
thanks
https://i.imgur.com/3UxSEtQ.png
stax76
14th September 2017, 11:38
Hi, please post text instead of images.
18fps
15th September 2017, 09:24
Given the errors it looks like a problem with avspmod rather than avisynth+. I think you have to update avspmod to use it with avisynth+.
Groucho2004
15th September 2017, 09:52
Given the errors it looks like a problem with avspmod rather than avisynth+. I think you have to update avspmod to use it with avisynth+.
Quite possible. Here are the links for the updated AvsPMod:
x86 (https://cloud.pados.hu/index.php/s/0e0d5588307a7b0474742711731699b6/download?path=%2Fr2172-MT-test%2Fi386&files=AvsPmod_v2.5.1_r452_x86.7z)
x64 (https://cloud.pados.hu/index.php/s/0e0d5588307a7b0474742711731699b6/download?path=%2Fr2172-MT-test%2Fx64&files=AvsPmod_v2.5.1_r452_x64.7z)
lansing
18th September 2017, 19:49
This thread should go under the avspmod main thread, as people reported similar problems.
Thanks Groucho for the update, it fixed the warning pop up, but the feature to toggle through tab with scrolling is still broken in the 64 bit version.
vcmohan
2nd October 2017, 13:40
I am getting a problem of formats not matching for subtract.
My script is
b =imagesource("c:\images\stamil.jpg",end = 10).converttoRGB24()
c = converttoy8(b)
a = converttoRGB24(c)
file = "c:\temp\NeuralPlus.txt"
red = Neural(a,b, iter = 500, wset = false, bestof = 5,tty = 300, tlx = 200, trx = 300, tby = 400, xpts = 3,rgb = 0, file = "none", fname = file)
green = Neural(a,b, iter = 500, wset = false, bestof = 5,tty = 300, tlx = 200, trx = 300, tby = 400, xpts = 3,rgb = 1, file = "none", fname = file)
blue = Neural(a,b, iter = 500, wset = false, bestof = 5,tty = 300, tlx = 200, trx = 300, tby = 400, xpts = 3,rgb = 2, file = "save", fname = file)
m = mergeRGB(blue,green,red)
subtract(a, m).Levels(127,1,129,0,255)
return(last)
I am using Neural function of modplus plugin. But that should not matter. The input is 602 x566. I get a message from subtract that the input does not match. If I use blue or red or green in place of m in subtract it works fine. MergeRGB appears to do something.
StainlessS
2nd October 2017, 14:19
You should get a clue as to where problem lies by inserting in turn
Return m.Info
Return a.Info
Return red.Info
Return green.Info
Return blue.Info
Return b.Info
Return c.Info
Before the subtract line. (compare colorspace, narrow down where problem occurs).
vcmohan
2nd October 2017, 14:50
I checked them and all seem ok. In place of subtract stackhorizontal also gives same error if I include m (mergeRGB) output. For all other clips it works OK. The mergeRGB appears to give a different colorspace.
StainlessS
2nd October 2017, 14:52
Sorry, cannot assist, do not use Avs+.
EDIT: Post a.Info m.info, images on PostImage.org or similar.
EDIT: Oops, sorry, should have said Return m.Info etc.
EDIT: Is it an RGB24, RGB32 mismatch. EDIT: Ignore this.
Does StackVertical work ok?
vcmohan
2nd October 2017, 15:01
m.info indicates RGB32 while all others are RGB24
StainlessS
2nd October 2017, 15:02
Looks like you found a bug in MergeRGB, RGB32 result. Just check if red/green and blue are RGB24.
[EDIT: No, not a bug]
vcmohan
2nd October 2017, 15:04
I checked them to be RGB24
StainlessS
2nd October 2017, 15:05
Then vcmohan wins a coconut, MergeRGB bug. [EDIT: No, not a bug]
[Dont forget to collect your prize at the door, when leaving the forum :) ]
EDIT: VC, can you post which version AVS+ you are using, and perhaps someone can verify similar problem on latest version avs+.
StainlessS
2nd October 2017, 15:16
Well actually this works, (produces RGB32, where I assumed it would not)
colorbars.killaudio
convertToRGB32
MergeRGB(Last,Last,Last)
info
but if Red, Green, and Blue, are RGB24 then is a problem there. [Above on AVS standard]
StainlessS
2nd October 2017, 15:19
Found it, docs
pixel_type default RGB32, optionally RGB24, specifies the output pixel format.
So, not actually a bug, set MergeRGB(...,Pixel_type="RGB24")
vcmohan
3rd October 2017, 07:03
Thanks. I was looking at Doc but failed to notice this.
raffriff42
3rd October 2017, 11:05
Edited the page to make it a little easier to read.
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.