Convert videos to 60fps (Updated 21 May 2015)

May 19, 2010 / SubJunk / 1,250 Comments

Sections:

Introduction
Purpose
Instructions
Final Thoughts
FAQ
Thanks
Changelog

Introduction:

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!

Purpose:

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.

Cores=4 SetMemoryMax(512) SetMTMode(3,Cores) PluginPath = "C:\Program Files (x86)\MeGUI\tools\avisynth_plugin\" LoadPlugin(PluginPath+"svpflow1.dll") LoadPlugin(PluginPath+"svpflow2.dll") Import(PluginPath+"InterFrame2.avsi") <input>.ConvertToYV12() SetMTMode(2) <deinterlace> <crop> <denoise> <resize> InterFrame(Cores=Cores)

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 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 🙂

FAQ:

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.

Thanks:

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.

Changelog:

21/05/2015:

Updated InterFrame to 2.8.2, which improves speed

16/03/2015:

Corrected and improved the instructions and FAQ

05/03/2015:

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

24/02/2015:

Updated the instructions and FAQ

27/09/2014:

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

22/07/2014:

Added more items to the FAQ

10/07/2014:

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

20/05/2014:

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

05/03/2014:

Updated MeGUI instructions and screenshots
Updated the link to MKVToolnix to 6.8.0
Added more notes about some options

09/01/2014:

Updated MeGUI instructions

16/12/2013:

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

10/01/2013:

Updated Introduction section

24/12/2012:

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

27/06/2012:

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

03/04/2012:

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

25/02/2012:

Script stability improvements
Updated the link to MKVToolnix to 5.3.0 from 5.0.1

29/02/2012:

Updated InterFrame and its dependencies to 1.13 from 1.12.2 (Changelog) which improves speed and ATI GPU compatibility

03/11/2011:

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

12/09/2011:

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

22/07/2011:

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

05/07/2011:

Updated InterFrame to 1.11 from 1.10 (Changelog)

04/07/2011:

Updated Step 9 because of an extra window added by MeGUI (thanks to Sko for the reminder)
Updated sample videos

18/06/2011:

Updated InterFrame to 1.10 from 1.8.1 (Changelog)
Updated sample videos

20/05/2011:

Updated InterFrame to 1.8.1 from 1.7.1 (Changelog)

03/05/2011:

Wrote version information to avisynth.dll to fix software conflicts

30/04/2011:

Updated InterFrame to 1.7.1 from 1.7 (Changelog)
Updated the thanks section to include SVP

29/04/2011:

Fixed a mistake in the guide (Thanks Sebastian)

28/04/2011:

Updated InterFrame to 1.7 from 1.6 (Changelog)

22/04/2011:

Added a new note below the scripts explaining how to increase the encoding speed

20/04/2011:

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

13/04/2011:

Updated InterFrame to 1.5.1 from 1.5 (Changelog)

12/04/2011:

Updated the scripts to disable GPU-acceleration by default since it causes errors for people with older or no video cards.

11/04/2011:

Updated InterFrame to 1.5 from 1.3.1 (Changelog)
Updated the scripts and made them more simple
Added new video samples

09/04/2011:

Slightly changed the scripts to fix a colorspace bug

01/04/2011:

Updated InterFrame to 1.3.1 from 1.2 (Changelog)
Updated the video samples

24/03/2011:

Updated InterFrame to 1.2 from 1.1 (Changelog)
Updated Speed script to work with InterFrame update

22/03/2011:

Updated InterFrame to 1.1 from 1.0.2 (Changelog)
Updated scripts to work with InterFrame update

21/03/2011:

Updated InterFrame to 1.0.2 from 1.0 (Changelog)
Updated MVTools2 to 2.5.11.2b from 2.5.11.1b (Changelog)

19/03/2011:

Updated FAQ with links and more correct and specific answers

18/03/2011:

I’m releasing the script as an AviSynth plugin called InterFrame so I’ve added that to this guide

17/03/2011:

Removed unnecessary file (mt.dll) and updated guide and scripts accordingly

16/03/2011:

Increased quality of the scripts by improving the detection of scene-changes

