Avisynth+ - Page 65

tormento · 25th September 2015, 11:13

Quote:

Originally Posted by RazorBurn

The problem relies on the bug in upgrading your Build in Windows 10..

My Solution was Install clean state windows 10 build 240.. And Dont upgrade to new Win10 Builds..

My decision to jump over fast build wagon was AFTER I tested it on plain build and did not work. Are you on 32 or 64 bit?

Groucho2004 · 25th September 2015, 11:18

Quote:

Originally Posted by tormento

Is possible to use x264 directly with avs

It should work just like 32 bit AVS/x264. Why don't you just try it? Takes 10 seconds to find out.

tormento · 25th September 2015, 11:22

Quote:

Originally Posted by Groucho2004

It should work just like 32 bit AVS/x264. Why don't you just try it? Takes 10 seconds to find out.

I use MeGUI for 32 bit. Just have to try harder.

Groucho2004 · 25th September 2015, 11:24

Quote:

Originally Posted by tormento

I use MeGUI for 32 bit. Just have to try harder.

Code:

x264_64 -o foo.264 script.avs

tormento · 25th September 2015, 11:29

Quote:

Originally Posted by Groucho2004

Code:

x264_64 -o foo.264 script.avs

LOL

Code:

d:x264_64.exe  --level 4.1 --pass 1 --qp 16 --ref 3 --bframes 3 --analyse all --me umh --trellis 1 --subme 9 --merange 16 --keyint 250 --min-keyint 25 --b-adapt 2 --direct auto --weightb --mixed-refs --b-pyramid strict --8x8dct --no-fast-pskip --threads 8 --output amelie_64.mkv amelie_64.avs
avs [info]: 1920x816p 0:0 @ 24/1 fps (cfr)
x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 FastShuffle SSE4.2 AVX
x264 [info]: profile Main, level 4.1
x264 [info]: frame I:121   Avg QP:13.00  size:191308
x264 [info]: frame P:569   Avg QP:16.00  size: 64478
x264 [info]: frame B:1074  Avg QP:17.63  size: 25673
x264 [info]: consecutive B-frames: 13.0%  7.3% 30.8% 49.0%
x264 [info]: mb I  I16..4: 21.2%  0.0% 78.8%
x264 [info]: mb P  I16..4: 23.8%  0.0%  0.0%  P16..4: 66.2%  0.0%  0.0%  0.0%  0.0%    skip:10.0%
x264 [info]: mb B  I16..4:  4.0%  0.0%  0.0%  B16..8: 36.3%  0.0%  0.0%  direct:35.8%  skip:23.9%  L0:31.4% L1:40.8% BI:27.9%
x264 [info]: direct mvs  spatial:99.0% temporal:1.0%
x264 [info]: coded y,uvDC,uvAC intra: 67.1% 89.3% 72.8% inter: 27.2% 61.6% 8.6%
x264 [info]: i16 v,h,dc,p: 39% 29% 20% 13%
x264 [info]: i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 28% 22%  8%  6%  8%  8%  7%  8%  6%
x264 [info]: i8c dc,h,v,p: 41% 21% 28% 10%
x264 [info]: Weighted P-Frames: Y:3.9% UV:3.0%
x264 [info]: kb/s:9513.83

encoded 1764 frames, 22.83 fps, 9513.91 kb/s

LOL

Groucho2004 · 25th September 2015, 11:33

Quote:

Originally Posted by tormento

LOL

Code:

d:x264_64.exe  --level 4.1 --pass 1 --qp 16 --ref 3 --bframes 3 --analyse all --me umh --trellis 1 --subme 9 --merange 16 --keyint 250 --min-keyint 25 --b-adapt 2 --direct auto --weightb --mixed-refs --b-pyramid strict --8x8dct --no-fast-pskip --threads 8 --output amelie_64.mkv amelie_64.avs
avs [info]: 1920x816p 0:0 @ 24/1 fps (cfr)
x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 FastShuffle SSE4.2 AVX
x264 [info]: profile Main, level 4.1
x264 [info]: frame I:121   Avg QP:13.00  size:191308
x264 [info]: frame P:569   Avg QP:16.00  size: 64478
x264 [info]: frame B:1074  Avg QP:17.63  size: 25673
x264 [info]: consecutive B-frames: 13.0%  7.3% 30.8% 49.0%
x264 [info]: mb I  I16..4: 21.2%  0.0% 78.8%
x264 [info]: mb P  I16..4: 23.8%  0.0%  0.0%  P16..4: 66.2%  0.0%  0.0%  0.0%  0.0%    skip:10.0%
x264 [info]: mb B  I16..4:  4.0%  0.0%  0.0%  B16..8: 36.3%  0.0%  0.0%  direct:35.8%  skip:23.9%  L0:31.4% L1:40.8% BI:27.9%
x264 [info]: direct mvs  spatial:99.0% temporal:1.0%
x264 [info]: coded y,uvDC,uvAC intra: 67.1% 89.3% 72.8% inter: 27.2% 61.6% 8.6%
x264 [info]: i16 v,h,dc,p: 39% 29% 20% 13%
x264 [info]: i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 28% 22%  8%  6%  8%  8%  7%  8%  6%
x264 [info]: i8c dc,h,v,p: 41% 21% 28% 10%
x264 [info]: Weighted P-Frames: Y:3.9% UV:3.0%
x264 [info]: kb/s:9513.83

