Tag: 60FPS

InterFrame 2.8.2 (Updated 21 May 2015)


InterFrame is an AviSynth script.
Its main use is to give videos higher framerates like newer TVs do. Common names are framedoubling, smooth motion, HFR (high framerate) and 60FPS conversion.
High framerate (HFR at 48fps) was used in The Hobbit and will be used in upcoming films like the Avatar sequels, which will use HFR at 60fps, so why not watch all your movies at higher framerates?



Here is a before and after video comparison:
Original File
InterFrame (default settings with GPU=true)

Code Samples:

Here is a sample of what the AviSynth script could look like.
It shows the recommended syntax and should be used with SET’s AviSynth 2.6 build from here.

SetMTMode(3, Cores)
dss2("video.mkv", fps=23.976).ConvertToYV12()


Dependencies are included in the download.

To use it in your script just call the function InterFrame(Cores=x) (replacing the path with the path to the flow DLL files) and it will automatically choose a good framerate and preset for you.
There are more specifics like optional parameters and examples on this page, which is also included in the download.

There is also a complete guide on how to use it for those with no knowledge about any of this stuff here.
If you have any questions about it please check the guide first, there is a FAQ section and everything 🙂


21/05/2015 – 2.8.2:

  • Updated to SVPflow 1.1.15, which increased speed (thanks, SVP!)

02/05/2015 – 2.8.1:

  • Updated to SVPflow 1.1.14, which increased speed by up to 15% (thanks, SVP!)

10/03/2015 –

  • Updated to SVPflow 1.1.13, which fixed the unused SVConvert function (thanks, SVP!)

05/03/2015 – 2.8.0:

  • Updated SVP libraries (thanks, SVP!) which:
    • Increased speed by up to 20%
    • Reduced memory usage
    • Removed 2 dependencies (from 4 to 2)
  • Updated documentation

03/01/2015 – 2.7.0:

  • Added “fastest” preset, for even more speed but lower quality.

09/09/2014 – 2.6.0:

  • Added new boolean option “FrameDouble”, which when set to “true” will always double the framerate of the input video, unless NewNum is greater than 0.
  • Updated the “Recommended” script in the documentation

11/05/2014 – 2.5.2:

  • Updated SVP libraries (thanks, SVP!) which:
    • Improved quality
    • Fixed bugs

16/12/2013 – 2.5.1:

  • Minor code cleanup
  • Updated SVP libraries (thanks, SVP!) which:
    • Improved quality
    • Improved GPU support
    • Fixed bugs

18/02/2013 – 2.5.0:

  • Minimized artifacts (thanks, Widezu69!)
  • Made motion smoother by default (only in GPU mode)
  • Updated libraries which improve scene-change detection, thanks to SVP

24/01/2013 – 2.4.0:

  • Updated libraries which improve scene-change detection, thanks to SVP

16/01/2013 – 2.4.0 RC1:

  • Fixed the presets Weak and Faster when not using GPU (thanks, Motenai Yoda!)
  • Fixed the Animation tuning (thanks, HolyWu!)

11/01/2013 – 2.4.0 Beta 1:

  • The “Medium” preset is back to what it was in 2.2.0
  • The “Fast” preset is the same as “Medium” was in 2.3.0
  • The new “Faster” preset is the same as “Fast” was in 2.3.0
  • The “Animation” tuning has been changed a lot based on SVP recommendations
  • The “Weak” tuning has been changed a lot based on widezu69’s recommendations
  • The “Smooth” tuning is smoother

24/12/2012 – 2.3.0:

  • Increased speed
  • Decreased blobs/artifacts in high-action scenes
  • Updated libraries which optimise memory use and support more video cards, thanks to SVP

13/11/2012 – 2.2.0:

  • Fixed a syntax bug that appears to have had little-to-no effect (thanks to HolyWu for reporting it).
  • Tweaked scene-change detection again (tightened this time to improve artifacts).

27/06/2012 – 2.1.0:

  • Improved smoothness in high-action scenes by loosening scene-change detection.

05/06/2012 – 2.0.2:

  • Better interpolation stability.
  • Supports more video cards.
  • Better compatibility with AviSynth 2.6.
  • Thanks to SVP.

05/05/2012 – 2.0.1:

  • Updated libraries to support new video cards like GTX 680, thanks to SVP.