25/02/2011:

Increased quality of Quality script

23/02/2011:

Increased quality of scripts

22/02/2011:

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

10/02/2011:

Updated introduction section

03/01/2011:

Updated MVTools from 2.5.11b to 2.5.11.1b
Re-introduced divisible framerates, which increases interpolation accuracy and speed

17/11/2010:

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

08/11/2010:

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.

27/10/2010:

Updated the Quality script sample.

26/10/2010:

Updated MVTools from 2.5.10.1b to 2.5.11b.

13/10/2010:

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.

08/10/2010:

Added a common question to the FAQ; “Prefer DSS2 over DirectShowSource” is disabled.

20/07/2010:

Increased accuracy of the Quality script
Corrected minor language errors

17/07/2010:

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

16/07/2010:

Significantly reduced tearing in high-motion scenes using the Quality script. Here are comparisons of interpolated frames:
Comparison 1, old script, comparison 1, new script
Comparison 2, old script, comparison 2, new script
It’s almost unbelievable they are the same frames, but they are.
Speed of the Quality script has also increased

15/07/2010:

Input uses SetMTMode 2 now instead of 1, since 1 can cause quality problems for .avi files.

13/07/2010:

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.

12/07/2010:

Added to the FAQ
Minor wording changes

10/07/2010:

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.

06/07/2010:

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 2.5.10.1b
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

02/07/2010:

Added new sample videos (original, speed and quality)

01/07/2010:

Increased accuracy in the Quality script

25/06/2010:

Added a new script with improved quality

16/06/2010:

Improved speed slightly
Fixed a crash

15/06/2010:

Updated script for increased accuracy

05/06/2010:

Fixed a bug with resizing

04/06/2010:

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

26/05/2010:

Updated high quality script since last version had problems

24/05/2010:

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

23/05/2010:

Removed need to change script depending on your CPU and improved quality

21/05/2010:

Small change to script

20/05/2010:

Fixed an error with the DLL files

Categories: AviSynth, Encoding, Guide, InterFrame

Tags: 48FPS, 50FPS, 60FPS, convert, encode, framedoubling, HFR, high framerate, megui, smooth

50 Comments

TrueAndyyy
March 15, 2015 at 5:44 am

I still can’t open AVI files … Jesus this is harder as i thought i reinstalled all stuff but no success.
nimda
March 15, 2015 at 10:58 pm

@SubJunk
http://www.uppic.org/image-31F9_55055891.jpg

I thought this is a problem why someone copied your script and get message “Please make sure it’s a valid AviSynth script and that AviSynth is properly installed…… Error message for your reference : Can’t read the video stream”

Please correct it.
SubJunk (Post author)
March 16, 2015 at 6:31 pm

@Salaam when you delete the InterFrame line you’ll also need to delete the SetMTMode(2) line, that should solve that issue. Not sure why resizing to mod16 wouldn’t solve that error, it sounds like a MeGUI problem, or the resizing was unsuccessful. What’s the script you used, and which version of MeGUI are you using? I’m on the development version 2525.

@Darus thanks for the tip, I’ve added it to the FAQ now 🙂

@Rady1993 check that the quotation marks are straight up and down, not slanted ones. If they are slanted then just use the normal ones on your keyboard.

@nimda thanks a lot, I have corrected that now – WordPress was automatically converting the quotation marks.

@TrueAndyyy what’s the error? I don’t have any issues with any files including avi
UltimateSWX
March 16, 2015 at 8:43 pm

Is there any way to get rid of or reduce the ghosting?
eric
March 17, 2015 at 4:31 am

is it possible to using 4k video input ? because when im using 4k video input, it get stuck after i hit the save button 🙁 *its going well when im using 1080p video input
Salaam
March 18, 2015 at 10:04 am

@SubJunk I’ve deleted both “InterFrame”, “SetMTMode(2)” lines which fixed MeGUI error but most importantly it also fixed mkvmerge errors! (you can review my previous posts if you need so)
I’m using 2507 version of MeGUI and couldn’t update it to the development one after changing server source through its options.
So, did you figure out what’s wrong? (fingers crossed 🙂 )
Salaam
March 18, 2015 at 10:57 pm

