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

SubJunk (Post author)
November 30, 2013 at 1:39 pm

@Reed it probably means that the path on line 3 is incorrect, try making sure it points to proper directory

@Robert Lantin Thanks a lot for the feedback 🙂 I don’t think I have ever had a DRM file so I don’t know about them, sorry

@Vegasigitp Glad you got it working! 🙂
Mark
December 14, 2013 at 6:36 pm

Hi,

First of all, thank you so much for sharing this.

I just have a problem when choosing Directshowsource after selecting the video file…Error is “Unable to render the file. You probable don’t have the correct filters installed”.

Would you happen to know the solution to this error?

Thanks,
Mark
SubJunk (Post author)
December 16, 2013 at 11:40 am

@Mark It can probably be fixed by installing K-Lite Mega Codec Pack

@John Doe Does it work with InterFrame 2.5.1?
Umer
December 19, 2013 at 1:02 am

Is it possible to convert 50 fps video to 100fps using this tool ?

thanks
SubJunk (Post author)
December 19, 2013 at 10:46 am

@Umer Yes, using the parameters “NewNum” and “NewDen” you can output any framerate you want 🙂
Nic727
December 22, 2013 at 7:48 am

Hi, you can delete some of my post. I’m really sorry. I downloaded codec from here ; http://www.windows7codecs.com/ and it worked. But I have an error on line 4. Do you want a screenshot?

thx
SubJunk (Post author)
December 22, 2013 at 9:46 am

@Nic727 A screenshot would help 🙂
Alberto
December 28, 2013 at 4:11 am

Hi,

these is the example script for convert video to 60fps:

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)

But if I like convert for 23.976 to 48fps, what changes should I do?

Thanks.
Alberto
December 28, 2013 at 5:06 am

Hi,

with these script it’s possible convert 23.976 to 48fps?
Which line can I modificate?

Thanks.
SubJunk (Post author)
December 28, 2013 at 10:02 am

@Alberto You can use:

InterFrame(Cores=4, NewNum=48000, NewDen=1001)
Alberto
December 30, 2013 at 5:43 am

Thanks SubJunk, I used these script yesterday and perfect.
Another question, I used these script for make a 3D sbs movies:

LoadPlugin(“H264StereoSource.dll”)
videol=DirectShowSource(“left.mkv”, audio=false, fps=24000/1001).convertToYV12()
videol=AssumeFPS(videol, 24000, 1001, false)
videor=H264StereoSource(“decoder.cfg”, 151952).convertToYV12()
videor=AssumeFPS(videor, 24000, 1001, false)
video=StackHorizontal(videol,videor)
Spline64Resize (video, 1920, 1080).Sharpen(0.17)

How integrate these script for make a 3D sbs 48fps movie?

Thanks.
Glen
December 31, 2013 at 2:32 pm

Hello Subjunk, your tutorial is awesome, and I have encoded many a vid before I leave for groceries (and booze) and come home to watch 60fps pron, i mean… movies.

I gotta ask though, at the beginning of th3 60fps tutorial, you mention that this can be done in real time via UMS. I downloaded and tried it out with the 60fps videos that I made previously, and they look great 😀

I am just wondering, does real time mean I can watch a 30fps video that I downloaded and UMS will interpolate the video to 60fps, so i can watch it on my playstation 3?

I am a little confused how to do this. I did search this website, but I can not find instructions on how to do this.

Happy new year,
SubJunk (Post author)
January 1, 2014 at 3:03 pm

@Glen In UMS, on the Transcoding Settings tab you can enable “True Motion” for the AviSynth engines

@Alberto This should work:

LoadPlugin(“H264StereoSource.dll”)
videol=DirectShowSource(“left.mkv”, audio=false, fps=24000/1001).convertToYV12()
videol=AssumeFPS(videol, 24000, 1001, false)
videor=H264StereoSource(“decoder.cfg”, 151952).convertToYV12()
videor=AssumeFPS(videor, 24000, 1001, false)
video=StackHorizontal(videol,videor)
InterFrame(video, Cores=4, NewNum=48000, NewDen=1001, InputType=”SBS”)
Spline64Resize (video, 1920, 1080).Sharpen(0.17)
pyuu
January 9, 2014 at 4:56 pm