encoded 1764 frames, 22.83 fps, 9513.91 kb/s

LOL

So, the problem you had appears to be related to some GUI?

tormento · 25th September 2015, 11:51

Quote:

Originally Posted by Groucho2004

So, the problem you had appears to be related to some GUI?

No, to 32bit.

The 64bit versions of anything solve the problem of using DGDecNV and KNLMeansCL together.

Same image corruption even in 64 bit version.

qyot27 · 25th September 2015, 14:39

Quote:

Originally Posted by LigH

Ah, another idea: I believe to remember that some plugins already use API version 6 while AviSynth+ may still use API version 5, might be a reason why it can't load plugins with a higher API version?

That's only true of AviSynth+ 0.1/r1576. The changes from RC1 (API version 6, et al.) were merged into the MT/HEAD branch back in March. All the builds since then are v6.

LigH · 25th September 2015, 15:20

avs4x26x is a 32-bit application, calling 32-bit AviSynth, and piping the raw video stream to another (possibly, but not necessarily, 64-bit) encoder.

tormento · 25th September 2015, 19:46

This image corruption appears even in 64bit, one thread.

Plugin authors tell it's AviSynth+ fault.

Any idea?

qyot27 · 26th September 2015, 03:04

Due to the differing rules in setting the MT mode between the two, you're using mode 3 for SetMemoryMax in AviSynth-MT, but mode 2 in AviSynth+ (the same point also applies for LoadPlugin). I'll go on record saying I highly, highly doubt this has anything to do with the problem, but that difference means the script isn't as 1:1 a conversion from Avs-MT to Plus that it otherwise would be.

tormento · 26th September 2015, 09:32

Quote:

Originally Posted by qyot27

Due to the differing rules in setting the MT mode between the two, you're using mode 3 for SetMemoryMax in AviSynth-MT, but mode 2 in AviSynth+ (the same point also applies for LoadPlugin). I'll go on record saying I highly, highly doubt this has anything to do with the problem, but that difference means the script isn't as 1:1 a conversion from Avs-MT to Plus that it otherwise would be.

In MT I use the same memory modes, both in AviSynth and in AVS+, I did not know that SetMemoryMax could enter into equation. After this encoding session I'll try to remove the line or put as exception in initial plugin declaration and see. My current scripts, are quite similar:

PHP Code:


			
SetMTMode(3)
SetMemoryMax(2048)
LoadPlugin("D:\eseguibili\media\DGDecIM\DGDecodeIM.dll")
DGSourceIM("E:\in\2_01 favoloso mondo di Amelie, Il\amelie.dgi",engine=1)
SetMTMode(2)
CompTest(1)
ChangeFPS(last,last,true)
Crop(0,132,0,-140)
SMDegrain (tr=4,PreFilter=4,thSAD=400,contrasharp=false,refinemotion=false,plane=4,chroma=true,lsb=true,mode=6)

PHP Code:


			
SetFilterMTMode("DEFAULT_MT_MODE", 2)
SetFilterMTMode("DGSourceIM", 3)
SetFilterMTMode("KNLMeansCL", 3)
SetMemoryMax(2048)
LoadPlugin("D:\eseguibili\media\DGDecIM\DGDecodeIM.dll")
DGSourceIM("E:\in\2_01 favoloso mondo di Amelie, Il\amelie.dgi",engine=1)
CompTest(1)
ChangeFPS(last,last,true)
Crop(0,132,0,-140)
SMDegrain (tr=4,PreFilter=4,thSAD=400,contrasharp=false,refinemotion=false,plane=4,chroma=true,lsb=true,mode=6)
Prefetch(4)

The corruption however is even in single thread.

ndjamena · 12th October 2015, 18:42

Are the updated audio parameters in BlankClip not included in AVISynth+ or has it been changed to something else. I can't find any mention of it anywhere.

http://avisynth.nl/index.php/BlankClip

int channels, string sample_type

VirtualDub is complaining that BlankClip has no such arguments.

Reel.Deel · 12th October 2015, 18:52

Quote:

Originally Posted by ndjamena

Are the updated audio parameters in BlankClip not included in AVISynth+ or has it been changed to something else. I can't find any mention of it anywhere.

