MT 0.7(+custom avisynth)a filter to run filters multithreaded. Usefull for SMP or HT

[tsp]

aberforthsgoat : are you using version 0.5 of mt and the included avisynth.dll (and copied to the c:\windows\system32 directory)? And please when using both setmtmode and mt inside the same script try testing of it is actually faster(that is fps not cpu utilization) than not using both because there are some overhead by using both filters together.

TSP,

I didnt realise you wernt supposed to use setmtmode and mt() - there is a large thread on avsforums about using Limitedsharpenfaster and its become 'assumed' (incorrectly by the sound of it) that people should use both.

So people should use either MT(lsf) or SetMTmode() and not both?

Cheers,
Bitey

[aberforthsgoat]

Originally Posted by tsp

aberforthsgoat : are you using version 0.5 of mt and the included avisynth.dll (and copied to the c:\windows\system32 directory)? And please when using both setmtmode and mt inside the same script try testing of it is actually faster(that is fps not cpu utilization) than not using both because there are some overhead by using both filters together.

Thanks for the response!

I *do* have the whole 0.5 package installed - I'm dead sure of that. But as far as I can tell, I mt() is making a big difference, but setmtmode is making no difference at all in my scripts.

BTW, it's hard to get much of a read on the fps because the OSD flickers constantly between two numbers - I think I'm seeing 21 and 32. With mt() I get a steady flicker between the two. With setmtmode(2) by itself I seems to stick on the 21 more - and occasionally dip all the way down to 9 or 16 or the like.

Peace,

Mike

[foxyshadis]

According to the first page, there's no SetMTMode(0), so something like this to reduce the overhead isn't possible, am I correct?

SetMTMode(3)
Filter()
SetMTMode(0)
MT("Filter2()")
SetMTMode(2)
...

aber, try avstimer to get accurate readings on the speed on scripts (although I haven't read through this thread to see if it's threadsafe), or just time a complete null render with and without.

[Boulder]

It used to be possible to disable multithreading where needed by calling SetMTMode(0), don't know if it's been removed.

[tsp]

Mr.Bitey: I don't say you shouldn't use setmtmode with mt. I just say that sometimes it's slower to use both together and that you should always check if the framerate is faster with both setmtmode and mt compaired to using mt alone. Another thing the SetMTmode should be the first line in the script before import("") and this script disables SetMTMode completely because only mode 5 is used:

#note setmode before import
SetMTMode(5) 
Import("C:\Program Files\AviSynth 2.5\plugins\LimitedSharpenFaster.avs")
MT("HQDN3D(1)")
LanczosResize(1440x960)
MT("LimitedSharpenFaster ss_x=1.0,ss_y=1.0,Smode=3,strength=100,overshoot=7)")

aberforthsgoat: try using virtualdub and take time on how long it takes to process the script.

foxyshadis : There are no mode 0. Use mode 5 or 6 instead. mt 0.5 internaly calls SetMTMode(5) and restores the old mode afterwards so you don't have to add SetMTmode(5) before mt and restore the old mode after.

TSP: Thanks for the clarification. I think i'll go revisit my scripts ;-) I do recall SetMTMode(5) seemed to run quicker when used with MT() in my Limitedsharpenfaster script.. Its going to be a long night I think You also mention SetMTMode() should be the first line - so if im using a .avsi named version of limitedsharpen - I should rename it to .avs and manually include?

Cheers,
Bitey

[tsp]

Mr.Bitey
one way to test if it is necesary to rename the avsi is to add this after the first SetMTMode:

subtitle(string(GetMTMode)))

it should show the current mode. If it is larger than zero the SetMTMode works correct.

[Kador]

do you have plans to integrate your avisynth.dll in the mail avisynth development (dir the 2.5.7 final for example) ?

[tsp]

kador it will be in the 2.6 release. The changes are too big to be included in the 2.5 version.

[Serbianboss]

Today i tested with version 0.5.

Firstly i copy MT.dll in avisynth plugin directory and copy avisynth.dll in system32.

I am using A64 X2 3800+, capturing to DV avi and than with avisynth and CCE i encode to mpeg2 (720x576)

And always use Convolution 3d filter (avisynth filter).

I tested on 15 minute material and took 36 minute in 2-pass CBR in CCE without crash.


This is code:

SetMTMode(2)
LoadPlugin("Convolution3d.dll")
avisource("D:\CAPTURE\bmw.avi")
ConvertToYuY2(interlaced=true)
SeparateFields()
odd=SelectOdd.Convolution3D (1, 32, 128, 16, 64, 10, 0)
evn=SelectEven.Convolution3D (1, 32, 128, 16, 64, 10, 0)
Interleave(evn,odd)
Weave()
crop(8,4,-8,-12)
AddBorders(8,8,8,8)

With SetMTMode(2) i get 50% speed up in CCE

So i am interesting is OK just to put SetMTMode(2) at begin?

p.s Congratulations to your multithreaded filter.

[Serbianboss]

Now i have one error.

When encoding begin, few minutes after it sais:

Mux video buffer overflow.




When i use Mainconcept encoder i get this error



When i try without scrip everything is OK. What can be this?

best regard

[Serbianboss]

I figure what was problem.

Problem was in CCE. When i use option CBR-system then show me "Mux video buffer overflow". In other case everything as OK.

New results: I encoded 2 hours movie in 2-pass without crach using MT 0.5. It was 40% faster.

TSP, excellent filter.

[tsp]

Serbianboss: It's okay to use that script with setmtmode(2) in the first line. Try watching a minute or so for artifacts that might appear if the filters used is not thread safe.
Good you figured out the error with CCE.

[Serbianboss]

What kind of artifacts you mean?

I encoded two hours and i thing that there no have artifacts.

[Boulder]

Compare the output in VirtualDub, one script with SetMTMode and one without it.

I've noticed that sometimes MVTools-related functions require SetMTMode(5), with SetMTMode(2) there are occasional artifacts - they appear as white/grey horizontal stripes.

[Serbianboss]

I didnt see any artifacts in virtual dub (tested on minute source).
But when in virtual dub go left or right with slider, virtual dub has cloused.

One more thing: With SetMTMode (5) i dont have any increase in speed.

[tsp]

that is because setmtmode(5) disables multithreading for the filters below it.
The artifacts is different from filter to filter. Like using blur and sharpen in the same filter using an older version of avisynth.dll caused excessive blur or sharpen in some of the frames.

[Boulder]

Is the documentation incorrect then? It says that modes 1-6 are available and that mode 5 is a rather safe one.

[tsp]

it is rather safe because only one thread is used so it makes no sense only to use mode 5 alone but it should be used for only part of the script that doesn't work with lower modes like mvtools.