Avisynth 2.6 MT

[Groucho2004]

Originally Posted by lansing

When I ran a script like this on AVSmeter, the line that reports "active MT mode" was 0.

SetMtMode(2)
LimitedSharpenFaster()

Post the Avisynth version AVSMeter reports and your complete script.

[lansing]

avsmeter reports:
Avisynth 2.60 build:August 28 2012

MPEG2Source("mt_test.d2v")

SetMtMode(2)
LimitedSharpenFaster()

[IanB]

A SetMtMode statement must be the first line of the script.

[Groucho2004]

I just tried several MT modes with the latest MT version and AVSMeter reports them correctly. No idea why it does not work for you.

Edit: Ouch, it seems that Ian was the first to see the forest for the trees.

[lansing]

tried this, but still nothing's change and avsmeter still reports 0. Must be something wrong with my computer but I can't find the problem.

SetMTMode(1,0)

MPEG2Source("mt_test.d2v")

SetMtMode(2)
LimitedSharpenFaster()

[Groucho2004]

Just put "SetMTMode(5)" in the first line.

[lansing]

Originally Posted by Groucho2004

Just put "SetMTMode(5)" in the first line.

still the same

[Groucho2004]

Sorry, I'm pretty much out of ideas. Probably a long shot - Maybe something in your "autoload" directory is interfering?

[lansing]

Originally Posted by Groucho2004

Sorry, I'm pretty much out of ideas. Probably a long shot - Maybe something in your "autoload" directory is interfering?

ok i finally got the mt working. After uninstalling Avisynth, I need to delete the entire folder that was left in the program files directory, and that was what got it back working. Previously I tried only empty the plugins folder and that didn't work.


UPDATE:

After further investigation, I was able to find the problematic avs script in the plugins folder, named tbcv01.avs, one i got back in 2008. Removing it will solve the problem. I'll leave a note in the avisynth plugin wiki about this issue.

[fbs]

Which mvtools2.dll should I use with this? I've getting lots of crashes after some hours of processing..

[martin53]

Please allow me to reveal myself as novice. I am using 2.60MTalpha_SEt 8/28/12 and obviously, DeleteFrame(0,0) does not delete two frames, but just one.

Question: is there, and if so where, a bugtracking list, and is this issue maybe already known?

Sorry for causing effort with this probably misplaced post.

[IanB]

DeleteFrame(0,0) is only supposed to delete 1 frame.

The input list is internally sorted, deleting duplicates. The coding choices were to ignore duplicates or throw an error, it was decided by a very small margin that ignoring duplicates would be a more useful implementation.

To delete the first 2 frames either do :-
DeleteFrame(0, 1)
or
DeleteFrame(0).DeleteFrame(0)

[martin53]

Thanks a lot, reasonable.

[mark0077]

Hi, does anyone know how to get around the problem of mpc-hc not closing down properly when using avisynth. I have read on some threads that this is due to a problem somewhere in avisynth / mt? I am using SVP Interframe scripts with the latest avisynth from this thread, and whenever avisynth is enabled in ffdshow, mpc-hc refuses to gracefully shut down about 30% of the time. Sometimes it silently stays there in task manager, other times it will give a program not responding windows dialog.

Any hacked workarounds that has proven to work for anyone or does anyone know the reason for this?

[ney2x]

Originally Posted by mark0077

Hi, does anyone know how to get around the problem of mpc-hc not closing down properly when using avisynth. I have read on some threads that this is due to a problem somewhere in avisynth / mt? I am using SVP Interframe scripts with the latest avisynth from this thread, and whenever avisynth is enabled in ffdshow, mpc-hc refuses to gracefully shut down about 30% of the time. Sometimes it silently stays there in task manager, other times it will give a program not responding windows dialog.

Any hacked workarounds that has proven to work for anyone or does anyone know the reason for this?

What build and revision of ffdshow-avisynth are you using? Have you tried ffdshow builds from xvidvideo.ru or clsid rev4486? I am also experiencing freeze or memory leak of MPC-HC / BE whenever I used xhmikosr ffdshow-avisynth latest builds.

[mark0077]

Hi ney2x, I try to keep upto date with ffdshow builds from xhmikosr's page here http://xhmikosr.1f0.de/ (currently using build 4487)and avisynth 2.6 MT builds from this thread (currently using 2012.08.28: http://www.mediafire.com/file/4dm34k...rk/avisynth.7z). I'll try a different build of ffdshow now from xvidvideo.ru and report back.

EDIT: Wow you're right, I havn't been able to reproduce with the xvidvideo one at least. Opened a video 20 times and got 0 crashes of mpc-hc. Usually I would get at least 6 or 7. I'll ping xhmikosr

[ryrynz]

Yeah I already mentioned this in the ffdshow thread, his ICL12 builds are broken.

[nibus]

Originally Posted by fbs

Which mvtools2.dll should I use with this? I've getting lots of crashes after some hours of processing..

Me too.. tried a bunch of mvtools2.dll's with no luck, all with different crashes. Reverting back to the last version of MT from this thread to see if that helps.

[bcn_246]

Is there any way to get the MT.dll to work with AviSynth v2.6... or plans to build one... I have tried v0.7 and it (understandably) throws up an error regarding the wrong avisynth.dll version. SetMTMode() gives a speed improvement, but MT("filter") is vastly faster. This is the only reason I still use v2.58.

[SEt]

If you recompile MT.dll it'll probably work the same.