AVS › AVS Forum › Video Components › Home Theater Computers › Avisynth Script for doubling video frame rates
New Posts  All Forums:Forum Nav:

Avisynth Script for doubling video frame rates

post #1 of 1963
5/3/08 at 9:09pm
Thread Starter 
Ok folks, I've been getting a lot of responses and questions to the way I achieve the "motion morphing, 120hz" look on my videos from a PC rather than letting a new LCD screen do the work. Not only do I feel the results are better than the TVs, but depending on your hardware, you'd be saving a lot of $$$. Now my friend Kevin wrote this script after I told him I wanted to buy a 120hz projector. He advised me to wait until he could find a software solution, and sure enough he did with some plugins and tinkering around. I'm going to paste you folks right here the settings I'm using. I hope it makes sense to some of you out there. Also I'd like to mention I'm using a e6300@2.8ghz to get very nice results in MPC. Also I am using the Haali splitter on the 720p MKVs. Boy do they look great. If any of you folks have better hardware, or tinker around with this script and find BETTER results, please let us all know!

Grab MVtools Here
Grab Avisynth MT Here


SetMtmode(2,10)
source=ffdshow_source()
source=changefps(source,source,true)
# assume progressive PAL 25 fps or NTSC Film 23.976 source
backward_vec = source.MVAnalyse(blksize=16, isb = true, chroma=false, pel=1, searchparam=1, idx=1)
# we use explicit idx for more fast processing
forward_vec = source.MVAnalyse(blksize=16, isb = false, chroma=false, pel=1, searchparam=1, idx=1)
source.MVFlowFps(backward_vec, forward_vec, num=2*FramerateNumerator(source), \\
den=FramerateDenominator(source), mask=0, idx=1)
distributor()
Reply
Reply

AVS Top Picks

post #2 of 1963
5/4/08 at 1:07pm
Thread Starter 
If you folks jsut want to test things out on your hardware, a quick and easy way is to go into FFdshow and go into Deinterlacer - > Frame Rate doubler. I'm using 1 pixel motionleft & right. It looks ok... give it a shot.
Reply
Reply
post #3 of 1963
5/4/08 at 3:42pm
im pretty new to using avisynth, but THANKS SO MUCH for this.
all i need is avisynth, ffdshow, and mpc, right?
Reply
Reply
post #4 of 1963
5/4/08 at 6:19pm
Quote:
Originally Posted by blazed View Post

im pretty new to using avisynth, but THANKS SO MUCH for this.
all i need is avisynth, ffdshow, and mpc, right?

You also need MVTools.

I was unable to get his script to work via Media Player Classic Home Cinema, though.

When I attempted to use it, the player would just crash immediately with a DLL error in mvtools.dll (That was when having add ffdshow video source was checked)

When I unchecked the add ffdshow video source box, I just got a black picture. When attempting to seek strange things happened but no video, sometimes just a still frame.

My settings looked just like this



No success with some 23.97 fps XviD videos I have.
Reply
Reply
post #5 of 1963
5/4/08 at 7:34pm
After some playing around, I got it to work with FFDShow.

I checked the AVISynth tab, made sure add FFDShow video source was unchecked, had only input colorspaces of YV12 and YUY2 checked and used this script.

Code:
source=ffdshow_source()
# assume progressive PAL 25 fps or NTSC Film 23.976 source
backward_vec = source.MVAnalyse(blksize=16, isb = true, chroma=false, pel=1, searchparam=1, idx=1)
# we use explicit idx for more fast processing
forward_vec = source.MVAnalyse(blksize=16, isb = false, chroma=false, pel=1, searchparam=1, idx=1)
return source.MVFlowFps(backward_vec, forward_vec, num=48000,  den=1001, mask=0, idx=1)
Very similar to your script but I hardcoded num to 48000 and den to 1001.

48000 represents my desired frame doubling of 23.97fps to 48hz

Of course this only works with 23.97fps-24hz videos. Anything else will probably end up looking odd...

Good fun on my Intel Core 2 Duo E8400 @ 3.6ghz ;p
Reply
Reply
post #6 of 1963
5/4/08 at 7:43pm
Thread Starter 
Which do you like more? the script or the info i posted in #2?
Reply
Reply
post #7 of 1963
5/4/08 at 9:57pm
Script. most definitely.
Reply
Reply
post #8 of 1963
5/4/08 at 10:47pm
So what does this do exactly? Is this mostly for xvid/divx or does this work on dvd/hdtv?
Reply
Reply
post #9 of 1963
5/5/08 at 12:28pm
Quote:
Originally Posted by NickB View Post

