Log in

View Full Version : I made a mt 2.5.8 avisynth.dll and mt.dll


Pages : [1] 2 3 4 5 6

Jeremy Duncan
7th February 2009, 22:49
src (http://www.mediafire.com/?tmjdmn2igfm)
dlls (http://www.mediafire.com/?kghxrwtzmrx)
Microsoft Visual C++ 2008 Redistributable (http://www.microsoft.com/downloads/details.aspx?FamilyID=9b2da534-3e03-4391-8a4d-074b9f2bc1bf&displaylang=en)
msvcp71 and msvcp71 plugins (http://www.megaupload.com/?d=SP5FE2KG)

dlls. Updated january 10, 2010. These were compiled using the windows 7 sdk so it may be more compatible with windows 7. (http://www.mediafire.com/?zy2xm2ejvzg)
________ Notes ________

\\\\\ Once installed. Reboot twice.

\\\\\ How do I use these new avisynth and mt dll's you made?
install avisynth 2.5.8
substitute the avisynth dll in windows\system32 folder with the one I made
ADD the mt.dll in C:\Program Files\AviSynth 2.5\plugins folder
done.

\\\\\ It's crashing on me.
Install the "Microsoft Visual C++ 2008 Redistributable"

\\\\\ It's crashing on me and I'm using a windows 32 bit os.
In the system32 folder is there the msvcp71 and msvcr71.dll?

\\\\\ It's crashing on me and I'm using a windows 64 bit os.
In the syswow64 folder is there the msvcp71 and msvcr71.dll?
In the syswow64folder is there a avisynth.dll?

\\\\ I can't build it?
I built them in windows 7 build 7100 on july 2, 2009. I ran visual studio as administrator.

\\\\ Your Avisynth makes the video ugly and the audio choppy.
Reboot. Before I thought that one dll compile build was different from the other. But I was wrong.

I was recompiling the dll everytime to get one that worked, but then I decided to just try removing the dll giving the ugly picture and choppy sound from the avisynth or system 32 folder, and put it on my desktop.
Then I put the dll back in either the system32 folder or the avisynth folder and it gave no ugly picture or choppy sound.

So for some reason when I put the mt or avisynth dll in the folder they should go into (mt in the avisynth folder and avisynth into the system32 folder), sometimes the video player gives ugly bad results.
Simply removing it from the folder and then putting it back in there fixes this, or you may leave it in there and just reboot and it will be fixed.

\\\\ What is different about these dll's than the other SEt builds you munkeyed around with?: October 6, 2009

I updated some files in the src, core folder. I got the new ones from SEt's 2.6 src. I read the bug fix he made in that 2.6 thread of his today and so decided to make a new dll with the fix and thought it would be cool to include other mt files from his src so I did.
I forget which ones though.

\\\\ What is different about these dll's than the other SEt builds you munkeyed around with?: September 11, 2009

I fixed a bug gavino found and I added the mt in the file info tab that was requested.

\\\\ What is different about these dll's than the other SEt builds you munkeyed around with?: August 17, 2009
I shrunk the avisynth.dll using upx.exe. The code I used with upx.exe is in the src distrib folder, nsi file. I use upx.exe version 3.3.0.0

\\\\ What is different about these dll's than the other SEt builds you munkeyed around with?: August 16, 2009
I deleted this line from the main.cpp and avisynth.h in the src core folder:
#define Interlockedincrement _Interlockedincrement

\\\\ What is different about these dll's than the other SEt builds you munkeyed around with?: July 22, 2009

This is second build on July 22. No, now it's july 23 2009.
What did I do?
I found much to my surprise the project wasn't calling all the files in the src folders. So I added those then spent some time optimizing the project settings, making sure mt.dll was made right and then posted them here.
I was going to use upx.exe to shrink the dlls but it didn't work like before, so I didn't shrink the file size this time.

Works pretty good though. :)

\\\\ What is different about these dll's than the other SEt builds you munkeyed around with?: July 22, 2009
This is the build made on July 22, 2009 and not July 17 2009.
Look below to see previous changes I made.

I used the july 17 src and put SEt's stdafx.h file in there, before it was the japan one.
And I put my project settings in the include folder: softwire, soundtouch, pfc.

One other thing I did was shrink the file size.
I think shrinking it made it more stable.

When you install the avisynth dll, reboot Twice. I dunno why but rebooting twice helps make sure it's fine after that. Maybe I'm wrong?

And I'm using tsp's mt.dll in the dlls link above.

\\\\ What is different about these dll's than the other SEt builds you munkeyed around with?: July 17, 2009
What I did was find the different files between the SEt July 12 build and the original Japan src.
Then I guessed the files that SEt modified and the ones I did. It wasn't hard as my adjustments were of a base skill and SEt's were expert.

I then cross checked the ones I changed with the Japan src and the Japan src files were the same as the official avisynth 2.5.8 src.
So I switched the ones I changed for the japan src ones, and kept the ones SEt changed.
Then I kept the include libs: softwire, soundtouch, pfc from the japan version, and the stdafx from the japan version as well. I put all these into the SEt july 12 src.

I will post a list of the files different from the SEt july 12 src from the original japan src below.

This list I changed to the japan src version:

core parser folder
expression.cpp

filters folder
color.cpp
convolution.cpp
edit.cpp
focus.cpp
greyscale.cpp
histogram.cpp
layer.cpp
layer.h
levels.cpp
planeswap.cpp
resample.cpp
resize.cpp
transform.cpp

filters overlay, conditional folders

sources folder
source.cpp

sources, avi folder
AVIReadHandler.cpp

____________________________________________

This version I kept as they were altered by SEt:

Audio folder
audio.cpp ++
avs-soundtouch.cpp ++
supereq.cpp ++

core folder

Avisynth.h ++
Avisynth.cpp ++
avisynth_c.cpp ++
cache.cpp ++
cachemt.cpp ++
main.cpp ++
mt.cpp ++
mt.h ++
softwire_helpers.cpp ++

filters folder
merge.cpp ++


\\\\ I did a comparison of my july 9th, july 11th, 5th version, and SE'ts version from his new thread.

http://thumbnails9.imagebam.com/4186/c1905941854223.gif (http://www.imagebam.com/image/c1905941854223)
http://thumbnails16.imagebam.com/4186/af6ddb41854227.gif (http://www.imagebam.com/image/af6ddb41854227)

Link to see pictures of the stats. In case the picture host is too slow or goes kaput. (http://www.mediafire.com/?miv4dndzim2)

\\\\ I wanna build my own. How do I do it?

Follow the instructions in this link: link (http://forum.doom9.org/showthread.php?t=145130)


A.) You will need to use the sw in the link at the top of the link as the instructions for other versions are different.

B.) The youtube video showing avisynth compilation is for the official 2.5.8 version, not my mt version.
To compile my version you setup visul studio as shown in the video then unzip my src and change to release in configuration manager (in visual studio). Then you build the soundtouch, softwire, pfc then you build avisynth.dll

C.) when you build the softwire, soundtouch, pfc, avisynth.
Highlight the one your going to build then from the "build tab, project only, build only" on the top menu.
You build only the one thing at a time, or else you will get a bunch of errors and that's not cool. :)

D.)

1.) Once the dll is made then go to the avisynth src folder, release and get the avisynth dll and put it on your desktop.

2.) Then go and get the upx.exe from google, windows console version, and put the upx.exe on your desktop.

