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

Sed
March 25, 2012 at 11:17 pm

and also i forgot to ask that should i put the new version 2 .dll files just into avisynth plugin folder or like the version 1 i also should put them in my sys32 or syswow64 too and if yes, all of them or which one?
thanks again
sed
SubJunk
March 25, 2012 at 11:20 pm

@Sed: 2.0 is not recommended for use yet so it isn’t in this guide. When it is good enough I will update the guide for it.
Sed
March 26, 2012 at 11:51 pm

OK, thanks, actually i did play around with it for a while and i got it working, and right now i am doing my first conversion with 2 (just a test) on a file that i did before with one, its not finished yet, as for being faster, cant say if its faster, as for quality, i just have to wait and see and compare it with the one i did with 1 to be able to say, but i did notice something that made me happy and that’s when i was trying to do some split and joint with 1 it was almost always MeGui crush but so far it did not (don’t know for sure if it has some thing to do with interFrame 1 and or 2 or it was a bug in my system that its not there anymore), anyway i want to really thank you for your hard work (it took me almost 3 months to get comfortable with MeGUI and then i found out about interFrame and another month to get hang of this, but i am really happy as i am finding my way to build a big collection of 60FPS movies, again thanks to you guys.

Sed
Derfu
April 20, 2012 at 9:47 am

Hi Subjunk,

I get a AviSynth Script Error: There is no function named “SetMTmode” I’m kind of a newbie but would like to code some of my 30fps AVI and other video files to 60fps
SubJunk
April 20, 2012 at 10:03 am

@Derfu: Make sure you follow step 1 fully and it will fix that error
Derfu
April 20, 2012 at 12:04 pm

Thank Subjunk =)

MKVMerge will not mux wmv to the new mkv. Is there any way around this? or some other software to aid this mux? Thank you in advance
SubJunk
April 20, 2012 at 12:14 pm

@Derfu: Yeah WMV is a pain in the butt, try to avoid it 🙂 You can try ctrl+f7 in MeGUI which will work for some files, if that doesn’t work it’s probably best just to convert the audio in MeGUI. You can convert it to FLAC which is lossless so it’s kindof the same as muxing 🙂
derfu
April 20, 2012 at 4:37 pm

@Subjunk

I have yet to try ctrl+f7 but will do so later. What would be the script to convert it to FLAC?

Also, I have done a couple converts to 60fps but have not seen any or much difference at all to the original source. Am I missing something here? I do notice when I do download some 60fps torrents that those videos have movement that look real smooth, so far my conversion isn’t producing the smoothness I read other users are experiencing. Is there something wrong with my script.

Here is the script I’m using.

Setmemorymax(1024)
SetMTMode(2,7)
PluginPath = “C:\Program Files (x86)\MeGUI\tools\avisynth_plugin\”
LoadPlugin(PluginPath+”mvtools2.dll”)
LoadPlugin(PluginPath+”RemoveGrainSSE3.dll”)
Import(PluginPath+”InterFrame.avsi”)
.ConvertToYV12()
SetMTMode(2)

InterFrame(FlowPath=PluginPath)
SubJunk
April 20, 2012 at 4:48 pm

@derfu: For the FLAC conversion you can just use MeGUI.
For extra smoothness you can use the smooth tuning, like:
InterFrame(FlowPath=PluginPath, Tuning=”Smooth”)

Plus your script is old, I suggest updating it based on the guide
derfu
April 20, 2012 at 6:42 pm

@SubJunk

I’m quite new and don’t understand the software too much. Can you let me know how to do the FLAC conversion using MeGUI.

Can you give me a script that you use for your upconversion as a template for me to try.
derfu
April 20, 2012 at 6:43 pm

Also want to thank you SubJunk for your quick replies. Great job on this also!
SubJunk
April 20, 2012 at 8:48 pm

@derfu: For the audio conversion, in the main window of MeGUI there is the video section then an audio section below it. Just load your file with the Audio Input option, then choose FLAC in the Encoder settings then click Queue and start the job like with videos.

Bringing your script up to date would be:

Setmemorymax(512)
SetMTMode(3,7)
PluginPath = “C:\Program Files (x86)\MeGUI\tools\avisynth_plugin\”
LoadPlugin(PluginPath+”mvtools2.dll”)
LoadPlugin(PluginPath+”RemoveGrainSSE3.dll”)
Import(PluginPath+”InterFrame.avsi”)
<input>.ConvertToYV12()
SetMTMode(2)
InterFrame(FlowPath=PluginPath)
Jet
April 21, 2012 at 5:15 am