So what does this do exactly? Is this mostly for xvid/divx or does this work on dvd/hdtv?

Adds intermediate frames for a "MotionFlow" type look to film.

Also, I've been playing with the script and came to terms that MVTools doesn't properly convert some numerator and denominator combinations, like when you use the auto calculation for 2* the FrameNumerator, AVISynth sometimes returns 2997 for Numerator and 125 for Denominator.. if you auto multiply the 2997 by 2 and feed both 5994 and 125 into the MVFlowFPS, it won't work right. It has to be changed to 48000 and 1001...

I made a script to detect 23.976 and 29.97 fps input and use the appropriate values and pass them to MVFlowFPS... it doesn't mess with any odd numbered ones, or shouldn't.

Code:
source=ffdshow_source()
SetMTMode(2,2)
frn = int ( FrameRateNumerator(source) )
frd = int ( FrameRateDenominator(source) )
# If the denominator is 1, multiply the numerator by 1000
frn = ( frd == 1 )  ? ( frn * 1000 ) : frn
# If the denominator is 1, now change it to 1001
frd = ( frd == 1 ) ? 1001 : frd
# If the numerator is 2997 and the denominator is 125, change the numerator to 24000
frn = ( ( frn == 2997 ) && ( frd == 125 ) ) ? 24000 : frn
# If the numerator is 2997 and the denominator is 100, change the numerator to 30000
frn = ( ( frn == 2997 ) && ( frd == 100 ) ) ? 30000 : frn
# If the denominator is 125 and the numerator was changed earlier to 24000, change the denominator to 1001
frd = ( ( frd == 125 ) && ( frn == 24000 ) ) ? 1001 : frd
# If the denominator is 100 and the numerator was changed earlier to 30000, change the denominator to 1001
frd = ( ( frd == 100 ) && ( frn == 30000 ) ) ? 1001 : frd
# If the denominator is 1001, which is the only denominator MVTools seems to work with, multiply the numerator by 2.
frn = ( frd == 1001 ) ? ( frn * 2 ) : frn
# assume progressive PAL 25 fps or NTSC Film 23.976 source
backward_vec = ( frd == 1001 ) ? source.MVAnalyse(blksize=16, isb = true, chroma=false, pel=1, searchparam=1, idx=1) : 0
# we use explicit idx for more fast processing
forward_vec = ( frd == 1001 ) ? source.MVAnalyse(blksize=16, isb = false, chroma=false, pel=1, searchparam=1, idx=1) : 0
# If the denominator is 1001, return the MVFlowFPS version of the source, otherwise return the original source
return (  frd == 1001 ) ? source.MVFlowFps(backward_vec, forward_vec, num=frn,  den=frd, mask=0, idx=1) : source
.. Haven't tested it with PAL stuff... I know the code could stand to be cleaned up and I don't understand the if then else crap in AVISynth mostly at all. Wish the syntax was as easy as C.
Reply
Reply
post #10 of 1963
5/5/08 at 2:58pm
Thread Starter 
Soda, I just ordered new hardware, I'll be messing around with the script. BTW I was talking with my friend Kevin and the script I gave to all of you was the "FAST" one. There's two more scripts that do "good" and "insane" quality. I ordered an Asus Geforce 8200 mATX board with an AMD Phenom 9550 CPU. I'll let you guys in on all the results.
Reply
Reply
post #11 of 1963
5/5/08 at 4:40pm
Thread Starter 
Soda, I just ordered new hardware, I'll be messing around with the script. BTW I was talking with my friend Kevin and the script I gave to all of you was the "FAST" one. There's two more scripts that do "good" and "insane" quality. I ordered an Asus Geforce 8200 mATX board with an AMD Phenom 9550 CPU. I'll let you guys in on all the results.
Reply
Reply
post #12 of 1963
5/5/08 at 4:53pm
Quote:
Originally Posted by sodaboy581 View Post

Adds intermediate frames for a "MotionFlow" type look to film.

Also, I've been playing with the script and came to terms that MVTools doesn't properly convert some numerator and denominator combinations, like when you use the auto calculation for 2* the FrameNumerator, AVISynth sometimes returns 2997 for Numerator and 125 for Denominator.. if you auto multiply the 2997 by 2 and feed both 5994 and 125 into the MVFlowFPS, it won't work right. It has to be changed to 48000 and 1001...

I made a script to detect 23.976 and 29.97 fps input and use the appropriate values and pass them to MVFlowFPS... it doesn't mess with any odd numbered ones, or shouldn't.