03/05/2012 – 2.0:

  • Updated libraries, thanks to SVP.

17/04/2012 – 2.0 RC1:

  • Updated libraries, thanks to SVP.

12/04/2012 – 2.0b4:

  • Reduced instances of warping by fixing usage of SAD mask, thanks to Bernardd for reporting the bug.
  • Further reduced instances of warping by lowering area_sharp (sadgamma).

11/04/2012 – 2.0b3:

  • Updated libraries, thanks to SVP.
  • Changed some fields from string to int (NewNum, NewDen, OverrideAlgo and OverrideArea).

30/03/2012 – 2.0b2:

  • Updated libraries, thanks to SVP.
  • Fixed 3D modes.
  • Fixed “overlap must be even” error.

24/03/2012 – 2.0b1:

  • Rewrite which no longer uses MVTools2 and has better quality and is faster.

23/03/2012 – 1.14:

  • Allow any value for OverrideAlgo.
  • Lots of documentation updates.

29/02/2012 – 1.13:

  • Added the “OverrideAlgo” option for users who wants to override the recommended algo value.
  • Added the “OverrideSadML” option for users who wants to override the recommended sadml value.
  • Updated FFTW to 3.3.1 from 3.2.2.
  • Updated MVTools2 (SVP Build) to from, thanks to SVP.
  • Updated libflowgpu to 1.2.7 from 1.2.6, thanks to SVP.

31/12/2011 – 1.12.3:

  • Updated libflowgpu to 1.2.6 from 1.2.5 which improves ATI GPU compatibility, thanks to SVP.
  • Code reshuffle (no changes)

03/11/2011 – 1.12.2:

  • Updated MVTools2 (SVP Build) to from which improves speed by 2-15%, thanks to SVP.

16/09/2011 – 1.12.1:

  • Updated MVTools2 (SVP Build) to from which synchronises the build with the official beta release.
  • Updated libflowgpu to 1.2.5 from 1.2.0 which improves GPU compatibility, thanks to SVP.

12/09/2011 – 1.12:

  • Improved some warping.
  • Added new UltraSmooth tuning and changed the Smooth tuning. Smooth now has more error-correction than before, while UltraSmooth is roughly what Smooth was before.

05/07/2011 – 1.11:

  • Increased quality of all presets. This change makes fast panning less smooth, but also decreases errors in general.
  • Fixed bug with Placebo preset (thanks to Alek93j and Gavino).

18/06/2011 – 1.10:

  • Increased quality of all presets. Thanks to DeathTheSheep for collaborating.
  • Increased speed of “Ultra Fast” and “Super Fast” presets.
  • “Animation” tuning is now much better and recommended for cartoon/anime inputs.
  • What used to be the “Animation” tuning is now called “Weak”.

23/05/2011 – 1.9:

  • Added support for 2 more types of 3D inputs (Half-SBS and Half-Over-Under).

20/05/2011 – 1.8.1:

  • Fixed stuttering motion particularly visible in cartoons.

04/05/2011 – 1.8:

  • Improved support for 2 types of 3D content – SBS (Side-By-Side) and OU (Over-Under), AKA Top-to-Bottom. This new feature is controlled by the new parameter InputType.

30/04/2011 – 1.7.1:

  • Increased the speed by roughly 40%, thanks to SVP

28/04/2011 – 1.7:

  • Increased the quality of all presets

20/04/2011 – 1.6:

  • Updated libflowgpu from 1.1 to 1.2 which improves the quality of GPU=true mode, thanks to SVP
  • Added more presets (“Faster” and “Super Fast”) based on some realtime user’s suggestions, so now there is a smoother step between presets

13/04/2011 – 1.5.2:

  • Set GPU=false by default instead of true, because of slight quality loss with GPU=true

13/04/2011 – 1.5.1:

  • Fixed bug with GPU=false mode

11/04/2011 – 1.5:

  • Improved the quality of the default, Fast and Placebo presets
  • It now checks for the existence of the mandatory value for FlowPath and displays an alert if it isn’t defined
  • Added the GPU parameter (true for GPU-acceleration, false for CPU-only)

10/04/2011 – 1.4:

  • Added custom mvtools2 and GPU-acceleration thanks to SVP
  • Improved the quality of all presets
  • Updated the sample videos in this post

