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

Soma
October 2, 2012 at 10:31 am

I copied it, checked again to be sure and it’s there.
SubJunk (Post author)
October 2, 2012 at 11:31 am

@Soma: It could be a corrupted version of the file, though not likely you could re-download it. I can’t think of anything else it could be right now, sorry.
Soma
October 2, 2012 at 9:26 pm

Re-downloaded and re-copied still nothing. Oh well I’ll just keep trying and if I could get it to work I’ll post here.
Commander Shepard
October 5, 2012 at 7:22 am

Thanks for the great tutorial.
I added the gpu line but my gtx 580 doesn’t do anything(0% usage).It’s just tooooooo slow otherwise.
My i7 920 at 4Ghz needs more than two days to convert a 720p video with a size of 1.07Gb
Bill
October 5, 2012 at 6:15 pm

I am having that same problem as Mythotin…my original video file get’s processed typically to just over 90%, and then the processing stops/freezes. The log file says “Process exits with error: 0xFFFFFFFF (-1).

What makes this weirder is that MeGUI ran the 60FPS script fine the first couple times I used it a few days ago. Now in the last couple days, I keep getting the above error…as far as I know, nothing in my system or settings changed (or the setting of MeGUI itself) (Win 7, 64 bit).
Soma
October 6, 2012 at 11:33 am

Figured out what the problem was. When I re-installed my system I didn’t check the AMD OpenCL/Hardware encoding/decoding on the ATI driver package. Installed the driver and it’s working now. Still slow but it cut the usual time by a half even though it’s only using 3% of the GPU power (measured using GPU-Z program).
SubJunk (Post author)
October 7, 2012 at 6:38 pm

@Commander Shepard: To make it faster you can select a faster x264 preset. The presets do not affect video quality.

@Bill: What codecs or codec packs do you have installed?
T
October 31, 2012 at 6:48 pm

When I load the avs file, the program causes the mouse to show a busy animation, I can still click around but “Queue” doesn’t put the file into the queue. Any ideas?
laxsop
November 16, 2012 at 5:07 pm

Can confim Commander Shepards and somas statement. Got also only 3% GPU (measured using GPU-Z @ 580GTX) usage during the encoding. The measurement seems to be correct because other OpenCL-Application show an 100% load using GPU-Z.
Daniel
December 2, 2012 at 6:12 am

Hi subjunk thanks alot for this tutorial… is there anyway to increase the framerate to even more than 60fps?, i heard some tvs interpolate up to 240fps.
SubJunk (Post author)
December 2, 2012 at 10:00 am

@Daniel: Sure, you can make it any framerate you want 🙂 The only thing is that most TVs will only support a maximum of 60FPS, even the ones that display 240fps (my TV displays 600fps but will only accept 60fps inputs)
Anyway if you want to try, feel free to with the NewNum and NewDen parameters, so for 240fps you would use:
InterFrame(cores=4, NewNum=240000, NewDen=1001)
Joseph
December 19, 2012 at 12:33 am

Hello, I have a problem a week ago. I followed all the steps in the tutorial but when you click “save” I get this error. I need help please, I have a month trying to make this work.

This is the image of error…

http://imageshack.us/photo/my-images/846/errormf.png/

This is the Script de AviSynth…

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”)
LoadPlugin(“C:\Program Files (x86)\K-Lite Codec Pack\Filters\Haali\avss.dll”)
dss2(“C:\Users\José\Desktop\Nueva descarga\20110618-Sample-Original.mkv”, fps=23.976).AssumeFPS(24000,1001).ConvertToYV12()
SetMTMode(2)
#deinterlace
#crop
#denoise
#resize
InterFrame(Cores=2)
SubJunk (Post author)
December 19, 2012 at 12:38 pm

@Joseph: It may be the é in “José”. Try putting the file in a different folder and try then.
Hector
December 20, 2012 at 12:15 pm

Hi Subjunk im getting this error message for some reason. What am i doing wrong?

http://imageshack.us/photo/my-images/191/erroruax.png/
SubJunk (Post author)
December 20, 2012 at 2:57 pm

