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:
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.
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\.
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.
Start MeGUI again. You should be left with a window that looks similar to this:
Push ctrl+r, or go to Tools -> AVS Script Creator.
Now you should see something like this:
Click the Config button next to Avisynth profile.
It should look like this:
Click the New button down the bottom and type 60FPS in the name box, so it should look like this:
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):
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
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:
Click the Save button. The video preview window might pop up again, you can close it again.
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.
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.
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!
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:
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:
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
- Updated MeGUI instructions and screenshots
- Updated the link to MKVToolnix to 6.8.0
- Added more notes about some options
- Updated MeGUI instructions
- Updated InterFrame to 2.5.1 which is better quality, more stable and supports more video cards.
- Updated the link to MKVToolnix to 6.6.0
- Updated instructions
- Updated Introduction section
- Updated InterFrame to 2.3.0 which is faster, better quality, supports more video cards and has lower memory usage.
- Updated the link to MKVToolnix to 5.9.0
- Simplified instructions
- Updated InterFrame to 2.1.0 which is much faster, better quality, etc.
- Updated SEt’s AviSynth MT to 2.6 (2012.05.16)
- Include the new AviSynth DLL in the installer to make things easier to set up
- Updated the link to MKVToolnix to 5.6.0
- Simplified instructions
- Updated InterFrame to 1.14
- Updated SEt’s Avisynth MT to 2.6 (2012.03.31) which is faster and more stable
- Updated the link to MKVToolnix to 5.4.0
- Improved instructions slightly
- Script stability improvements
- Updated the link to MKVToolnix to 5.3.0 from 5.0.1
- Updated InterFrame and its dependencies to 1.13 from 1.12.2 (Changelog) which improves speed and ATI GPU compatibility
- Updated InterFrame and its dependencies to 1.12.2 from 1.12 (Changelog) which improves speed by up to 15%
- Updated AviSynth DLL (SEt’s MT Build) to 2011.09.13 from 2009.09.19 which increases stability and fixes bugs
- Updated the link to MKVToolnix to 5.0.1 from 4.6.0
- Updated InterFrame to 1.12 from 1.11 (Changelog)
- Rolled back to previous AviSynth version because the newer one was causing crashes
- Link to latest MeGUI installation package directly since they don’t seem to be releasing installers anymore
- Updated SEt’s AviSynth DLL to 2011.07.19 from 2009.09.19
- Updated AviSynth to 2.6 Alpha 3 from 2.6 Alpha 2
- Updated InterFrame to 1.11 from 1.10 (Changelog)
- Updated Step 9 because of an extra window added by MeGUI (thanks to Sko for the reminder)
- Updated sample videos
- Updated InterFrame to 1.10 from 1.8.1 (Changelog)
- Updated sample videos
- Updated InterFrame to 1.8.1 from 1.7.1 (Changelog)
- Wrote version information to avisynth.dll to fix software conflicts
- Updated InterFrame to 1.7.1 from 1.7 (Changelog)
- Updated the thanks section to include SVP
- Fixed a mistake in the guide (Thanks Sebastian)
- Updated InterFrame to 1.7 from 1.6 (Changelog)
- Added a new note below the scripts explaining how to increase the encoding speed
- Updated InterFrame to 1.6 from 1.5.1 (Changelog)
- Changed the guide so that it muxes audio and/or subtitles, whereas before it always converted audio and ignored subtitles
- Changed a lot of text and some images in the guide to be easier to follow
- Added donation link
- Updated InterFrame to 1.5.1 from 1.5 (Changelog)
- Updated the scripts to disable GPU-acceleration by default since it causes errors for people with older or no video cards.
- Updated InterFrame to 1.5 from 1.3.1 (Changelog)
- Updated the scripts and made them more simple
- Added new video samples
- Slightly changed the scripts to fix a colorspace bug
- Updated InterFrame to 1.3.1 from 1.2 (Changelog)
- Updated the video samples
- Updated InterFrame to 1.2 from 1.1 (Changelog)
- Updated Speed script to work with InterFrame update
- Updated InterFrame to 1.1 from 1.0.2 (Changelog)
- Updated scripts to work with InterFrame update
- Updated InterFrame to 1.0.2 from 1.0 (Changelog)
- Updated MVTools2 to 126.96.36.199b from 188.8.131.52b (Changelog)
- Updated FAQ with links and more correct and specific answers
- I’m releasing the script as an AviSynth plugin called InterFrame so I’ve added that to this guide
- Removed unnecessary file (mt.dll) and updated guide and scripts accordingly
- Increased quality of the scripts by improving the detection of scene-changes
- Increased quality of Quality script
- Increased quality of scripts
- Improved accuracy of the Quality script with little performance impact
- Updated file package to include fftw, a requirement of the improved accuracy setting
- Updated file package to include Builds.txt which contains the versions and links to the files in the package
- Added a menu at the top of the post to make it easier to see which sections there are and jump to them
- Updated introduction section
- Updated MVTools from 2.5.11b to 184.108.40.206b
- Re-introduced divisible framerates, which increases interpolation accuracy and speed
- Minimised artifacts in Quality script with no performance hit (maybe a bit faster, too)
- Moved resize to above the interpolation after testing that showed it is more accurate at 720p than 1080p
- Updated AviSynth from 2.5.8 to 2.6 after tests which found it is more stable for multithreading.
- Improved instructions, fixed typos, restructured steps.
- Updated MVTools from 220.127.116.11b to 2.5.11b.
- Increased the interpolation strength of the scripts. It can cause errors, (stripes and cross-like patterns may cause glitches), but it is better than before for general use.
- Added a common question to the FAQ; “Prefer DSS2 over DirectShowSource” is disabled.
- Increased accuracy of the Quality script
- Corrected minor language errors
- The value of blksize will now automatically change based on input resolution, which hopefully provides the most accurate settings for all inputs
- Added the ConvertToYV12 function, just meaning MeGUI doesn’t need to keep adding it all the time
- Input uses SetMTMode 2 now instead of 1, since 1 can cause quality problems for .avi files.
- Reverted to always using 60FPS. Using divisible framerates did provide increased accuracy with technically the same level of smooth motion, but monitors and televisions can’t display those exact framerates anyway which results in less visible smoothness. Thanks to Widezu for pointing this out.
- Added to the FAQ
- Minor wording changes
- Increased accuracy of both scripts by allowing for different framerates depending on the input. See here for more details.
The videos still play perfectly on 60Hz and 75Hz monitors/TVs, so don’t worry about that.
- Increased speed by roughly 100% for both scripts
- Updated DLL package:
- Removed DirectShowSource.dll
- Removed TCPDeliver.dll
- Updated mvtools2.dll from 2.5.10b to 18.104.22.168b
- Updated mt.dll
- Updated avisynth.dll
- Fixed a bug that would very infrequently cause a backwards frame
- Note: Users of previous scripts will need to make sure they have selected “Prefer DSS2 over DirectShowSource” in the AviSynth configuration settings (under the Extra Setup tab)
- Updated instructions and wording throughout the whole article, to keep it current with these latest changes and make it easier to follow.
- Added instructions on how to make MeGUI update to the latest releases
- Added basic instructions on video encoding quality
- Added new sample videos (original, speed and quality)
- Increased accuracy in the Quality script
- Added a new script with improved quality
- Improved speed slightly
- Fixed a crash
- Updated script for increased accuracy
- Fixed a bug with resizing
- Merged both scripts since the high quality one produced choppier motion
- Fixed a bug that stopped functions like crop and resize from working
- Fixed a bug that caused random crashes on very high-quality videos
- Updated high quality script since last version had problems
- There are now 2 scripts; one for quality and one for speed. Both are good.
- Updated Step 2 for better compatibility
- Removed code formatting since it was confusing to copy/paste
- Removed need to change script depending on your CPU and improved quality
- Fixed an error with the DLL files