01/04/2011 – 1.3.1:

  • Added input validation for Tuning and Preset values with descriptive error messages

30/03/2011 – 1.3:

  • Added new Tuning value called Smooth
  • Improved detection of scene-changes

24/03/2011 – 1.2:

  • Renamed Fast preset to Ultra Fast
  • Added Very Fast and Fast presets
  • Increased quality of Placebo and Medium presets
  • Added Tuning variable
  • Improved detection of scene-changes
  • Added the file dependencies to the download since a couple of them were confusing some people
  • Added links to the dependency websites in the help file

22/03/2011 – 1.1:

  • Renamed Quality preset to Medium (default)
  • Renamed Speed preset to Fast
  • Increased quality of Medium (default) preset
  • Added Placebo preset (little quality gain with big performance hit, not recommended)
  • RemoveGrain is now required for Medium (default) preset
  • EEDI2 is required for Placebo preset

21/03/2011 – 1.0.2:

  • Increased speed of both presets

20/03/2011 – 1.0.1:

  • Slightly faster
  • Scene-changes no longer fade/blend

17/03/2011 – 1.0:

  • Initial release

Convert videos to 60fps (Updated 21 May 2015)



Many modern TVs now include an extra frames feature, usually either 120Hz or 240Hz. This just means they take the source video, which is usually between 24-30FPS, and add new, interpolated frames between the original frames that make the motion look much more smooth.

High framerate (HFR at 48fps) was used in The Hobbit and will be used in upcoming films like the Avatar sequels, so why not watch all your movies at higher framerates?

A lot of people don’t realize this, but 99% of TVs made before this feature was introduced are actually capable of displaying 50FPS and 60FPS, and of course most LCD monitors display 60FPS as well.

This tutorial will allow you to convert videos of any framerate to higher framerates; 25FPS becomes 50FPS and 24/30FPS becomes 60FPS by default, or you can specify whichever framerate you want.

This script offers greater quality than any televisions I have seen.

I’m sure many people will want to see how well this script works, so here’s a comparison:
Original File
Converted File

Note: This can now be done in realtime using Universal Media Server!


This post provides instructions on how to easily convert any video to 60FPS, which allows you to take advantage of this feature of modern TVs on your computer monitor or TV without actually buying anything.

Step 1:

The files needed for this step are found in this zip folder (~3MB).

Run and install the file AviSynth.exe.
It is an early version of AviSynth 2.6 that is more stable and faster for multithreading than 2.5 releases.

Download and install MeGUI, run it, let it update all the things it wants to and import all of the presets.

Optional Tip: If you want MeGUI to update to the very latest stuff (at your own risk) you can push ctrl+s, go to the Extra Configuration tab, and in the Auto Update section select “Use development update server”

Close MeGUI and extract the files in the tools folder from our zip file into your MeGUI tools folder, which for most people will be either C:\Program Files (x86)\MeGUI\tools\ or C:\Program Files\MeGUI\tools\.

Step 2:

Download and install MKVToolnix.
When that is installed, run MKVMerge (Start Menu -> All Programs -> MKVToolnix -> mkvmerge GUI).

You will also need codecs installed. If you don’t already have them I recommend K-Lite Mega Codec Pack. If you install K-Lite, make sure to select “Profile 9: Lots of Stuff” during installation.

Step 3:

Start MeGUI again. You should be left with a window that looks similar to this:


Step 4:

Push ctrl+r, or go to Tools -> AVS Script Creator.
Now you should see something like this:


Step 5:

Click the Config button next to Avisynth profile.
It should look like this:

Step 6:

Click the New button down the bottom and type 60FPS in the name box, so it should look like this:

Step 7:

Now for the script that will do the actual 60FPS conversion.
Just copy and paste the following code into the text input area.

PluginPath = "C:\Program Files (x86)\MeGUI\tools\avisynth_plugin\"

Important note #1: Make sure the path on the third line is correct.
For example, if you are running 32-bit Windows, you will need to modify the path to “Program Files” instead.

Important note #2: You should change the number “4” in the script (on line 1) to your number of CPU cores. If you don’t know how many cores your CPU has just Google your CPU and you should be able to find the specs somewhere, or 4 should be fine anyway.