@SubJunk Oh wait! After trying some more conversions to be sure, sadly the error showed up again in mkvmerge! (as it occurs occasionally for some reason)

“Error in the Matroska file structure at position 1823043838. Resyncing to the next level 1 element.
The last timecode processed before the error was encountered was 01:04:35.455000000.
Resyncing successful at position 1824197496.
The first cluster timecode after the resync is 01:04:42.962000000.”
Maybe x264 Encoder is behind this?
As for resizing to mod16 in order to use XviD Encoder, that didn’t fix MeGUI error either!

Here’s my script before deleting the 2 lines:
Cores=4
SetMemoryMax(512)
SetMTMode(3,Cores)
PluginPath = “C:\Program Files (x86)\MeGUI\tools\avisynth_plugin\”
LoadPlugin(PluginPath+”svpflow1.dll”)
LoadPlugin(PluginPath+”svpflow2.dll”)
Import(PluginPath+”InterFrame2.avsi”)
.ConvertToYV12()
SetMTMode(2)

InterFrame(Cores=Cores, GPU=true)
Salaam
March 18, 2015 at 11:06 pm

@SubJunk Here’s the complete script as it got edited by your site:
http://pastebin.com/U5c1ZCbJ
Salaam
March 19, 2015 at 11:12 pm

@SubJunk Correction: Getting last mkvmerge error while deleting the 2 lines was due to the file itself as it worked with others without any error!
So we’re back to the “InterFrame”, “SetMTMode(2)” theory.
Sorry for the confusion!
Many thanks 🙂
Leonardo Mota
March 21, 2015 at 6:13 pm

Please, when i choose the video to convert, the program show me this message: “unable to render the file. You probably dont have the correct filters installed”. What i have to do? please help.
TrueAndyyy
March 22, 2015 at 6:55 am

@SubJunk
Well i posted already the Error, i post it again but that doesnt help because there are no infos in the error.
http://puu.sh/gtcfi/7cb1656da8.png
http://puu.sh/gkDmL/1a4bc7c36c.png
http://puu.sh/gkDkF/e9921ff025.png
SubJunk (Post author)
March 22, 2015 at 9:14 pm

@UltimateSWX check the FAQ for tips on how to tweak the quality 🙂

@eric AviSynth unfortunately isn’t great at dealing with memory, so it has trouble with 4k videos. You can try increasing the memory by changing the first line to SetMemoryMax(768) or SetMemoryMax(1024) to see if that helps.

@Salaam maybe MKVMerge has developed a problem processing 60FPS videos? I’m not sure, but that is the only difference between a video with the InterFrame line and without it. Everything else (the codec, bitrate, etc.) is controlled by the codecs via MeGUI and has nothing to do with InterFrame 🙁

@Leonardo Mota check the FAQ 🙂
SubJunk (Post author)
March 22, 2015 at 9:18 pm

@TrueAndyyy in the Start Menu, go to K-Lite, then Tools, then GraphStudioNext. Then open your video with that file. That should show you which filters are being used to decode your video and help us see problems. Screenshot it and post it here if you want me to try to help more.
TrueAndyyy
March 23, 2015 at 8:05 am

@SubJunk
Thank you for taking time, for my problems.
You mean like this?
http://puu.sh/gLc5l/958cfdd264.png
SubJunk (Post author)
March 23, 2015 at 2:30 pm

@TrueAndyyy yeah that’s right, and it looks okay. What happens when you click the play icon in that program?
Curious Tom
March 23, 2015 at 3:38 pm

Is it possible to upscale video using MeGUI?

For example 720p to 1080p or 1080p to 4K?

If this can’t do it what software programs should I look into?
TrueAndyyy
March 24, 2015 at 12:02 am

@SubJunk
It start’s the video normaly and it works perfect.
TrueAndyyy
March 27, 2015 at 9:48 pm

@SubJunk
No Idea how to help now? 😀
Salaam
March 28, 2015 at 3:28 pm

