I made a mt 2.5.8 avisynth.dll and mt.dll

[Gavino]

Originally Posted by burfadel

I believe using the combined functions such as
Filter().Filter2(...
Is a bad idea with the MT avisynth as the combined function will be passed as a complete fuction, and not separate functions and threads (so you negate the benefit)?

No, that only applies when using the explicit MT function, ie MT("Filter().Filter2()...)".

With SetMTMode switched on, the MT Avisynth treats each filter in a chain distinctly, since this is handled by changes to the parser in the amended avisynth.dll.

[leeperry]

nice! 2.5.8 should allow mod2 in LSF, where 2.5.7 is mod4 only

but I've tried it on a few mod2 samples, and sometimes it works....but most of the time it's very slow and crashes

[burfadel]

Originally Posted by Gavino

No, that only applies when using the explicit MT function, ie MT("Filter().Filter2()...)".

With SetMTMode switched on, the MT Avisynth treats each filter in a chain distinctly, since this is handled by changes to the parser in the amended avisynth.dll.

Ah ok! thats good to know

The Mpeg2source filter when decoding HD material doesn't like it when SetMTmode is set! It works fine set to 2 for standard definition 720x576 material though, so this may need to be taken in to consideration for other people that different resolutions may lead to different compatibility! Easiest way around this is just to set MT mode after the source filter!

[leeperry]

humm yeah, it crashes all the time w/ mod2...back to 2.57

[lych_necross]

I've got the same problem with mod2 files... Oh well, 2.57 works. Does anyone know if ConvertFPS( benefits with either SetMTMode or MT( ?

Edit: I test convertfps with both MT and SetMTMode and I found no discernible difference on my system (others may differ).

[Jeremy Duncan]

Originally Posted by leeperry

nice! 2.5.8 should allow mod2 in LSF, where 2.5.7 is mod4 only

but I've tried it on a few mod2 samples, and sometimes it works....but most of the time it's very slow and crashes

I have made my version of the dll the kind person made. I used their src and fixed some code.

Go see!

Edit.
2 days and nobody says how the dll I made did for them?
It is different than the one seraphy made!
It should do the mythical mod2 you talk about...try it out and tell us what it did?

[lych_necross]

Hi Jeremy, I tried your version of the dll and it seems to work alright. No problems so far. I'll test it some more and report any problems. The only thing I noticed is that when you display the avisynth version in a script, it still says Seraphy (just add version() to the end of a script). You might want to alter that to reflect your additional changes.

@leeperry
Does it work on your end?

[cweb]

Originally Posted by lych_necross

Hi Jeremy, I tried your version of the dll and it seems to work alright. No problems so far. I'll test it some more and report any problems. The only thing I noticed is that when you display the avisynth version in a script, it still says Seraphy (just add version() to the end of a script). You might want to alter that to reflect your additional changes.

It worked for me too. HC encoder says the version is 2.5.8.5, creation date 31-12-2006 (?)..

thanks for the dll.

[leeperry]

Originally Posted by lych_necross

@leeperry
Does it work on your end?

looking good indeed!
I've got a 672x384 AVI file w 7/4 DAR(that becomes 1022*584 after resizing to 1024*768 in ffdshow), I've tried to open it like 20 times...it only crashed once(same as the old buggy DLL), basically it went really slow and crashed my player after a few secs.

it also crashes a lot when I seek..

when it's mod2, it seems to stall for a few seconds before starting playback

if only ffdshow could resize to 1024* when I ask it to, but it doesn't seem possible..

[alph@]

hi jeremy, thanks for your work, the question , why your version of avisynth dll mt is so big '1287 ko' instead of the other one wich is smaller '336 ko'

[Guest]

He probably built the debug version.

[Jeremy Duncan]

I updated the dll in the first post.

I don't know why it's so big.

[Guest]

Set the project to "Release" instead of "Debug".

Build/Configuration Manager.

[squid_80]

I think the official builds have been UPX'd or similar.

[lych_necross]

Yes, the official builds have been UPX'd.

[Jeremy Duncan]

Originally Posted by neuron2

Set the project to "Release" instead of "Debug".

Build/Configuration Manager.

I did. For all the libs: soundtouch, softwire, pfc. And the avisynth dll.

"when it's mod2, it seems to stall for a few seconds before starting playback".
if you specify the fps and then run your code under that it should be ok.
See assumefps

My film is 29.970 fps I think. So I use assumefps like this:
ffdshow_source()
MT("
assumefps(30000, 1000, false)
",2)

The false is to show no audio is used in the setting.

The stall is due to the avisynth dll having 64 to 32 bit conversion. I think.

[alph@]

'Yes, the official builds have been UPX'd' , yes it is , thanks

[Gavino]

Originally Posted by Jeremy Duncan

I use assumefps like this:
ffdshow_source()
MT("
assumefps(30000, 1000, false)
",2)

It's pointless putting MT around assumefps since the filter does not process any pixels - it just changes the clip properties.
Using MT here will actually slow it down instead of speeding it up - just use assumefps on its own.

[Jeremy Duncan]

Originally Posted by Gavino

It's pointless putting MT around assumefps since the filter does not process any pixels - it just changes the clip properties.
Using MT here will actually slow it down instead of speeding it up - just use assumefps on its own.

I tried my frame doubler with no mt around assumefps and it crashed. Not right away, but after some time.
Putting it in mt solved this problem.

I made another avisynth mt dll today and put it in the first post.
I included a build log so you can see it's a release and not a debug.

This version had most of the convert warnings fixed.
It's more stable I think after testing it with my frame doubler in ffdshow.

[Leak]

Originally Posted by Jeremy Duncan

I tried my frame doubler with no mt around assumefps and it crashed. Not right away, but after some time.
Putting it in mt solved this problem.

Except that AssumeFPS plain doesn't work in ffdshow. I made sure of that, as no matter what you it'll destroy any synchonization between audio and video since AviSynth only operates on the audio.

AssumeFPS all you want - ffdshow will use the timestamps of the input frames to calculate the output frame timestamps. If your file itself has it's framerate wrong remux it with the correct framerate.

np: Fink - If Only (Distance And Time)