Thank you for sharing this tutorial.

On step 11 I can’t find Enqueue button, where is it?
SubJunk (Post author)
January 9, 2014 at 10:15 pm

@pyuu It’s “Queue” now, since MeGUI updated the word they use. I’ve updated it in the tutorial. Thanks! 🙂
JoJo
January 10, 2014 at 1:56 pm

Hi SubJunk,
i have a problem here,

AviSynth script error
LoadPlugin:unable to load”C/Program Files/MeGUI/tools/avisynth_plugin/svpflow1,dll, error=0x7e

i’ve installed Avisynth, put the svpflow.dll to avisynth_plugin folder & avisynth_plugin inside MeGUI

i’m using intel i3 with radeon 4850
4gb ram

my 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()
GPU=true
SetMTMode(2)

InterFrame(Cores=2)

please help me
zed026
January 11, 2014 at 10:00 am

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,GPU=true)

Hi i have used this script to convert from 24fps to 60fps. But I was wondering what changes would i have to make in order to convert it from 24fps to say for example 120fps. Any and all the help is much appreciated.
zed026
January 11, 2014 at 10:02 am

Also can you tell me if there is any way of reducing the time for encoding process…
Thanks in advance.
zed026
January 11, 2014 at 5:06 pm

Hi there thank you very much for this conversion it works like a charm but i was wondering if i could convert from 24fps to 120fps or 60fps to 120fps using this script or by modifying it somehow. The script that i am using at the moment is given below :

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, GPU=true)

Also can anyone please tell me what modification do i have to make for this to work if it is possible.
Thanks in advance.
SubJunk (Post author)
January 11, 2014 at 6:57 pm

@Jojo Check the path “C:\Program Files (x86)\MeGUI\tools\avisynth_plugin\”. It’s possible that you’re on a 32-bit operating system for example, so the path would be different.

@zed026 You can use the NewNum and NewDen parameters, like this: InterFrame(Cores=2, NewNum=120000, NewDen=1001)
zed026
January 11, 2014 at 10:03 pm

Thanks for the reply. Can you suggest me any way of reducing the time required for encoding. Also is there any way to reduce the size of the output file. Sometime it is just too big like 10-15GB. BTW can i use the line like this :
InterFrame(Cores=4, GPU=true, NewNum=120000, NewDen=1001)

Thanks for the help.
SubJunk (Post author)
January 11, 2014 at 10:38 pm

@zed026 You can reduce the encoding time by moving the x264 preset slider to the left; the further left it goes, the faster it will encode, but it also skips optimizations so the filesize will be larger.
To make the filesize smaller, you can increase the “Quality” number. You won’t want to go above 23.
That line looks good 🙂
zed026
January 11, 2014 at 11:17 pm

Thanks works fine. 😀
JoJo
January 14, 2014 at 1:51 pm

thanks for the reply,
yes i’m using windows 7 32bit, so what is the correct path?
or what should i do?

thx SubJunk
SubJunk (Post author)
January 14, 2014 at 2:02 pm

@JoJo The path needs to point to the proper directory, which is where you copied the unzipped files. By default it would be C:\Program Files\MeGUI\tools\avisynth_plugin\ (not C:\Program Files (x86)\MeGUI\tools\avisynth_plugin\)
Christopher
January 15, 2014 at 2:01 am

Hi there, I don’t know if anybody else has this problem, but I have some files which do not want to finish converting. They kind of stop at like 99.97%. And once a file has done that, it will keep doing it if I try again.\
Hope somebody can help!
SubJunk (Post author)
January 17, 2014 at 10:23 am

@Christopher Usually this can be fixed by using a different or updated codec pack. I recommend K-Lite Mega
Rashad
January 18, 2014 at 11:27 am

