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

Jarno
October 16, 2010 at 11:17 pm

My encoding stops at 98,6 % after an hour. Iam trying to convert 200 mb file, how long should it normally take to encode such a small file with high settings.
Christiano
October 20, 2010 at 5:42 am

It is normal some flaws make the video after encoding with the script? Stayed in
missed some points and a half grid. Others were perfect. thanks
SubJunk
October 21, 2010 at 8:18 am

Hi Jarno,
I can’t say how long it should take, but it should never stop at any point. Try reinstalling codecs, and try to avoid doing demanding things while encoding (like playing CPU-heavy games), since sometimes that can make it stop.
Steven
October 26, 2010 at 8:09 pm

Hello,
When trying to use this tutorial to add frames to your “Original” MKV that you have in the beginning of the write up, MeGUI crashes with the error: invalid arguments to function “ssrc”. I used the Avatar “Original” MKV only as a way of testing this as I have no short clips myself. K-lite codec pack is installed. When converting only the video there are no problems. All available audio encoders result in a crash. Have you experienced this? Any solutions?
SubJunk
October 27, 2010 at 1:55 pm

Hi Steven,
There is no audio in the original clip.
Christiano
October 28, 2010 at 3:09 am

Which method to convert dvd’s, which are in vob files? thanks
SubJunk
October 28, 2010 at 10:31 am

Hi Christiano,
You can use MeGUI’s File Indexer (Ctrl+F2 in the program)
redman458
October 29, 2010 at 6:34 pm

The new scripts are great! Thanks!
SubJunk
October 29, 2010 at 6:41 pm

Hey redman, thanks for the feedback! Glad you like them 🙂
Christiano
November 11, 2010 at 3:42 am

After the updates I had improvements in the results of videos. Solved some
bugs that appeared. But I can not convert videos in 1080p yet. He says it is
unbearable or that the application is already open in another process. I do not understand this.
Thanks
SubJunk
November 11, 2010 at 5:24 pm

Hi Christiano,
I haven’t seen that error before. It might mean you don’t have enough RAM but I don’t know.
Christiano
November 19, 2010 at 1:54 am

I converted a movie that was in 1080p. “Iron Man 2.” But the
play on the PS3, it ran crashing. Question: The PS3 can run movies
1080p 60fps? Congratulations for the site and keep up to date. The script is getting better. thanks!
SubJunk
November 19, 2010 at 9:20 am

Is that using PS3 Media Server or playing directly on the PS3?
Thanks for the kind words 🙂
Christiano
November 20, 2010 at 1:24 am

I use directly on the PS3. I always leave the files with the extension m2ts.
SubJunk
November 20, 2010 at 8:59 am

Try using PS3 Media Server 🙂
Cipher
November 21, 2010 at 5:57 pm

Any idea why .wmv files are stuck encoding the last second of a video?
SubJunk
November 22, 2010 at 10:26 am

Probably a codec thing. Try uninstalling your codec pack/s, restart the computer, then install a different one
Sidder
December 14, 2010 at 12:04 pm

Can someone please help? I’m trying to convert my videos to 60 fps. But I get an error that says there’s no such function name SetMTMode. Then I removed that line. Then another error message came up and says MSuper: Clip must by YV12 or YUY2. Is there a fix for this?
SubJunk
December 14, 2010 at 12:41 pm

Hi Sidder 🙂 It seems like that error would be caused by the wrong files. Please double-check that you followed Step 1 exactly 🙂
Sidder
December 14, 2010 at 6:23 pm

I followed Step 1 exactly and all other steps exactly, I still get an error that says “MSuper: Clip Must be YV12 or YUY2”. Is there a way to fix this?
SubJunk
December 14, 2010 at 6:28 pm

The “there’s no such function name SetMTMode” error you described is caused by the program using the wrong avisynth.dll file.
Make sure you have overwritten the original avisynth.dll with the downloaded one.
You can paste it to both the folders (System32 and SysWOW64) to be sure.
Sidder
December 14, 2010 at 6:48 pm

I already pasted the avisynth file in the system folder. I’m not getting that SetMTMode error anymore. I’m only getting an “MSuper: Clip Must be YV12 or YUY2” error message. I’m trying to encode a raw uncompressed AVI file recorded at 29.97fps that was recorded from my TV Tuner. Is there another to fix this without getting this error message again.
SubJunk
December 14, 2010 at 6:50 pm

Are you not getting the error anymore because you removed the SetMTMode line from the script, or is the line still in the script?
Sidder
December 14, 2010 at 6:57 pm