Code:
source=ffdshow_source()
SetMTMode(2,2)
frn = int ( FrameRateNumerator(source) )
frd = int ( FrameRateDenominator(source) )
# If the denominator is 1, multiply the numerator by 1000
frn = ( frd == 1 )  ? ( frn * 1000 ) : frn
# If the denominator is 1, now change it to 1001
frd = ( frd == 1 ) ? 1001 : frd
# If the numerator is 2997 and the denominator is 125, change the numerator to 24000
frn = ( ( frn == 2997 ) && ( frd == 125 ) ) ? 24000 : frn
# If the numerator is 2997 and the denominator is 100, change the numerator to 30000
frn = ( ( frn == 2997 ) && ( frd == 100 ) ) ? 30000 : frn
# If the denominator is 125 and the numerator was changed earlier to 24000, change the denominator to 1001
frd = ( ( frd == 125 ) && ( frn == 24000 ) ) ? 1001 : frd
# If the denominator is 100 and the numerator was changed earlier to 30000, change the denominator to 1001
frd = ( ( frd == 100 ) && ( frn == 30000 ) ) ? 1001 : frd
# If the denominator is 1001, which is the only denominator MVTools seems to work with, multiply the numerator by 2.
frn = ( frd == 1001 ) ? ( frn * 2 ) : frn
# assume progressive PAL 25 fps or NTSC Film 23.976 source
backward_vec = ( frd == 1001 ) ? source.MVAnalyse(blksize=16, isb = true, chroma=false, pel=1, searchparam=1, idx=1) : 0
# we use explicit idx for more fast processing
forward_vec = ( frd == 1001 ) ? source.MVAnalyse(blksize=16, isb = false, chroma=false, pel=1, searchparam=1, idx=1) : 0
# If the denominator is 1001, return the MVFlowFPS version of the source, otherwise return the original source
return (  frd == 1001 ) ? source.MVFlowFps(backward_vec, forward_vec, num=frn,  den=frd, mask=0, idx=1) : source
.. Haven't tested it with PAL stuff... I know the code could stand to be cleaned up and I don't understand the if then else crap in AVISynth mostly at all. Wish the syntax was as easy as C.


soda,
sorry for all the lame questions, but after everything is installed, i just copy your script, and paste it in ffdshow under avisynth, right?
Reply
Reply
post #13 of 1963
5/5/08 at 5:36pm
Quote:
Originally Posted by blazed View Post

soda,
sorry for all the lame questions, but after everything is installed, i just copy your script, and paste it in ffdshow under avisynth, right?

Yes, but make sure you have installed the MVTools plugin for AVISynth too.

You can download it from http://avisynth.org.ru/mvtools/mvtools.html

The "SetMtMode" line there needs the AVISynth MT version as well.

So, you'll need FFDShow, AVISynth MT, and MVTools and that should be it.
Reply
Reply
post #14 of 1963
5/5/08 at 5:43pm
Quote:
Originally Posted by sodaboy581 View Post

Yes, but make sure you have installed the MVTools plugin for AVISynth too.

You can download it from http://avisynth.org.ru/mvtools/mvtools.html

The "SetMtMode" line there needs the AVISynth MT version as well.

So, you'll need FFDShow, AVISynth MT, and MVTools and that should be it.

once again, thank you very much sir!
Reply
Reply
post #15 of 1963
5/5/08 at 7:26pm
Quote:
Originally Posted by sodaboy581 View Post

Yes, but make sure you have installed the MVTools plugin for AVISynth too.

You can download it from http://avisynth.org.ru/mvtools/mvtools.html

The "SetMtMode" line there needs the AVISynth MT version as well.

So, you'll need FFDShow, AVISynth MT, and MVTools and that should be it.


Is there anything online that can walk me through how to install and use plugins and various filters for Avisynth? For a novice user, Avisynth has been a huge pain in the butt for me; the one time I tried to throw in the LimitedSharpen filter files into my Avisynth folder, Avisynth in MeGUI gave me an error message.

Right now, I'm just using DGIndex to build me a .d2v file, which I open up in Avisynth creator, and resize to the appropriate resolution with Spline36 (I'm also using tdeint(mode=1) to speed up my 1080i caps to 60fps), which in most cases is 1280x704.

I then use a Level 4.1 720p video profile for the actual encoding.