Actually, there is another solution to Christopher’s problem. Here’s how you do it. When the file stops there, play the file in question and pause it. Then make a copy of the file. Now cancel the encoding. You should have 2 versions of the same file: The original and the copy. Erase the copy. The original file now has everything encoded like it should. Hope that helps.
andreas
January 20, 2014 at 11:13 am

must give a program to do all the work of converting 60fps
Sheppard
January 22, 2014 at 10:17 am

Hello, thanks for this guide, works like a charm! I have two questions though.
I have GPU parameter set to “true”, but during convertion process the load of GPU is only 0-30% and CPU 100%. Using ATi Radeon 5770. How to engage more of the GPU power? And second question is about comparison with SVP, real time convertion. Which method gives me a better conversion quality, this or SVP ? Thanks!
Anthony
January 22, 2014 at 4:13 pm

Hello,
I’ve tried uninstalling all my codecs (including K-lite), restarting, reinstalling K-lite, then restarting again. But the DSS2 > DirectShowSource is still grayed out. What gives?

Thanks in advance!
SubJunk (Post author)
January 22, 2014 at 5:34 pm

@andreas InterFrameGUI

@Sheppard 1) that’s normal, 2) in my opinion this is the better quality

@Anthony I think in the latest K-Lite packs they don’t include DSS2 by default so you have to select Haali in the preferences when you install it? I should update the guide for that
Anthony
January 23, 2014 at 4:13 am

Thank you, I chose Haali for everything and that fixed it.
thavo
January 23, 2014 at 11:52 am

Hi, this looks like an awesome guide, but I am stuck with this problem that MeGUI just freeze after I choose an .mkv-video, have tried several files with the same result. Any idea what can cause it? Seems like all codecs are installed correct, so I are really wondering what is going on. I use windows 7, 8-core AMD CPU and AMD 6870 GPU.
Lawrence
January 24, 2014 at 12:24 pm

Wow! This is amazing, my movies and anime’s look so much better at 60 FPS.
Do you have any guides on upscaling or do you know a line of code that I can add to the script for it?
meGUI doesnt seem to let me up the resolution.
Øyvind
January 25, 2014 at 4:12 am

Hi, thanks for a great guide, but I have this problem that MeGUI just freeze after choosing DirectShowSource after choosing video in step 9… any clue? Did not help to install K-Lite codec pack…
SubJunk (Post author)
January 27, 2014 at 7:26 pm

@Lawrence Glad you like it 🙂 For upscaling you can use a nice resizer like Spline36Resize or if you don’t mind waiting you can use nnedi3. Then you run it through filters to make it sharper, QTGMC does well for upscaling if you look at the docs. Then most people add noise as the final step since it tricks the eyes into thinking the image is sharper than it is. AviSynth is a powerful upscaling tool if you put in the time to learn it!
kgian
January 28, 2014 at 2:22 am

Hello, I’ve got an HP Microserver with an AMD N54L dual core processor. I did change

SetMTMode(3,4)

InterFrame(Cores=4)

to

SetMTMode(3,2)

InterFrame(Cores=2)

as per the instructions. The cpu usage is only about 30% and I get 1.2 FPS converting 1080p MKVs.
If I leave the original values CPU usage is almost 100% and I get 3FPS.

In my other pc with i5 and radeon 7770 with GPU assist I get 100% cpu usage and about 16FPS.

My questions:
1)Are there any better settings that I could use for the microserver with the dual core system? Why are the 4 core settings better when it is a dual core system?
2)If I fit a radeon 7750 in the microserver, which is the fastest GPU it can accept, will there be a significant boost in rendering performance?
zed026
January 28, 2014 at 2:30 am

@Subjunk
Bro if I reduce the encoding time by moving the x264 preset slider to the left extreme end will it decrease the quality meaning will it differ form the same move done in placebo mode. I mean what is difference in doing this process fast and doing it in placebo mode.
Thanks in advance.
SubJunk (Post author)
January 28, 2014 at 11:18 am