http://avisynth.nl/index.php/BlankClip

int channels, string sample_type

VirtualDub is complaining that BlankClip has no such arguments.

BlankClip(channels=2, sample_type="16bit") works for me on r1576. Are you sure you're not doing anything wrong? Those parameters have been there since v2.58...

ndjamena · 12th October 2015, 19:03

I must have made a typo somewhere.

real.finder · 8th November 2015, 19:26

mt test

Code:

ColorBars(width=720, height=480, pixel_type="RGB32")
ConvertToYV12()
QTGMC(InputType=1, Ezdenoise=2)
LSFMod(strength=66)
gradfun3()
Prefetch(12)

Code:

setmtmode(2,12)
ColorBars(width=720, height=480, pixel_type="RGB32")
ConvertToYV12()
QTGMC(InputType=1, Ezdenoise=2)
LSFMod(strength=66)
gradfun3()

stranno · 15th November 2015, 22:21

I'm testing a bit and it seems that 1576 is a bit faster than 1773 that is more faster than 1825.

But i'm interested in ffmpeg so i must use a newer version.

Is there any way to set 1773 only for ffmpeg and keeping 1576 for daily work with x264? Aside switching the avisynth files every time.

MysteryX · 15th November 2015, 23:45

If you open the script with avs2yuv.exe and pipe into ffmpeg, then it won't care which version of AviSynth you're using.

qyot27 · 16th November 2015, 02:44

Quote:

Originally Posted by stranno

I'm testing a bit and it seems that 1576 is a bit faster than 1773 that is more faster than 1825.

But i'm interested in ffmpeg so i must use a newer version.

Is there any way to set 1773 only for ffmpeg and keeping 1576 for daily work with x264? Aside switching the avisynth files every time.

Put the AviSynth.dll from the r1773 package in the same directory as ffmpeg.exe.

stranno · 16th November 2015, 15:25

Very useful, thanks both for the tips.

25th September 2015, 15:20	#1289 \| Link
LigH German doom9/Gleitz SuMo Join Date: Oct 2001 Location: Germany, rural Altmark Posts: 6,784	avs4x26x is a 32-bit application, calling 32-bit AviSynth, and piping the raw video stream to another (possibly, but not necessarily, 64-bit) encoder. __________________ New German Gleitz board MediaFire: x264 \| x265 \| VPx \| AOM \| Xvid

25th September 2015, 19:46	#1290 \| Link
tormento Acid fr0g Join Date: May 2002 Location: Italy Posts: 2,582	This image corruption appears even in 64bit, one thread. Plugin authors tell it's AviSynth+ fault. Any idea? __________________ @turment on Telegram

15th November 2015, 22:21	#1297 \| Link
stranno Registered User Join Date: Jul 2011 Posts: 50	I'm testing a bit and it seems that 1576 is a bit faster than 1773 that is more faster than 1825. But i'm interested in ffmpeg so i must use a newer version. Is there any way to set 1773 only for ffmpeg and keeping 1576 for daily work with x264? Aside switching the avisynth files every time. Last edited by stranno; 15th November 2015 at 22:24.

15th November 2015, 23:45	#1298 \| Link
MysteryX Soul Architect Join Date: Apr 2014 Posts: 2,559	If you open the script with avs2yuv.exe and pipe into ffmpeg, then it won't care which version of AviSynth you're using. __________________ FrameRateConverter \| AvisynthShader \| AvsFilterNet \| Natural Grounding Player with Yin Media Encoder, 432hz Player, Powerliminals Player and Audio Video Muxer

26th September 2015, 03:04	#1291 \| Link
qyot27 ...? Join Date: Nov 2005 Location: Florida Posts: 1,420	Due to the differing rules in setting the MT mode between the two, you're using mode 3 for SetMemoryMax in AviSynth-MT, but mode 2 in AviSynth+ (the same point also applies for LoadPlugin). I'll go on record saying I highly, highly doubt this has anything to do with the problem, but that difference means the script isn't as 1:1 a conversion from Avs-MT to Plus that it otherwise would be.

12th October 2015, 18:42	#1293 \| Link
ndjamena Registered User Join Date: Sep 2012 Posts: 366	Are the updated audio parameters in BlankClip not included in AVISynth+ or has it been changed to something else. I can't find any mention of it anywhere. http://avisynth.nl/index.php/BlankClip int channels, string sample_type VirtualDub is complaining that BlankClip has no such arguments.

12th October 2015, 19:03	#1295 \| Link
ndjamena Registered User Join Date: Sep 2012 Posts: 366	I must have made a typo somewhere.

16th November 2015, 15:25	#1300 \| Link
stranno Registered User Join Date: Jul 2011 Posts: 50	Very useful, thanks both for the tips.