Hi SubJunk,
I want to rotate video. How could I do it with avisynth script?
SubJunk
April 21, 2012 at 9:55 am

@Jet: Looks like there is a plugin called Rotate: http://avisynth.org.ru/rotate/rotate.html
I don’t want to get into the habit of giving general Avisynth support though so if you have more questions like that I suggest using a forum like Doom9 🙂
Derfu
April 22, 2012 at 3:46 am

@subjunk
Thank you for all your help. I have converted a few videos successfully and it has been fun testing this. I recently ran into a problem doing a 1440 x 1080 res wmv. It would process that video about 60% and stop. Any idea why this process is stopping. There was also a mpg4 video that had this problem occur.
SubJunk
April 22, 2012 at 10:26 am

@Derfu: I’m glad it’s working now. Sounds like an FTV video, sometimes codecs for WMV and MP4 do weird things and re-installing or configuring codecs fixes it.
klys
April 22, 2012 at 10:47 pm

when i use megui to make 60fps video,original video is MP4 format,and transform it become 60fps video successfully,but the video before two seconds is the same like the first frame,the same pictuer will lasts two second,other was normal like original vieo without any error,when i transform original video that is avi format is normal use same parameter is normal,i don’t koow where is error,following is my AVS Script:
Setmemorymax(512)
SetMTMode(3)
PluginPath = “C:\Program Files\MeGUI\tools\avisynth_plugin\”
LoadPlugin(PluginPath+”mvtools2.dll”)
LoadPlugin(PluginPath+”RemoveGrainSSE3.dll”)
Import(PluginPath+”InterFrame.avsi”)
DirectShowSource(“E:\BTOB – Insane (HD 1080p).mp4”, fps=23.976, audio=false, convertfps=true).AssumeFPS(24000,1001).ConvertToYV12()
SetMTMode(2)
#deinterlace
#crop
LoadPlugin(“C:\Program Files\MeGUI\tools\avisynth_plugin\Convolution3DYV12.dll”)
Convolution3D(“movielq”) # Heavy Noise
#resize
InterFrame(FlowPath=PluginPath)
SubJunk
April 23, 2012 at 12:01 pm

@klys: Try following Step 8 fully 🙂
kasou
May 1, 2012 at 5:53 pm

my computer keeps crashing after i choose ” directshowsource” in step 9..what should i do?
Rise Against
May 6, 2012 at 1:09 am

Can you please tell me what you mean by “extract the tools folder over the top of your MeGUI tools folder”?
SubJunk
May 6, 2012 at 10:35 am

Just to take the contents of the zip file from the guide and put them into the MeGUI tools folder
bakonfreek
May 11, 2012 at 1:21 am

Can there be a way to do this with FFMpeg?
SubJunk
May 11, 2012 at 10:36 am

FFmpeg can take AviSynth scripts instead of video input so yes 🙂
horam07
May 14, 2012 at 12:30 pm

What is the script to do it on live in ffdshow video decoder?…
i put the script of the guide and show syntax error mesage..

sorry my english
zeroka
May 31, 2012 at 1:32 pm