@kgian A lot of dual-core CPUs are like faux-quad-cores, just like some quad-cores like running as octa-cores. There’s different reasons for each chip from each company. Like for Intel chips I think they call it hyperthreading, not sure about AMD ones.
There may not be a significant increase in speed in GPU mode, mostly because the quality of the picture is improved in that mode because GPUs are capable of processing finer detail natively than CPUs. You might see an increase in performance though, I haven’t compared the speed of the two modes recently and it would be different for different hardware.
If you want I can compare the performance on my machine, let me know.

@zed026 The preset slider doesn’t affect quality, only speed and and bitrate (filesize). The CRF value is the thing that affects quality 🙂
Kgian
January 28, 2014 at 12:00 pm

I did some more tests. On the i5 PC, if I set the slider to fastest and quality to 21, I get about 80fps for 720p content. If I don’t use the GPU I get about 120fps in the same file! I understand that the quality will be reduced though…

On the amd system I get about 35fps with the same file. That means that transcoding on the fly is a no go.

I tried transcoding with UMS with the i5. Most 720p files are working with quality set to 21.

If anyone knows, SVP has the same hardware requirements? That is, the i5 PC will struggle for 720p files and the amd PC is a no go even with a modern video card?
SubJunk (Post author)
January 28, 2014 at 12:18 pm

@Kgian SVP will do it faster than the transcoding solutions because it skips the encoding step – we are doing interpolation and encoding at the same time
z-machine95
January 30, 2014 at 7:35 am

hello, amazing guide dude, but i have a problem, when i press to save the avs script it gave this error:

Avisynth script error:
Script error: there is no function named “SetMTMode” (C:\Users\*****\Desktop\test.avs, line 2)

i use this script:
Setmemorymax(4096)
SetMTMode(3,8)
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=8, GPU=True, NewNum=48000, NewDen=1001)
z-machine95
January 30, 2014 at 8:10 am

ok i have solved the other problem… but i came with another and more serious problem… i try to convert a scene of a film and in the output video moving object are distorted… i have already try to convert a film in 48 using twixtor for after effect and there was the same problem, distorsion all over the place…. the is a way to eliminate the distorsion or at least reduce it?
here is a sample, but there are parts where it’s even worse: http://imgur.com/lcrpNXD
z-machine95
January 30, 2014 at 9:59 am

Hello SubJunk…. his is an amazing guide!!!! i try to convert the hobbit trailer, but i experience a lot of image distorsion during the video, mainly in scene when there are moving objects. there is a fix or a special command for it?
SubJunk (Post author)
January 30, 2014 at 12:18 pm

@z-machine95 You can try using the smooth tuning, like this:
InterFrame(Tuning=”Smooth”, etc)

Some distortion will always be there but this may improve it
z-machine95
February 1, 2014 at 9:16 am

QUOTE:[@Dario: The main difference between SVP and InterFrame scripts are that SVP switches to a less-smooth mode when there will be more artifacts. I’ve decided to keep the smoothness instead. If you want to change it yourself you can edit InterFrame2.avsi and remove the 2 occurrences of “mode:0″ near the bottom of the page.]

this is interesting i try to delete the two “mode:0″ in the avsi file…then i add tuning=”smooth” and overridearea=0 and now it has less distorsion.. this is the best configuration so far…
Vinicius
February 2, 2014 at 3:53 am

When I play the video after interframe, my processor goes to 100% and the player (media player classic) becomes too slow. What’s going on? Do I need to modify some configurations at player menu?
SubJunk (Post author)
February 2, 2014 at 10:58 am

@Vinicius it might mean that the x264 options were too high, like if you put the slider on “Placebo” or something. Make sure the slider is on “Slow”
Z-machine95
February 2, 2014 at 7:42 pm

@subjunk there are other option to make the video less distorted? Apart from overridearea=0, tuning=”smooth”, and delete mode:0 in .avsi?