No, I didn’t remove the SetMTMode line. I left it in the script after pasted the newer avisynth.dll to system32 and sysWOW64 folders. I’m only getting the “MSuper: Clip Must be YV12 or YUY2″ error message” I’m trying use your method of encoding so my video file is encoded at 60fps as my TV Tuner won’t record anymore than 29.97fps when output into a raw umcompressed AVI.
SubJunk
December 14, 2010 at 7:00 pm

Ah I see, cool 🙂
Well the error is related to the colours of the video. Try to move the line “ConvertToYV12()” to before the MSuper line. It may give you an error when you do that, in which case you can do 2 conversions (convert your clip to YV12 first, then load the new file using the 60fps script).
Hopefully that makes sense 🙂
Sidder
December 14, 2010 at 7:04 pm

Ah! Thanks! I think this fixed it. After I moved the ConvertToYV12(), I no longer see any error messages. Thanks.
SubJunk
December 14, 2010 at 7:05 pm

Cool, glad I could help 🙂
edilvan
December 21, 2010 at 11:27 am

No seu exemplo, seu arquivo nem dobrou de tamanho mas, aqui com um arquivo de 50mb, ele cresceu para 300mb!
É normal isso?
Tom
December 25, 2010 at 3:21 pm

Everything worked perfectly! Even a dummy as myself got it from the first try. Thank you SubJunk!

I just wonder how come my new 60FPS video file is smaller then the original (apprx 55% of the original size).
erick
December 29, 2010 at 3:38 pm

thaaaaaaaaaaaank you so much for this tutorial. now i can watch my videos on 60 fps hahaha. btw, is there a way to make the conversion process faster? 😀
pyro
December 30, 2010 at 4:57 pm

thank you very much! but can i like pause the conversion and continue it on the other day?
SubJunk
January 2, 2011 at 1:40 pm

@pyro: You’re very welcome 🙂 MeGUI doesn’t support pausing. Maybe it will in the future.

@erick: Glad you like it 😀
You can make it faster by getting faster hardware or overclocking hehe 🙂

@Tom: Great, thanks a lot for the feedback 🙂
If the visible quality of the files are the same, it probably means the original file was using an inferior codec or codec settings.

@vulcan: You’re welcome 😀

@edilvan: Sorry, I only speak English 🙂
Phil
January 11, 2011 at 2:11 am

Well thanks for the script. Actually I created the script and opened it in Vdub instead of recoding with MEgui. Vdub opened the file without a problem and looking up the file information told me that it was in 60fps so I could actually play it back in that frame rate through Vdub right there, even before recoding it.

Two questions though:

1: Is it normal if it doesn’t open WMV’s?

2: I have a 25fps file and opening it in Vdub through the script doesn’t change the frame rate. Vdub still tells me that the file is in 25fps but if I try to play it back the sound is slowed down…?

Thanks for the input
SubJunk
January 11, 2011 at 8:32 am

@Phil: Hi 🙂
If you would like a realtime guide there is one here.
Unfortunately the quality will be lower than with this script and that is the reason for the creation of this guide; so that anyone can watch the smoothing at the highest quality with any computer instead of being bound to their hardware 🙂

1) WMV’s are notoriously problematic! The answer is no, it’s not normal, but it’s a common problem 🙂 I suggest wiping all codecs from your system then installing the latest K-Lite Mega Codec Pack, without the 64-bit addon.

2) It’s possible that Vdub doesn’t handle Avisynth scripts as nicely as MeGUI. I suggest just using MeGUI.
Ipman
January 13, 2011 at 7:14 am

How to get more Quality? How can i change it?
SubJunk
January 14, 2011 at 2:40 pm

@Ipman: This script is the highest quality I’m aware of
Phil
January 15, 2011 at 1:49 pm

Thanks for your reply and the link.

Got another question here:

Is there a way to double the frame rate and not put everything in 60. I have files that are in 24 and 25 and I would love them to become 48 and 50 respectively. In my opinion what was shot in 24/25 looks better converted to 48/50 rather than 60

Anyway you tip about achieving this and/or your feedback on my opinion is appreciated.

Thanks
SubJunk
January 15, 2011 at 2:07 pm

@Phil: You’re welcome 🙂

The script already makes 25fps content 50fps, 30fps content 60fps, and all others (like 29.97fps and 23.976fps) 59.94fps (that is what lines 17-25 do).
This is to maintain compatibility with TVs, since TVs usually support 50Hz-60Hz but not 47.952fps.

However it is up to you what you prefer, so to make it always double the framerate you can change this part of the Quality Script:

Framerate == 25 ? Eval(""" MFlowFps(super, backward_3, forward_3, num=50, den=1, ml=10000) """) : \ Framerate == 30 ? Eval(""" MFlowFps(super, backward_3, forward_3, num=60, den=1, ml=10000) """) \ : Eval(""" MFlowFps(super, backward_3, forward_3, num=60000, den=1001, ml=10000) """)

To this:

MFlowFps(super, backward_3, forward_3, num=FrameRateNumerator*2, den=FrameRateDenominator, ml=10000)
Phil
January 16, 2011 at 2:22 am

Oh so that’s why it rounds it up. Thanks for the modification, I will give it a try.

Well, so far then I am good with pretty much everything except this one problem left. Take a look a this:

http://img703.imageshack.us/i/capturezv.png/

This video plays fine in Media Player, VLC and KMplayer. If I drop it in Vdub it will also look fine. It is only when I open it through the script that the color streaks appear.

Now I gotta say that this file is not the original video. I took the original, dropped it in Sony Vegas, edited, color corrected it and recoded it in Xvid.

If I open the original file, which is an MP4, through the script (modified for MP4 that is) it will look fine. If I recode it this way it will also be fine.

Thing is though, I’ve been using Vegas, professionally, for the last 6 years so I am very efficient with it. So editing and color correcting is a breeze through it whereas through Vdub it’s a drag. Needless to say I’d like to keep my workflow if possible 😉

Any ideas?
SubJunk
January 16, 2011 at 10:46 am

@Phil: I have no experience with Vdub or Vegas so it’s hard for me to say. Sorry I can’t be of more help!
Phil
January 17, 2011 at 10:57 pm

The problem was that 852×480 is not 16×16 safe. So, instead of rendering it out of Vegas in 852×480 I had to do it in 848×480.

The recoded file now opens fine in Vdub through the script. So as you can see the problem was not related to either Vegas or Vdub. The file size simply needed to be set to a codec friendly resolution compliant to 16×16 multiples
glypto
February 5, 2011 at 2:10 am

Wow, great tool and very clear instructions, thank you very much, this is exactly what I was looking for !

Just One question:
Some TVs can insert frames to movies/videos so they are smooth and do not judder (on my Panasonic G20 it is called “Intelligent Frame Creation”). This however makes movie look different, more like home video – people call it “soap opera effect”. Can I expect the same when converting 23.976 > 60 fps using this script ?
Thanks.
glypto
February 5, 2011 at 6:22 am

On AVS Forum (http://www.avsforum.com/avs-vb/showthread.php?p=18890733#post18890733) widezu69 says:
“The script produces an infamous “soap opera” effect because it looks like the stuff seen on tv played at 50i. Some people, like me get used to it after a while, some people don’t. If you are after smooth motion but still with that filmic look, replace the third last line in the script with these lines:…”

The line that applies to 23.796 fps is this I guess:
MBlockFps(super, backward_3, forward_3, num=72000, den=1001)

In case I want to apply this to your Speed script, I suppose it should replace following line with the above(for 23.976fps):
MBlockFps(super, backward_3, forward_3, num=60000, den=1001, mode=0)
(it’s the 3rd line from bottom)

Am I right ?

Thanks
SubJunk
February 7, 2011 at 11:01 am

@glypto: Yes, you’re right. You can either do 72000 or 48000 🙂
Connor
February 12, 2011 at 11:46 am

Thank you so much for this, but I need help.
I’m at the step where I must prefer dss2 over direct show source, and the box is shadowed out, as in I can’t check it.
Am I doing something wrong?
SubJunk
February 12, 2011 at 2:50 pm

@Connor: You’re welcome 🙂 Please check the FAQ section of the post
noobie
February 23, 2011 at 11:19 pm

hi, i followed everything correctly until the last step.. and i clicked ‘start’ and it says, 9hours remaining. and my cpu is working at 100%, is it normal and should i continue? lol…
SubJunk
February 24, 2011 at 11:34 am

@noobie: Sure, that can be normal. It all depends on how fast your computer is, the resolution and length of the video (higher resolution and longer length take longer), and the codec settings.
You can make it faster by using the “Ultra Fast” x264 preset, which will make the output file larger but will take less time.
ak4115
February 24, 2011 at 12:14 pm

Hi, could you provide me with a 120hz variant that interpolates anything to 120hz.

Also I have serious problems with megui. It either hangs, or won’t start conversion on video :/ strange as preview, and other progs work fine so it’s not a decoder problem . I’ll try that net framework reinstall later.
SubJunk
February 24, 2011 at 11:18 pm

@ak4115: Hi 🙂 If you want exactly 120FPS, change the value of “num” to 120 and “den” to 1.
If you want the proper, divisible framerate, use num=120000 and den=1001.