Avisynth 2.6 MT

[VideoFanatic]

I can't seem to get a speed improvement on my dual core PC over normal Avisynth:

I have Avisynth 2.5.8. I replaced the system32 avisynth file with the 2.6 MT file. I am using this script with Simple x264 Launcher to make an h264 file:

setmtmode(5,0)
Mpeg2Source("I:\file.d2v", CPU=6)
setmtmode(2,0)
DeGrainMedian(limitY=2, limitUV=3, mode=1, interlaced=true)
Crop(0,12,0,-12)
Tweak(Bright=0, Sat=1.0, Cont=0.9, Hue=10.0, Coring=False)
AddBorders(0, 12, 0, 12)

What am I doing wrong?

[Groucho2004]

Originally Posted by holygamer

I can't seem to get a speed improvement on my dual core PC over normal Avisynth

Have you tried to measure the speed of the script alone? You can do that with AVSMeter.

[VideoFanatic]

How do I use that?

[Bloax]

Drop your .avs over the .exe?

[VideoFanatic]

It reported the following:

Minimum: 9
Maximum: 66
Average: 37

with this script:

setmtmode(5,3)
Mpeg2Source("H:\New\z = Encode\Raw January 03 2000 Fixed.d2v", CPU=6)
setmtmode(2,0)
DeGrainMedian(limitY=2, limitUV=3, mode=1, interlaced=true)

It reported the following:

Minimum: 13
Maximum: 30
Average: 21

with this script:

Mpeg2Source("H:\New\z = Encode\Raw January 03 2000 Fixed.d2v", CPU=6)
DeGrainMedian(limitY=2, limitUV=3, mode=1, interlaced=true)

So is it the limit of the h264 encoding speed thats preventing me from getting faster encoding times or do I need more than a dual core PC?

[Atak_Snajpera]

is cpu usage at 100 percent?

[VideoFanatic]

Yes it is.

[Atak_Snajpera]

so here is your answer why you don't see speed improvement. encoding speed on dual core is too slow.

[SubJunk]

Originally Posted by SEt

What? First time I hear such issue. How about making proper bug report?

I don't know if it's an issue or by design because of Intel's Hyperthreading (maybe they don't want to support the hyperthreaded cores)

Originally Posted by Atak_Snajpera

Avisynth 2.6 MT installer (2012.05.16) -> http://www.mediafire.com/?prfoy9wfj4gtnnw
Installer source files -> http://www.mediafire.com/?308aa5d3r4nszwz

If you make another version could you please make it set a unique version in the registry? It currently sets "2.6.0 MT" which is great but will be cool if it sets a different one next time so I can check against it (like "2.6.0 MT 2012.05.16" or something)

[SEt]

I have no idea what you are talking about. From Avisynth point of view hyperthreaded cores are as good as regular cores and there are no differences. I myself use hyperthreaded Intel CPU and never saw anything like that.
Note: as Avisynth is a dynamic library and not stand-alone process it inherits whatever CPU settings the host application set (like affinity) so such effects are possible but it's not Avisynth fault.

[SubJunk]

Sure, the thread-detection has always seemed weird. On my previous quad-core CPU I had to run SetMTMode(x,8) to get full CPU usage, even though it only had 4 cores/threads. It seems to detect my current CPU properly, though.
As a rule-of-thumb on AVSForum we usually recommend users enter 1.8* their core count into it (so an 8-core CPU would use SetMTMode(x,14), etc.). Some CPUs work ~80% faster with that value, others crash, in which case the user should enter the real number of cores.
I had always assumed that it was done on purpose by the AviSynth developers *shrugs*

[Atak_Snajpera]

it all depends what filters you use. When I was using mvtools for 50 fps -> 100 fps interpolation I also had to use SetMTMode(x,8 or 10) in order to achieve max speed/cpu usage on my Q6600@3Ghz. For less intensive filtering SetMTMode(x,4) was sufficient.

[SubJunk]

Yeah that could be it, since most of these times I was using mvtools2 or scripts that use it like QTGMC

[yup]

Originally Posted by SubJunk

Sure, the thread-detection has always seemed weird. On my previous quad-core CPU I had to run SetMTMode(x,8) to get full CPU usage, even though it only had 4 cores/threads. It seems to detect my current CPU properly, though.
As a rule-of-thumb on AVSForum we usually recommend users enter 1.8* their core count into it (so an 8-core CPU would use SetMTMode(x,14), etc.). Some CPUs work ~80% faster with that value, others crash, in which case the user should enter the real number of cores.
I had always assumed that it was done on purpose by the AviSynth developers *shrugs*

Hi Subjunk!
I am also increase filtering speed on Q6600 1.5 times replace SetMTMode(x,3) to SetMTMode(x,7) load CPU increase from 40 to 60%, if increase up to SetMTMode(x,8) load CPU increase up to 100% but filtering speed drop.
Script contain QTGMC.
Interesting.
Subjunk! Thanks for trick.
yup.

[VideoFanatic]

I've replaced the avisynth.dll in the System 32 folder with the file from MT. However when I try to encode the video in Simple x264 Launcher it crashes and I get the following message "avs2yux_x86.exe has stopped working". Yet if I encode with HC Encoder I don't get any problems.

[VideoFanatic]

The following works.

setmtmode(5,3)
Mpeg2Source("L:\Raw 2001\01 Raw January 2001\Jan 8\Raw January 08 2001.d2v", CPU=6)
setmtmode(2,0)

However when I add the following to the bottom, HC Encoder encodes the video with a white glow around the edges of objects. It won't encode at all in Simple x264 Launcher and it crashes saying that "avs2yuv_x86.exe has stopped working".

McTemporalDenoise(settings="medium", interlaced=true)

[VEGITA]

I have similar problems with QTGMC, I can open the script in AvsP but when I load it in MeGUI I get a gray output in preview window and it just freezes after I close the preview window.
Script:

SetMemoryMax(512)
SetMTMode(3 )
LoadPlugin("D:\MeGUI_2028_x86\tools\dgindex\DGDecode.dll")
DGDecode_mpeg2source("C:\ohi04.d2v", info=3)
LoadPlugin("D:\MeGUI_2028_x86\tools\avisynth_plugin\ColorMatrix.dll")
ColorMatrix(hints=true, threads=0)
SetMTMode(2)
QTGMC( Preset="Medium", SourceMatch=1, EdiThreads=1 )

[yup]

holygamer and VEGITA!
Your problem related to DGIndex.
At DGIndex demux to m2v Your VOB files.
MeGUI at tab tools have AVS script creator from source try ffmpegsource instead of DGDecode.
yup.

[Adub]

Yeah, if I remember correctly you want to be careful when calling a source function in a multithreaded fashion. Try loading your source with DGDecode and THEN loading SetMTMode().

[Groucho2004]

Originally Posted by Adub

Try loading your source with DGDecode and THEN loading SetMTMode().

That would certainly solve the problems but might be pretty slow.