Important note #3: If you have a video card, you can improve quality by adding “GPU=true” to the script. However, it may make encoding time slower, so take that into account.
So InterFrame(Cores=Cores) would turn into InterFrame(Cores=Cores, GPU=true)
If you do this, you may also need to go into your MeGUI tools folder (usually C:\Program Files (x86)\MeGUI\tools\x264) and rename the file opencl.dll to opencl.dll.bak. This will let MeGUI use the version of opencl.dll that your video card drivers have installed, instead of the generic one from MeGUI.

Important note #4: This script always outputs either 50FPS or 59.94FPS (60FPS) for compatibility reasons. If you want to always double the framerate instead, so that for example 23.976FPS turns into 47.952FPS (48FPS), you can use the “FrameDouble” parameter.
So InterFrame(Cores=Cores) would turn into InterFrame(Cores=Cores, FrameDouble=true)

So now your window should look similar to this (with different text):

Step 7

Step 8:

Click the Extra Setup tab and make sure “Prefer DSS2 over DirectShowSource” is checked.

Optional tip #1: You might also want to choose your preferred resizer. For aspect-ratio changes (like from 720×576 to 720×480) a neutral filter like Spline36 will be nice. For actual resizing (like from 1920×1080 to 1280×720) a sharp filter like Spline64 will be best. I usually just leave it on Spline36. Make sure to untick the checkbox on the option after you change the default resizer, otherwise it will always be used by default which is often unnecessary.

Optional tip #2: I recommend changing the “MOD value used for resizing” to mod4. This gives the best balance between compatibility (a lot of devices like PS3 don’t have good mod2 support) and aspect ratio accuracy (the higher the MOD value, the more likely the aspect ratio is to be skewed more heavily).

Now it should look something like this:


Then just click the Update button then the OK button

Step 9:

Now we’re back to the AviSynth script creator window and now that we have our 60FPS AviSynth template made and selected, it’s time to choose which video we want. Just click the button next to Video Input up the top of the window and find your video, then click Open.
A window will pop up with buttons, click the option on the right, usually either “DirectShowSource” or “AviSource”.
A window will pop up to show you the video, you can just close that.
Now you should see something like this:


Step 10:

Click the Save button. The video preview window might pop up again, you can close it again.

Step 11:

Now is the time when you need to choose the quality of the video and audio.

If you don’t know what to do here, something quick and easy is to just use CRF, which means you let the codec decide on the bitrates itself. So you can click the “Config” button next to the “Encoder settings” dropdown when you have a x264 option selected, then just enter a number between 16-20 in the “Quality” input box. 16 means your video will be almost exactly the same quality as the source, while 20 will look good too while taking up less space. Personally I use 16 for everything because why not? 🙂

So when you have your quality, click Queue in the Video encoding section.

Step 12:

Now your video is ready for conversion.
Now just go to the Queue tab and click Start down the bottom, then wait for it to finish.

Step 13:

The final step is to add your audio and/or subtitles from the original file to the converted file. This process uses muxing, not conversion, so there is no quality loss.
For this we will use the program we installed earlier, MKVMerge.
So run that and drag the converted file into that program, then do the same with the original file. If you can’t drag them on, you can use the add button instead.
Now you have several items in the Tracks, chapters and tags section. You just need to untick the ones you don’t want. Usually you will want to leave them all selected except for the original video track, as I’ve done in the following example:

Finally, set the Output filename down the bottom of the window and click Start muxing.
When that is done, you have your final video!

Final Thoughts:

This might seem like a long process, but actually it is only long once. Since we have now made templates, the process for the videos from now on will be much faster; instead of entering the script each time, now you can just make sure your 60FPS AviSynth script is selected.

This file can now be played just like any other video. I personally watch videos on my TV which is linked up to my computer using the awesome, free program called Universal Media Server, and that handles these 60FPS videos perfectly with no configuration.

Any comments are appreciated. If you can think of an improvement to the script, or to the process, or if you just found it useful and want to say thanks, please do leave a comment. I would love to know that it’s being used.