3.) Then open cmd prompt in admin and go to the desktop using the cd command as shown in the link to how to build the dll. Example: cd C:\Users\aye\Desktop

4.) Then with cmd prompt still open and both the upx.exe and avisynth dll on the desktop, in cmd prompt type: upx avisynth.dll
and then press enter and it will reduce the size of your dll!

5.) Then you put it in place of the other one in the system32 folder and reboot twice and then test your new dll.

@Tron@
9th February 2009, 22:35
Fully agree with the previous speaker!
Very useful to MT version avisynth 2.5.8 But I think no one will be taken for this as it is a long and laborious process!

Few will be able to change and adjust to avisint in MT and therefore unnecessary to wait and hope (at least for this year is already accurately) just so many unnecessary and all here (in the process remake MT)

lych_necross
10th February 2009, 07:17
:search:
This has already been discussed. The MT mod will be integrated into Avisynth in version 2.6.0. I wouldn't expect MT to be updated for 2.5.8 as it is currently based on 2.5.7.5.

Jeremy Duncan
16th February 2009, 06:40
Older stable versions of my avisynth builds and src's:

July 12th

src (http://www.mediafire.com/?nej4djmomw3)
dlls (http://www.mediafire.com/?tlvzmtjjnly)

July 23, 2009
src (http://www.mediafire.com/?djz11jcinjj)
dlls (http://www.mediafire.com/?mi1wrmynvw1)

August 17, 2009
src (http://www.mediafire.com/?m1zmylqdjjv)
dlls (http://www.mediafire.com/?wnxujmydded)

September 11, 2009
src (http://www.mediafire.com/?jjckmgtjmvw)
dlls (http://www.mediafire.com/?o1dccmm1l1t)

gator1102
16th February 2009, 15:46
http://seraphy.fam.cx/~seraphy/
http://seraphy.fam.cx/~seraphy/cgi-bin/cbbs.cgi?mode=one&namber=1990&type=287&space=15&no=0
http://seraphy.fam.cx/~seraphy/cgi-bin/upload/MT_07_with_Avisynth258.rar

@Tron@
16th February 2009, 17:56
http://seraphy.fam.cx/~seraphy/
http://seraphy.fam.cx/~seraphy/cgi-bin/cbbs.cgi?mode=one&namber=1990&type=287&space=15&no=0
http://seraphy.fam.cx/~seraphy/cgi-bin/upload/MT_07_with_Avisynth258.rar


Is it true !? Wow :eek::eek:!!! BIG THX !!! :thanks::thanks::thanks::thanks:

Now testing it !

Fizick
16th February 2009, 18:39
online translation 1 (excite)

DustMT Avisynth2.5.8 - contribution person/seraphy@ curator - (2009/01/12 (Mon) 13:21:43

DustV5 MT conversion of remodelling (with the society you call DustMT selfishly, it seems) is,
but It became unable to use the environment of the house by moving to Avisynth 2.5.8.5.
So, still as for tsp, as Avisynth.dll of MT correspondence (2.5.8) release not done.
http://forum.doom9.org/showthread.php?p=660247#poststop
Because is, taking diff of 2.5.7 and 2.5.7MT, it tried applying to 2.5.8 selfishly.
As for me as for the source of Avisynth you have not read seriously because and,
you do not read either the MT conversion tsp securely, whether or not it does properly, it does not guarantee.
Only the one which it can cope entirely on self responsibility please utilize.
Rash is different from courage.
It will wait wise one for the correspondence tsp.
By the way, because it compiles this with VC2008, (the birthplace VC6 kana? ) Execution time becomes necessary.


online translation 2 (babel fish):

- Contributor/ Seraphy@ manager -(2009/01/12(Mon) 13:21:43)

Without permission it is making remodeling (It seems to be called DustMT on the street) DustV5 MT
It is not possible to use it by having shifted the environment of the house to Avisynth 2.5.8.5.
And Avisynth.dll(2.5.8) for MT has not been released to Mr. tsp yet.
http://forum.doom9.org/showthread.php?p=660247#poststop

Diff of, 2.5.7, and 2.5.7MT was taken and it applied it to 2.5.8 without permission.
I seriously read the source of Avisynth, do not exist, and : because I do not firmly read Mr. tsp's making to MT.
It is not secured can tidy.
Please use can only all actions by the self-responsibility.
Courage and rashness are different. Wise one waits for Mr. tsp's correspondence.

By the way, because here is compiled with VC2008 (Is the head of the house VC6?), run time is needed.

@Tron@
16th February 2009, 20:06
online translation 1 (excite)

So ... its not full version ((((((9 Very bad ...

:confused::(:(:(

Razorholt
16th February 2009, 23:31
@Tron: did you try it yet?

Mug Funky
17th February 2009, 00:08
i'm going to try this out because the machine translation told me it's better to be rash than courageous :)

Jeremy Duncan
17th February 2009, 15:11
@Tron: did you try it yet?

I tried it, and it really works. :)

No problems playing ffdshow avisynth in realtime with this new mt.

I tried seesaw, lsf, spresso, and mvtools v2 frame doubler.

I have a new upload of it if you don't want to unzip a rar.
link (http://files.filefront.com/MT+07+with+Avisynth258zip/;13308431;/fileinfo.html)

I will wait and hope somebody looks at the code to make sure it's safe before I use it and link to it in the guide i made.
I have since ghosted my pc to a earlier state since I tested this grand mt this kind fellow made.

Many thanks mr or ms gator1102

Fizick
17th February 2009, 19:11
It seems, there is no source code explicitlly posted

lych_necross
18th February 2009, 11:28
Woops... source is now posted... nevermind :)

MfA
18th February 2009, 16:04
Have you tried simply asking him for the source code?

RedDwarf1
18th February 2009, 21:39
Would be nice if it works.

burfadel
18th February 2009, 23:29
It works :) I already have fairly good CPU utilisation, but with this it make it almost perfect, and it shows in the higher fps of encoding speed. I take it this doesn't affect the output too much?

cyberbeing
19th February 2009, 00:48
The source code is now available here: http://seraphy.fam.cx/~seraphy/cgi-bin/upload/avisynth258MT.zip
Source is here.
I don't think to post on the Doom9's Forum. (I'm not a member.)

These were modified based on the tsp's Patch,
but can't guarantee to work correctly because I don't understand the content of the change well.
Please use this at your own risk. ;-)

Jeremy Duncan
19th February 2009, 17:40
I can't see any avisynth file that shows major changes from the 2.5.8
And some files are in a format I can't open.

If you would be so kind as to find a avisynth with the changes this fellow made to it, and post it in c++.

:)

lych_necross
20th February 2009, 07:29
You need Visual Studio to open the project files. Other than that, all of the files can be read with either wordpad or notepad.:)

burfadel
20th February 2009, 09:07
The reason why this peaked my curiosity is I just got a Q9400 as an upgrade to my E6600 CPU a couple of days ago.

It works for me, although I don't use complex lengthy avisynth scripts. Just RemovegrainHD, spline64resize, gradfun2db, crop etc

On a sidenote I do believe in using gradfun2db before encoding, it not only takes out banding but other colour distortions too (with a threshold of around 1.6 is what I use). For re-encoding XVID/DIVX around 3. Not only do I believe the output looks better, but at least the encoder isn't trying to encode the banding and colour distortion (or abberations?)! Slight Debanding can also be used during playback :)

The settings I use for the MT is just the basic:

SetMTmode(2,4)

With 4 threads of course because of it being a quad core.

This is the very first line of the avisynth script (well filter list, as using Staxrip), and thats all thats different.

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)?

I do realise SetMTmode(1,4) would be faster but that has compatibility issues with most filters, and the benefit would be almost none I believe over using SetMTmode(2,4).

If you have a an avisynth filter list that isn't too taxing, and slow x264 settings its probably not that beneficial for older CPU's or even more modern dual cores (including the E8xxx). The Avisnth ratio is 1 thread to 2 (in terms of encoding potential). Since x264 for example can make use of 4 threads, the ratio between avisynth and x264 is 1:4, meaning unless you have an extremely fast avisynth filter list x264 is waiting for data from Avisynth.

This is an over-simplification, but consider that even if a dual core was ten times faster than those today, it just means the avisynth filters can run ten times as fast and still pass the frames on to x264 which, although is also running 10 times as fast can still only process at a ratio of 1:2!

If you use fast enough encoder settings on dual core that the encoder has to wait for the avisynth input, it would be beneficial to increase the encoder settings to make use of the CPU time and the loss of encoding speed won't be too excessive.

The only time on a dual core where I see the multithreading patch to be effective is when you have a very complex and slow script, or using a fast encoder.

I use very high settings for my encoding, so this probably becomes more visible if you use still quite reasonable settings. I think the key point when trialling this patch is to encode a couple minutes of a clip, with the typical input type and encoder settings that you usually use, and check the fps you achieve for the encoder. Then try the MT, and do the same. The cpu utilisation may not be a good indication of improved performance. If the encoder is the limiting factor, increasing the speed of avisynth won't give you any benefit and could potentially slightly slow down the system due to thread utilisation (from what I've heard), if Avisynth is the limiting factor then this patch will give you potentially a nice boost :)

Gavino
20th February 2009, 10:55
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
20th February 2009, 17:15
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 :o

burfadel
20th February 2009, 17:53
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
22nd February 2009, 06:52
humm yeah, it crashes all the time w/ mod2...back to 2.57 :o

lych_necross
22nd February 2009, 07:15
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
12th March 2009, 17:29
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 :o

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

Go see! :helpful:

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
13th March 2009, 07:51
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
13th March 2009, 07:59
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
13th March 2009, 10:30
@leeperry
Does it work on your end?
looking good indeed! :eek:
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@
13th March 2009, 21:01
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':eek:

Guest
13th March 2009, 21:24
He probably built the debug version.

Jeremy Duncan
14th March 2009, 01:42
I updated the dll in the first post.

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

Guest
14th March 2009, 03:07
Set the project to "Release" instead of "Debug".

Build/Configuration Manager.

squid_80
14th March 2009, 06:55
I think the official builds have been UPX'd or similar.

lych_necross
14th March 2009, 07:23
Yes, the official builds have been UPX'd.

Jeremy Duncan
14th March 2009, 08:19
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 (http://avisynth.org/mediawiki/ConvertFPS)

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@
14th March 2009, 10:42
'Yes, the official builds have been UPX'd' , yes it is , thanks:)

Gavino
14th March 2009, 11:36
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
14th March 2009, 17:23
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
14th March 2009, 19:28
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)

leeperry
14th March 2009, 19:37
I made another avisynth mt dll today [...] It's more stable I think
righty, will look into it. :thanks: for your efforts!

Jeremy Duncan
15th March 2009, 10:59
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)

changefps still works though?

I have remade a new avisynth mt and put it in the first post.
The last one I made I just suppressed the warnings.
With this new one I went to the first src I made and instead of suppressing warnings I fixed them.

There were other warnings I fixed too.

I tried it on my frame doubler and it is used more cache in the task manager performance tab than my 3rd try.

There are other warnings, but I won't even bother trying to fix those.
Look at the buildlog to see the warnings.

Leak
15th March 2009, 12:09
changefps still works though?
You can't set an arbitrary framerate, but if your filter returns more or less frames the timestamps will be adjusted accordingly.

Otherwise even a simple Bob() wouldn't work.

np: The Fireman - Is This Love? (Electric Arguments)

Jeremy Duncan
15th March 2009, 13:58
You can't set an arbitrary framerate, but if your filter returns more or less frames the timestamps will be adjusted accordingly.

Otherwise even a simple Bob() wouldn't work.

np: The Fireman - Is This Love? (Electric Arguments)

I just set the changefps to the fps in the dvd.
See the ffdshow configuration below.

________ advanced ffdshow: framerate doubler. (ntsc 60hz monitor compatible) ________

Codecs tab
Set Mpeg2 to Libmpeg2, and check "DVD decoding".
Set Avisynth to Avisynth, Raw video to All supported

Subtitles tab, Unchecked
Uncheck "Decode closed captions"
Uncheck "Accept embedded subs"
Uncheck "Accept SSA, ASS, ASS2 Subtitle (experimental)
Vobsub subpage, uncheck Vobsub Enable.

Avisynth tab checked
YV12 checked,
Add FFdshow Video source checked,
3:2 Pulldown box: Ignore Pulldown checked,
check Buffer back/Ahead: 0, 2

setmtmode(mode=1)
changefps(30000, 1001)
super = MSuper(pel=2,hpad=8,vpad=8)
backward_vec = MAnalyse(super,chroma=false, blksize=16, overlap=4, isb = true, search=5, searchparam=1)
forward_vec = MAnalyse(super, chroma=false, blksize=16, overlap=4, isb = false, search=5, searchparam=1)
MFlowFps(super, backward_vec, forward_vec, num=2*FramerateNumerator(last), \
den=FramerateDenominator(last), mask=0, ml=49)
distributor()

Resize & aspect tab checked
Multiply by:
1.844 (for 1280x720 16:9 aspect ratio)
2.729 (for 1920x1080 16:9 aspect ratio)
Process Pixel aspect ratio internally checked
No aspect ratio correction checked
spline
Luma Sharpen: 0.00
Accurate rounding checked

Queue & Output tab
Queue output samples unchecked
Very unstable. May cause player to crash.
No box is checked.

Output tab
rgb32 checked
high quality yv12 to rgb conversion checked

rgb conversion tab
ycbcr: itu-bt 601
contrast: standard
Output levels: Tv/Projector
Reclock: Be sure to use reclock vsync

lych_necross
16th March 2009, 08:14
If you want to double the framerate, why not just use ConvertFPS(framerate*2)
If you don't like blend mode, set the output to yuy2 and use
ConvertFPS(framerate*2, zone=80)

Jeremy Duncan
16th March 2009, 09:58
If you want to double the framerate, why not just use ConvertFPS(framerate*2)
If you don't like blend mode, set the output to yuy2 and use
ConvertFPS(framerate*2, zone=80)

I solved the problem.
THe solution was to use info by itself in the ffdshow avisynth tab and then to use the right mt.

I was using setmtmode before.
I tried the mt in the mvtools read me and with the info info() gave me I got it going.

:thanks: though.

Edit,

If I hadn't seen the chart in th mediawiki in the fps section I would still be trying different settings.

leeperry
16th March 2009, 10:30
well the framerate doubler used to be in ffdshow, but Haruhiko took it off for some reason...and doesn't want to put it back :D

anyway, your latest build seems to work perfectly fine! maybe you can work on Haali's Renderer now...j/k :p

Leak
16th March 2009, 11:30
well the framerate doubler used to be in ffdshow, but Haruhiko took it off for some reason...and doesn't want to put it back :D
Say what? (http://ffdshow-tryout.svn.sourceforge.net/viewvc/ffdshow-tryout?view=rev&revision=2642)

leeperry
16th March 2009, 13:15
oops...so he did put it back after all :cool:

anyway I needed mod2 in MT avisynth because the ffdshow resizer doesn't do what I want(resize to 1024 wide) :
https://forum.doom9.org/showpost.php?p=1261217&postcount=6836

but maybe there's some obscure AR voodooness I'm clueless about, as it works fine if I force 1.78 AR :rolleyes:

also, why is it mandatory to have avisynth.dll in /system32/? because you enforce it in ffdshow?

Leak
16th March 2009, 15:22
also, why is it mandatory to have avisynth.dll in /system32/? because you enforce it in ffdshow?
I don't think it's mandatory to have it in system32, it just has to be somewhere that Windows will look for it, like one of the directories specified in the PATH environment variable or in the player application's current directory, wherever that is...

I could be wrong, though - I always install AviSynth in the default location, i.e. system32.