hi…i want to ask something…
I want to make a 60fps video from an AVI video…
but when i`m inputting the video..one of the 3 buttons shows AviSource instead of DirectShowSource..
is this the right one ??
because after the encode process finished…suddenly the video have an extra 1 second at the beginning..
which make the video & audio could not fully sync….
anyway thx before…
SubJunk
June 1, 2012 at 10:09 am

@zeroka: Yes, that is the right way to do it. Maybe the avi file has an audio offset that MeGUI didn’t detect. You can set it yourself using MKVMerge 🙂
Nathan
June 2, 2012 at 6:20 pm

I keep on getting LINE 8 error when it try to Que it. This didn’t happen before. Please fix.
SubJunk
June 2, 2012 at 9:35 pm

@Nathan: What is the script you’re using and what is the exact error?
Kenny
June 3, 2012 at 7:06 am

im stuck at 99.98% what do i do?
SubJunk
June 3, 2012 at 11:16 am

@Kenny: When that happens, the file is usually 100% finished but the job isn’t stopping. It’s related to codecs/containers, usually happens with MP4s but can with others too. Just make a copy of the output file then cancel the job.
bakonfreek
June 13, 2012 at 5:40 pm

it says it can’t find “mediainfowrapper” and cannot proceed, what in the unholy fucking shit is that!?
SubJunk
June 14, 2012 at 12:03 am

@bakonfreek: Sounds like a MeGUI error, try updating the program or reinstalling it
kama
June 14, 2012 at 7:47 pm

I have the same problem than Kenny, it gets stuck at 99% but when I copy the output file and try to open it says the file is corrupted. I noticed this happens when I activate the “Prefer DSS2 over DirectShowSource” option.

Any clue?
john smith
June 19, 2012 at 5:41 pm

I must say this program and your very detailed instructions and illustrations did what you said it would and that is unimaginable results there is a few elements that needs to be addressed if i may say, but i am not writing this for that reason no. My main reason is to and if i may elucidate a bit, Is to publicly THANK YOU for the time and effort in posting a most informative step by step instructional tutorial on something i all ways had an interest somewhat in. You are unquestionably one of the most intelligent, intellectually and technically inclined individual, for that you deserve to be commended, so i commend you sir and i thank you again for sharing your knowledge and expertise and hope that you continue the good work thank you.
SubJunk
June 21, 2012 at 12:37 pm

@john: Thanks a lot for the encouragement, I really appreciate it 🙂
Waqas Qamar
June 23, 2012 at 2:01 am

A gazillion kudos! This is by far the coolest thing I have experienced regarding video encoding. I wasn’t expecting results this awesome.

Just one question, I have a sandy bridge cpu, can quick sync be of any use here? (I haven’t tried using GPU=true, not expecting much since its an on board gpu. However, Quick Sync would certainly speed up the awesomeness). I’ll try GPU=true and share the results for anyone with modern on board graphics.

Once again AWESOME WORK.
SubJunk
June 25, 2012 at 10:12 am

@Wagas: Thanks for the kind words, it’s really great 🙂 I’m not sure about Quick Sync, sorry
Heike
June 28, 2012 at 3:54 am

Hello and thanks for the guide! Got it working however it takes TIME! Right now I have at best 2.40fps enconding speed.. it says it will finish after 2 days rofl.. which isn’t really up my alley.. Any suggestions?
SubJunk
June 28, 2012 at 8:54 am

@Heike: Try using the fastest x264 preset in MeGUI and make sure you set the correct number of cores in the script.
Shawn
July 6, 2012 at 1:30 am

Awesome work, takes awhile to get used to the smoothness of the video, but you get to pick out details that you’d never see at high-speed 24fps. My only problem is because of the quality setting i used for the video, my file size grew fourfold, 2 gigs grew to 8 gigs. Encoding went at around 8 fps on my q6600 with 8800gt
Phil
July 9, 2012 at 9:28 pm

Hi,

It’s been a while since I dabble with conversion but now I’d like to get back in it. One thing though is that I lost my scripts and tools in an HD crash a couple of months ago. Good thing you keep an archive of all the comments because I found the script I used to use the most in a comment I left, here it goes

Setmemorymax(1024)
LoadPlugin(“C:\Program Files (x86)\60fps\MeGUI\tools\avisynth_plugin\mt.dll”)
SetMTMode(2,0)
LoadPlugin(“C:\Program Files (x86)\60fps\MeGUI\tools\avisynth_plugin\mvtools2.dll”)
AVISource(“G:\test.avi”, audio=false)
#deinterlace
#crop
#denoise
#resize
super = MSuper(pel=2, hpad=0, vpad=0, rfilter=4)
backward_1 = MAnalyse(super, isb=true, blksize=16, searchparam=3, plevel=0, search=3, badrange=(-24))
forward_1 = MAnalyse(super, isb=false, blksize=16, searchparam=3, plevel=0, search=3, badrange=(-24))
backward_2 = MRecalculate(super, backward_1, blksize=8, searchparam=1, search=3)
forward_2 = MRecalculate(super, forward_1, blksize=8, searchparam=1, search=3)
backward_3 = MRecalculate(super, backward_2, blksize=4, searchparam=0, search=3)
forward_3 = MRecalculate(super, forward_2, blksize=4, searchparam=0, search=3)
MFlowFps(super, backward_3, forward_3, num=FrameRateNumerator*2, den=FrameRateDenominator, ml=10000)
ConvertToYV12()

***

As you can see it merely functions as a doubler, which is what I want. Now I think I’ve reinstalled everything, the problem is that I can’t by a simple syntax error. Everytime I try to use the script I get :

Avisynth open failure
unexpected character “””
(H:\Stuff\60a.avs, line 2, column 11)

Now if I remove the ” I get the following

Avisynth open failure
Script error: expected a , or )
(H:\Stuff\60a.avs, line 2, column 13)

Any idea why that is?

Thanks!
SubJunk
July 11, 2012 at 1:07 pm

@Phil: It’s probably because the quotation marks are in a stylized format that AviSynth can’t recognise. Try replacing them all by typing them with your keyboard. However you really should update that old script because the new ones are much better quality and faster. The newer one can also double the framerate so you would not lose any functionality.
Phil
July 12, 2012 at 11:23 pm

Hi Sub,

You mean to use the new one in your step 7 ?

Two questions :

1: My workflow is that, with the script I posted I could frameserve from Sony Vegas to VirtualDub and let it encode in whatever codec I wanted, can I still do that with the new version of the script?

2: Which line, if any, should I change in order to make the script a doubler, cause if I have a 25FPS source I want to double it into 60fpps and not convert it to 60.

Thanks for your help.
Phil
July 12, 2012 at 11:48 pm

I mean “to double it into 50fps”
SubJunk
July 12, 2012 at 11:55 pm

@Phil: 1) Yes, I don’t think there will be any problems.
2) The default action of the script on this page is to convert 25fps videos to 50fps
Phil
July 13, 2012 at 1:01 am

Well I get a syntax error line 7 column 1

I’ve copied the script from your page and replaced all (“”), here it is again just to be sure

Setmemorymax(512)
SetMTMode(3,6)
PluginPath = “C:\Program Files\MeGUI\tools\avisynth_plugin\”
LoadPlugin(PluginPath+”svpflow1.dll”)
LoadPlugin(PluginPath+”svpflow2.dll”)
Import(PluginPath+”InterFrame2.avsi”)
.ConvertToYV12()
SetMTMode(2)

InterFrame(Cores=6, GPU=true)

Now, in the previous script I was using the was a line that calls for the location of an AVI source, so that Vdub will open the file I want to frameserve. Do I need this line or is it part of the “Interframe2.avsi”

Thanks
SubJunk
July 13, 2012 at 1:23 pm

@Phil: You’ll need to replace the input line with your input, so for example:

Setmemorymax(512)
SetMTMode(3,6)
PluginPath = “C:\Program Files\MeGUI\tools\avisynth_plugin\”
LoadPlugin(PluginPath+”svpflow1.dll”)
LoadPlugin(PluginPath+”svpflow2.dll”)
Import(PluginPath+”InterFrame2.avsi”)
AVISource(“G:\test.avi”, audio=false).ConvertToYV12()
SetMTMode(2)
#deinterlace
#crop
#denoise
#resize
InterFrame(Cores=6, GPU=true)
Phil
July 13, 2012 at 11:29 pm

All good so far now. Thank you for your time!
klys
July 15, 2012 at 5:54 pm

I have two questions about this:the frist is at the step 7,Important note #3,you say recent video card,whther it is independent video card or not,I don’t see what you mean.Or recent is the latest means.Could you explain,please.Not is use GPU coding no CPU coding quality good,I heard with GPU codes will reduce the video quality.Don’t know if it’s really true.The second is I have some 1080i,I want to turn them into a 720p or 1080p video that is 60fps.I can do the same as the one above,or still need to add other parameters.
Thanks.
ayan
July 18, 2012 at 7:50 pm

Dear SubJunk,
Hope to get your reply soon. I am trying to convert my 25 fps video to 50 fps (instead of 60fps) using interframe, and in the description , it is written that

if value of NewNum=> 0 – Automatic output framerate then If the input framerate is 25FPS, output 50FPS

i tried with 0 using the following 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”)
AVISource(“C:\Desktop\25p.avi”, audio=false).ConvertToYV12()
SetMTMode(2)
InterFrame(NewNum=0, NewDen=0, Cores=4)

–> in the above case i get 6 times increase in frame rate e.g: if original # of frames= 125 (for 25p video) then after conversion i get # of frame = 750(for 50p)
which is wrong as after conversion # of frame for 50p video should be 250(125 original+125 interpolated) frames.

i also tried with the case
InterFrame(NewNum=5, NewDen=1, Cores=4) and in this case i am also getting wrong frames number (after conversion for 50p i am getting less frames (60 frames))

please let me know why i am not getting the desired frame number (i.e 250 frames after the conversion from 25p to 50p)
thanks in advance,