@SubJunk
I don’t think it’s related to MKVMerge as I already tried the old versions. I updated MeGUI to 2525 and the same error occurs after muxing video with audio!
I’ll try without your script this time and see if it may help in troubleshooting.
Thanks for the tips buddy!
Stanko
March 29, 2015 at 6:44 am

I am converting 1280×720 25 or 30 fps to 1280×720 60 fps… i always get ghosting around soccer ball
i already put smooth settings
InterFrame(Cores=Cores, Tuning=”Smooth”, GPU=true)
what to do to remove or reduce it?
Please, answer…
thanks
Salaam
March 29, 2015 at 1:38 pm

@SubJunk
Nothing has changed either! Your script seems, it might has something to do with the x264 Encoder.
Any other thoughts to fix it or should I give up by now?
Thanks for bearing me!
dabojable
March 30, 2015 at 2:17 pm

Thank you for this guide. My Interpolation works, but I get artefacts, for example in shows like game of thrones, where there are sword fights, or fire, there are glitches. Anyway to resolve this?
GubJub
April 3, 2015 at 11:27 am

I keep getting the error

“Problem with video output filename: Access to the path ‘C:\Users\Me\Videos\The Flash.mkv’ is denied.

How do I fix this?
Soldatstar
April 5, 2015 at 11:32 am

I need help , my video is rendered in 60 fps but it lt is flickering and not looking smooth :https://youtu.be/tdv4STvM3-k?t=2m5s watch from 2:05
Jermy
April 12, 2015 at 5:36 am

Hi, how to make sure K-Lite Mega Codec Pack to select its preferred defaults (not “quick upgrade”)???
Jep
April 12, 2015 at 4:22 pm

Sir, thanks for this! I’ve so many converted videos already.
But I’m so irritated on ghosting whenever the movement of the vid is so fast (like, whenever I’m converting dance videos)

How do I reduce it? Or even take it off?

Thanks Sir!
Maks Di
April 17, 2015 at 5:15 am

I installed K-Lite Mega Codec Pack with “Profile 9: Lots of Stuff” , with the “Haali Media Splitter” but the option “Prefer DSS2 over DirectShowSource” is still disabled.I try reinstalled K-Lite but its not help.Dont now what to do.
This option is very needed in conversion, or i can work without it?
xllcck
April 17, 2015 at 10:13 am

”….avs cannot be opened.Please make sure it’s a valid AviSynth script and that AviSynth is properly installed.
Error massage for your reference: Can’t read the video stream”

Can you upload a video ?? Please help!!
David Petr
April 19, 2015 at 11:01 pm

Wow, amazing article, hundreds of comments, nice!
I’m at Step 11, clicking Queue and I get an error:

“Unsupported configuration
Audio input, audio output, and audio settings must all be configured”

But when I add audio in the “Audio” section (I add Audio input and Audio output”), add it to Queue and render it, everything I get is audio file in a different format.

What I want is just make “fake” 60 FPS video from a 30 FPS video. I don’t mind if I just get video without audio and then add audio afterwards, but MeGUI doesn’t allow me to do that.
Carlos
April 28, 2015 at 1:38 am

:)))))) MUITO OBRIGADO!!!!
Niteesh
April 28, 2015 at 7:02 pm

@Subjunk
Thanx for this wonderful guide. I have on question. My original video is of 20 GB, I am converting it from 24 to 36 fps. But the estimated size is showing as only 10 GB. Did i screw up the script somewhere?
In the quality section, I entered number 16 and in the preset I dragged it to “Slower” as I really need the quality on this one.
Please help.
Ben
May 4, 2015 at 5:11 pm

I am still getting the error “Please make sure it’s a valid AviSynth script and that AviSynth is properly installed…… Error message for your reference : Can’t read the video stream”

I followed the faq and renamed the file and moved it several different places.
Still getting the error.
Christian
May 12, 2015 at 12:42 pm

If I have an audio file of the video can I export to mp4 with MeGUI and combine the video file and the audio file in an editing software? ( Sony Vegas Pro 13 )
FeLLy
May 16, 2015 at 7:02 pm