@Hector: Not sure about that one. Are you using the same version of AviSynth from the guide?
Hector
December 20, 2012 at 6:04 pm

Yes i did, i unistalled K-lite codec pack, megui, and avisynth and installed them again but the problem stays, the funny thing is that i already did this procedure a few months ago and it worked after a few attempts but since i just restored my system i have to do it again but this error appears.
SubJunk (Post author)
December 20, 2012 at 8:58 pm

@Hector: Weird! I don’t know what the error means. If it worked before it must work again so I guess just go through the steps again if you want, sorry I can’t be of more help
Hector
December 21, 2012 at 7:55 am

Fixed, in line 4 the (x86) was missing in this command:

C:\Program Files\MeGUI\tools\avisynth_plugin

So i just added the (x86) and now looked like this:

C:\Program Files (x86)\MeGUI\tools\avisynth_plugin

And that solved the problem hope this helps others x86 users. Thanks alot Subjunk.
SubJunk (Post author)
December 21, 2012 at 8:37 am

@Hector: Glad you fixed it. There is a note in Step 7 about that 🙂
Quetz
December 30, 2012 at 1:32 am

I have a question. First to tell that i love you giude. It really works and it saves me a alot of time and space.
You have seen some videos on youtube that are really smooth ? They look like 60 fps but they are 30 beucase youtube supports only 30 fps. I don’t know how they do it. I have seen it in some video recorders (those camcorders) they film 30 but it’s super smooth not chopy. I wanted to do this with my gameplay videos. I have read everything in the net (forums videos and so on) and i can’t find anythink that can help me. Hope you can help.

Merry Xmas and a Happy New Year 🙂
SubJunk (Post author)
January 2, 2013 at 9:57 am

@Quetz: It sounds like you are talking about motion-blur. AviSynth has plugins that can achieve that, I recommend searching doom9 forums for more info 🙂
Eyvin
January 5, 2013 at 6:31 am

Is it possible to make this only bring it up to 48fps instead of 60? The 60fps felt a little too sped up for me in certain scenes, especially in ones with dialog.
SubJunk (Post author)
January 5, 2013 at 10:22 am

@Eyvin: Sure, that stuff is located in the InterFrame documentation at http://www.spirton.com/uploads/InterFrame/InterFrame2.html
For what you want, you would use NewNum=48000, NewDen=1001
L.Antigreen
January 5, 2013 at 1:19 pm

Hello. I have this error. What do I do wrong?
http://i.piccy.info/i7/af3b9bd0568707c1c2be78d81a48cdfd/4-55-366/1644847/Bezymiannyi.png
Aye Jay
January 5, 2013 at 1:57 pm

Thanks so much!! Been looking for exactly this and the instructions made it easy. much obliged 😉
SubJunk (Post author)
January 6, 2013 at 4:08 pm

@L.Antigreen: That means you have a different version of AviSynth installed than the one in the zip file from this article.

@Aye Jay: You’re welcome, cheers 🙂
klerik
January 10, 2013 at 2:30 am

Changelog is not updated (new version from December is much faster than previous, thanks a lot)
SubJunk (Post author)
January 10, 2013 at 9:52 am

@klerik: Thanks for reporting this, the changelog is updated now 🙂
Nicolas
January 10, 2013 at 1:12 pm

Hi,

I have this error http://image.noelshack.com/fichiers/2013/02/1357776638-error.png and I don’t know what to do. I’m doing all correctly and it doesn’t work. Is it possible for you to make a software to convert the video in 48 fps automaticly or in 60fps? with sound?
Nicolas
January 10, 2013 at 2:36 pm

Ok I found the problem 🙂 How to do in 48fps?
SubJunk
January 10, 2013 at 3:34 pm

@Nicolas: For 48fps you would use NewNum=48000, NewDen=1001, like:

InterFrame(Cores=4, NewNum=48000, NewDen=1001)
Nicolas
January 10, 2013 at 4:16 pm