But yeah, if anyone could spare some time to walk me through what I need that would be sweet. Would even Paypal you $10 for your time. (I'm that frustrated with this)
Reply
Reply
post #16 of 1963
5/5/08 at 7:55pm
Thread Starter 
#1. Place MVtools into the Avisynth/plugins folder.
#2. MT.dll is placed in the Avisynth folder. MT.dll is for people who can multithread. So if you have quad core, it's SetMtMode (2,2) for dual, SetMtMode (2,3) for Tri, SetMtMode (2,4) for quad.
#3. The avisynth.dll is then placed into the Windows/system32 folder.

I'll be bringing my friend Kevin over and he'll post up different settings(for those with the hardware that can push it!). Also as I stated above I just purchased new hardware, so I'll run through the gamut and let you guys have the results of all my tests with various media(Blu-ray, HD-DVD, MKVs).

Avsforum has done a lot for me, and I appreciate some of the responses I've gotten. We're all here to share info and possibly save us $$$ from the greedy companies. My best friend saved me thousands of dollars, I hope these results can do the same for you.

Thanks to Soda for bringing that up, I'll get Kevin to do a proper tutorial tomorrow.
Reply
Reply
post #17 of 1963
5/5/08 at 8:54pm
Quote:
Originally Posted by Bahn Yuki View Post

#2. MT.dll is placed in the Avisynth folder. MT.dll is for people who can multithread. So if you have quad core, it's SetMTmode(4), instead of 2...Tri-Core is 3, and so on and so forth.

This is absolutely wrong, it's SetMtMode(2,x) where x is the number of processors you have.

So SetMtMode (2,2) for dual, SetMtMode (2,3) for Tri, SetMtMode (2,4) for quad.
Reply
Reply
post #18 of 1963
5/6/08 at 5:09pm
Thread Starter 
Quote:
Originally Posted by sodaboy581 View Post

This is absolutely wrong, it's SetMtMode(2,x) where x is the number of processors you have.

So SetMtMode (2,2) for dual, SetMtMode (2,3) for Tri, SetMtMode (2,4) for quad.

This is Bahn's friend Kevin.

Yes, it's SetMtMode (2, x), with x being the number of threads you want running at once. The performance seemed to work better having a high number of threads (6-10), even on a dual core, instead of matching the number of threads to the number of cores.
Reply
Reply
post #19 of 1963
5/6/08 at 9:48pm
Quote:
Originally Posted by Bahn Yuki View Post

#1. Place MVtools into the Avisynth/plugins folder.
#2. MT.dll is placed in the Avisynth folder. MT.dll is for people who can multithread. So if you have quad core, it's SetMtMode (2,2) for dual, SetMtMode (2,3) for Tri, SetMtMode (2,4) for quad.
#3. The avisynth.dll is then placed into the Windows/system32 folder.

I'll be bringing my friend Kevin over and he'll post up different settings(for those with the hardware that can push it!). Also as I stated above I just purchased new hardware, so I'll run through the gamut and let you guys have the results of all my tests with various media(Blu-ray, HD-DVD, MKVs).

Avsforum has done a lot for me, and I appreciate some of the responses I've gotten. We're all here to share info and possibly save us $$$ from the greedy companies. My best friend saved me thousands of dollars, I hope these results can do the same for you.

Thanks to Soda for bringing that up, I'll get Kevin to do a proper tutorial tomorrow.

yes i agree 100%. almost everyone here at AVS is very kind and helpful.
Reply
Reply
post #20 of 1963
5/6/08 at 10:00pm
has anyone tried it ?? How are the results ? Can someone post screen shots with and without the script/method described above ?
Reply
Reply
post #21 of 1963
5/6/08 at 10:09pm
Quote:
Originally Posted by ajamils View Post

has anyone tried it ?? How are the results ? Can someone post screen shots with and without the script/method described above ?

Screenshots will do nothing for demonstrating this filter.

This filter affects motion only.. though it can cause some artifacting during videos, it's still somewhat cool.

Also, sorry if I came off as an ass with that "absolutely wrong" thing, it's just setting the wrong first number for Mt mode may cause peoples' scripts to crash ;x I mean, if they have anything else in there.

It's a pretty sensitive setting.

Might turn some people off from trying this
Reply
Reply
post #22 of 1963
5/7/08 at 3:31am
Thanks Yuki!

This is kickass. KICK ASS! It works on my setup (quad-core Q6600 @ 3.0GHz). I'm doing some fine tuning. She eats up too much CPU now.

Update: I'm using it mainly for 24fps (24/1.001) film content, interpolating to 29.97fps to get rid of 3:2 judder for my 60Hz plasma TV. It definitely works, no more judder!

I found that for my quad-core, setting the SetMtMode to (2,4) is better than (2,10). Works for 1080P content as well! CPU load pretty near 100% though.

But for fast motion, there are a lot of artifacts that look like 'bubbles' around fast moving objects. For example, the chase scene in Bourne Ultimatum is quite unwatchable. More experimenting with the settings for me!
Reply
Reply
post #23 of 1963
5/7/08 at 7:52am
Thread Starter 
My new hardware comes in today, sadly I work till 7PM. So it's unlikely I'll be able to even GET my stuff till tomorrow morning. I can try building it all tomorrow night, or let my buddy Kevin do it over the weekend. I'm thinking of letting him do it so he can setup something with all the software and what not.
Reply
Reply
post #24 of 1963
5/7/08 at 7:56am
Quote:
Originally Posted by hardc0re View Post

I found that for my quad-core, setting the SetMtMode to (2,4) is better than (2,10). Works for 1080P content as well! CPU load pretty near 100% though.

With the above setup on my E8400 @ 3.6ghz, I only seem to be using 36% CPU on average.

Also, even though I've defined the SetMtMode, it seems to only work against one of my processors. *shrug*

Running SpeedFan and Task Manager both reveal that usually my second core is the one doing most of all the work with this filter...

It's okay, though, no problem. I'd really only need to use the second core with higher resolution movies or if I tried the higher quality motion detection settings, I guess.

I've installed AVISynth MT correctly by copying the MT.dll into the Plugins folder and moving MT's version of AVISynth.dll into the system32 folder, but I think this script doesn't correctly use all of the cores while in FFDShow... at least for me. Perhaps it'd do better when feeding a movie to something like VirtualDub for conversion purposes to a final format.

I've tried with SetMtMode and different thread numbers and even adding Distributor to the end of the script.

Like I said, though, not a big deal for me as long as it's working without stuttering and jerking.
Reply
Reply
post #25 of 1963
5/7/08 at 8:02am
Thread Starter 
soda on my rig, it's using both cores. I'm getting 50% on the 720p MKV film with Haali splitter. It looks gorgeous. Then again I'm using an e6300@2.8 ghz. Process whole image, Avisynth, all four colorspaces, and buffer are all CHECKED. BTW Buffer back/Ahead has 10/10. Don't know if that changes anything for you guys...
Reply
Reply
post #26 of 1963
5/7/08 at 8:10am
Quote:
Originally Posted by Bahn Yuki View Post

soda on my rig, it's using both cores. I'm getting 50% on the 720p MKV film with Haali splitter. It looks gorgeous. Then again I'm using an e6300@2.8 ghz. Process whole image, Avisynth, all four colorspaces, and buffer are all CHECKED. BTW Buffer back/Ahead has 10/10. Don't know if that changes anything for you guys...

You might as well uncheck RGB24 and RGB32, though. MVTools specifically says it only works with YV12 and YUY2 images...

I don't know what's up with mine... you should check your Task Manager to be sure it's being evenly distributed amongst the cores...



As you can see here, the core on the right is clearly doing most of the work. The left core, I believe, is just doing the Lanczos resizing crap on my rig.

Not sure, though...! Maybe the multicore mode doesn't evenly distribute stuff and mine is working fine. *shrug*

EDIT: Also, checking the buffer ahead/back thing causes the script not to work.
Reply
Reply
post #27 of 1963
5/7/08 at 8:26am
Thread Starter 
If I could host pics, I'd gladly show you what I got on here. I have the buffer checked. I'm only using the script, nothing more. No resizing or any of that. Just "Avisynth" is checked.
Reply
Reply
post #28 of 1963
5/7/08 at 8:45am
Quote:
Originally Posted by hardc0re View Post

But for fast motion, there are a lot of artifacts that look like 'bubbles' around fast moving objects. For example, the chase scene in Bourne Ultimatum is quite unwatchable. More experimenting with the settings for me!

yes, all these methods(ffdshow frame doubler, avisynth assume) basically do frame blending.

it looks so awesome on slow motion(starwars intros), but it looks very bad with fast movements.

nothing beats Reclock in 24fps and your display in 24/48Hz
Reply
Reply
post #29 of 1963
5/7/08 at 6:36pm
Quote:
Originally Posted by leeperry View Post

yes, all these methods(ffdshow frame doubler, avisynth assume) basically do frame blending.

it looks so awesome on slow motion(starwars intros), but it looks very bad with fast movements.

nothing beats Reclock in 24fps and your display in 24/48Hz

reclock does something similiar?
Reply
Reply
post #30 of 1963
5/7/08 at 6:54pm
Quote:
Originally Posted by blazed View Post

reclock does something similiar?

No, all Reclock does is make sure the video is perfectly in sync with your display. Eliminating judder.

It doesn't add extra frames to make the motion look more smooth.
Reply
Reply
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Home Theater Computers

AVS Top Picks

AVS › AVS Forum › Video Components › Home Theater Computers › Avisynth Script for doubling video frame rates