WHY?
http://caps.vipmerkezi.net/images/2015/05/15/hata.png
Gray
May 19, 2015 at 1:35 pm

I use this script:

SetMemoryMax(512)
SetMTMode (3,4)
PluginPath = “C:/Program Files (x86)/MeGUI/tools/avisynth_plugin
LoadPlugin (PluginPath+”svpflow1.dll”)
LoadPlugin (PluginPath+”svpflow2.dll”)
Import (PluginPath+”InterFrame2.avsi”)
.ConvertToYV12()
SetMTMode (2)
Interframe (Cores=4)

I type that in, hit update then okay then after selecting a video hit preview AVS script and it gives me this error

AviSynth script error:
Script error: syntax error
((null), line 7, column 14)

I followed all of your instructions and have K-lite codecs installed and everything.
SubJunk (Post author)
May 21, 2015 at 6:13 pm

@dabojable you can try different InterFrame settings
SubJunk (Post author)
May 21, 2015 at 6:15 pm

@Soldatstar I guess the input video has the same jumps but it’s less noticeable at a lower framerate. Try going through the original frame by frame
SubJunk (Post author)
May 21, 2015 at 6:17 pm

@Niteesh it’s probably okay. 10GB for a 1080p video is a very nice size. 20GB is like a storage bitrate, where it has a lot of extra bitrate that won’t be noticeable in the quality.
SubJunk (Post author)
May 21, 2015 at 6:19 pm

@Christian I don’t know about Sony Vegas Pro specifically but yes you can, and the guide uses MKVToolnix to do that
SubJunk (Post author)
May 21, 2015 at 6:19 pm

@FeLLy you probably didn’t install the version of AviSynth that comes with the guide
SubJunk (Post author)
May 21, 2015 at 6:20 pm

@Gray there’s a missing quotation mark on line 3
Subzotic
May 21, 2015 at 7:20 pm

First, I wanted to say thank you for this detailed guide and your assistance with troubleshooting over the years!
Now I’ve seen others ask this same question, but I keep receiving this…

AviSynth script error:
LoadPlugin: Unable to load “C: PROGRAM Files (x86)\MeGUI\Tools\avisynth_plugin\svpflow1.dll”
(C:\Users\Subzotic\Desktop\ ____ \ ____ \ _____.avs, line 4)

I’ve made sure every file is in it’s correct position according to your guide, but this error is persistent.
Any idea?
Subzotic
May 21, 2015 at 7:52 pm

Hmm nevermind,
I re-copied and pasted the code and I guess that worked.
But it seems like the error is random at times, even when I re-pasted the code.
Oh well, as long as it works!
Thanks anyways
Bui Duc Tam
May 24, 2015 at 4:01 pm

Gray: drop “.” in line “.ConvertToYV12()”
BushiGreg
May 28, 2015 at 6:35 am

It works for me thank you! 😀
SandPox
June 5, 2015 at 2:13 pm

How about Linux? do you know anyway to do that? those dlls is for Windows only
MakeSomeNoise
June 6, 2015 at 11:14 pm

Can u help me , I’m tired converting because it always stops at 99.98% and I don’t know how many times I reinstalled K-Lite Mega Code Pack. Some of my conversions were good but almost all of them stopped at 99.98% and I need to convert them 7hrs-10hrs and it just fails. Thanks for this tutorial but it’s not always 100% working .
Zack117
June 7, 2015 at 11:13 am

Thank you so much for this guide! It worked perfectly even though I’ve had to skip the installation of some programms at the beginning as I already got the “full SVP package” installed.

What a great guide…
Hiro
June 7, 2015 at 12:51 pm

Always stops at 99.98%, how to fix that?
Cam
June 22, 2015 at 7:53 pm

So, much to my surprise, I managed to do it in one try ALMOST perfectly…however, I’m getting a weird distortion or smudging effect on certain parts of the video, sometimes it is very noticeable, sometimes it’s nonexistent. Here’s a picture of it at it’s worst:

http://imgur.com/HJhNgRN

Any fixes to this? Or is this just a side effect I’ll have to live with?