If you want to donate to help me with server costs and time spent keeping this article updated, you can do so here with my thanks 🙂


  • How can I fix random crashing of vfw4x264.exe?
    This probably means you are encoding a file using an input mode other than DSS2, which can happen if the clip is .m2ts or .dga (blu-ray) or another uncommon format.
    You can fix it by changing the 2 in the second line of the script to either 3, 4, 5 or just removing that line (try them in that order, since the options get progressively slower)
  • The option “Prefer DSS2 over DirectShowSource” is disabled. or
    I get an error like “can’t load avss.dll”.
    This means your computer is missing Haali Media Splitter. You can download it here or as part of a K-Lite Mega Codec Pack and the error should go away after you install it. If you install K-Lite, make sure to select “Profile 9: Lots of Stuff” during installation.
  • The file stops encoding after 99%.
    This usually indicates a codec configuration issue. Try installing/reinstalling K-Lite Mega Codec Pack, and make sure to let it select its preferred defaults (not “quick upgrade”)
  • Can I customize the output framerate to make it 48FPS, 75FPS, 120FPS, or anything else?
    Yes, you can choose any framerate you want. It is best to choose a framerate that is divisible in some way with the original video, but even that is your choice. You just need to add the options “NewNum” and “NewDen”, like this:
    InterFrame(Cores=Cores, NewNum=48000, NewDen=1001)
    NewNum stands for “New Numerator” and NewDen stands for “New Denominator”. In general, with NTSC material the NewDen should be 1001 and the NewNum should be 1000x your desired framerate (so for 48FPS you want 48000 and 1001) while for PAL content you might just want something like NewNum=75,NewDen=1 to output 75FPS content.
  • The output seems choppy, can I make it smoother?
    Yes, by default we output a video that sacrifices a little smoothness in order to reduce errors, but different people’s eyes pick up on different things so it can all be a matter of taste. You can try the Smooth tuning, like this:
    InterFrame(Cores=Cores, Tuning="Smooth")
    Also, using GPU mode produces more accurate results and therefore should appear smoother, though it can be slightly slower overall. You can try it like this:
    InterFrame(Cores=Cores, GPU=true)
    Or try both options at once like this:
    InterFrame(Cores=Cores, Tuning="Smooth", GPU=true)
  • Why isn’t the GPU being used much in GPU mode?
    Only some things are done with the GPU in GPU mode, it’s still mostly done by CPU but helped by GPU.
  • Why is the video still the original framerate after running it through MKVMerge?
    You probably selected the wrong tracks in MKVMerge so you’re getting the original video track instead of the new one; make sure you untick the original video stream before muxing.
  • Why does MeGUI give an error “SVSmoothFPS: unable to load library given in ‘compose’ […svpflow2.dll]
    Try re-installing or updating your video card drivers, and if that doesn’t work then maybe your video card doesn’t support OpenCL so remove GPU=true from your script.
  • Why am I getting the error “SVSmoothFps: unable to load library given in ‘compose'” when I try to run the encoding process, but not when I preview?
    Go into your MeGUI tools folder (usually C:\Program Files (x86)\MeGUI\tools\x264) and rename the file opencl.dll to opencl.dll.bak. This will let MeGUI use the version of opencl.dll that your video card drivers have installed, instead of the generic one from MeGUI.
  • Why am I getting the error “Error message for your reference: Can not read the video stream”?
    MeGUI can’t read from folders or files with certain characters, so try moving the video to a different folder and/or renaming the file.


Widezu69 for providing the original AviSynth script that I used as a base.
Fizick for MVTools, the library that does all the work, and SVP for the modifications to MVTools that make it even better for our purposes.
Everyone on various forums for their feedback, this is really a community effort.



  • Updated InterFrame to 2.8.2, which improves speed


  • Corrected and improved the instructions and FAQ


  • Updated InterFrame to 2.8.0, which improves speed and lowers memory usage
  • Updated conversion script


  • Updated the instructions and FAQ


  • Updated InterFrame to 2.6.0
  • Added a tip about using framedoubling mode
  • Updated most images to reflect the minor changes to MeGUI
  • Minor improvements to instructions


  • Added more items to the FAQ


  • Added more items to the FAQ
  • Shortened the changelog to only the latest 3 changes by default


  • Updated instructions
  • Added more tips
  • Added to and updated the FAQ
  • Updated the link to MKVToolnix to always point to the latest version

Click here to display the rest of the changelog

© 2023 Spirton

Theme by Anders NorénUp ↑