Hi, I don’t know if it worked very well… Check my video, I don’t see the 60FPS in that or it’s my eyes 🙂
Some scene are better, but other scene have the 24 fps look.
http://depositfiles.com/files/thhphhq9m

I put Cores=2 for this one, but I will try with Cores=4

thx a lot for your guide 🙂
SubJunk
January 10, 2013 at 4:53 pm

@Nicolas: The source video is 25fps so it is only outputting the trailer at 50fps. Try getting a trailer at 24fps, then you will get a 60fps video and it will be smoother.
Also you can try using Tuning=”Smooth” for more smoothness
Nicolas
January 11, 2013 at 3:58 am

OK, because I took that on youtube, I will try with Tuning=”smooth”

thx for your help
Nicolas
January 11, 2013 at 4:15 am

Oh, where I put Tuning=”smooth”, because I have an error
SubJunk
January 11, 2013 at 9:21 am

@Nicolas: InterFrame(Tuning=”Smooth”)
Nicolas
January 11, 2013 at 10:53 am

MY NEW VIDEO CAN’T BE UPLOADED, WILL TRY TOOMOROW

PS: I already have InterFrame(Core=4) and it said that I have an error when putting two InterFrame and even if I put (Tuning=”Smooth”) on the same line as the other…
SubJunk
January 11, 2013 at 12:06 pm

@Nicolas: Make sure you use regular quotation marks instead of the slanted ones; it should be Tuning=”Smooth”, not Tuning=”Smooth”
Nicolas
January 11, 2013 at 3:14 pm

I put

InterFrame(Core=4, Tuning=”smooth”)
instead of
InterFrame (Core=4), (Tuning=”smooth”)

It worked.

thx,

do you know where I can upload my video free without account? (more than 100mb/files)
Nicolas
January 12, 2013 at 4:40 am

Check my new video http://depositfiles.com/files/4njtm2ig8
It’s the same, but with smoother action.
thx
Nicolas
January 12, 2013 at 6:13 am

Lord of the rings : http://depositfiles.com/files/x4ysqxhh1
Jojo
January 14, 2013 at 8:08 am

Hello , please help me !!! I have this problem http://postimage.org/image/n8v4yc1hv/ . What should I do ???
SubJunk
January 14, 2013 at 9:19 am

@Jojo: The problem is the characters in your username. Put it in a different folder like just C:\
Jojo
January 14, 2013 at 10:39 am

Oh man !!!SubJunk , Thank you !!!
SubJunk
January 14, 2013 at 10:49 am

@Jojo: You’re welcome, enjoy!
elm
January 21, 2013 at 8:02 am

hi – very very useful script and guide, thanks!

couple of things:
1) things always seem to hang at the end of step 12 – after encoding the new mkv file – and i have to abort (though the converted file can be copied somewhere else and then used before i abort.) any idea why this happens?

2) is there a way to enable intel quicksync for the encoder? it’d speed things up greatly for me as i have no dedicated graphics card in this machine, but i do have a i7 2600k that’s going to waste..

hope to get a reply soon – thanks in advance!
SubJunk
January 21, 2013 at 4:20 pm

@elm: The first thing can be fixed by changing codecs, I recommend uninstalling all codecs and codec packs, restarting the computer, then installing K-Lite Mega 32-bit (no 64-bit!) As for quicksync, probably not
fatboy05
January 24, 2013 at 12:28 am

SubJunk, nice tutorial. i have made a translation of your tutorial and post it in a forum, is it okay?

i also want to ask. can i made a 1080p 60fps video? without resize to 720p? because everytime i tried, it ends up not smooth but lagging instead. and the audio always out of sync. when i added the resize to 720p command, the re encoded video always succesfully converted to 60fps and played smoothly.

so i just wan to confirm, is it possible to produce 60fps @ 1080p or not. or maybe it just my x264 setting problem.

thanks.
SubJunk
January 24, 2013 at 11:15 am

@fatboy05: That sounds great, if you give me a link to the translation I can link to it from here 🙂 Yes 1080p (or any resolution) is possible so the problem must be something else
steve
January 29, 2013 at 5:16 pm

Does anyone know how to do this using Staxrip?