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

Stanko
May 22, 2014 at 10:49 pm

Hello and thanx for tutorial. This is Great!
I am converting HD football match from 1280-720 29.97fps to 1280-720 60fps, everything looks fine after 8 -9 hours of decoding except that in converted video i always see trace of soccer ball, when player hit it, especially when some player hit ball quick and hard, than ball fly with “trace” of balls behind..Any solution?
Thank You.
Maturo
May 26, 2014 at 5:34 pm

Hey amazing tutorial! I just have one quick question, everything is great up until the Queue portion in step 12. I press start but it shows nothing and doesnt convert at all. its very irritating. heres what it looks like, http://prntscr.com/3mnss2 thanks
SubJunk (Post author)
May 27, 2014 at 12:15 pm

@TSM Sorry it didn’t work out for you but it’s really very simple if you follow the instructions exactly 🙂 The cool thing is that even though it take a bit of time (5 minutes or so) to set up initially, it’s very fast on subsequent times.

@Stanko You can try tuning=”Smooth” 🙂 See the InterFrame documentation for more possible options

@Maturo Thanks 🙂 It looks like you might have missed the last part of Step 11, “click Queue in the Video encoding section”. Hope that helps 🙂
Gntx
June 2, 2014 at 3:37 am

Hi, everything works just fine, but I get “ghost frames” how can I fix that?
GoLfWRC
June 15, 2014 at 6:26 am

Hi Blog Writer,

I know this is useless when watching on a normal computer monitor but I really need to know how to raise a video frame rate to 120fps or above from this method? i.e. by modifying a script above ?

Thanks guy.
SubJunk (Post author)
June 15, 2014 at 4:47 pm

@GoLfWRC You can specify any framerate, for 120FPS use:
InterFrame(NewNum=120000,NewDen=1001)
Sean
June 17, 2014 at 10:09 am

Umm, Step 8. “Prefer DSS2 over DirectShowSource” is grayed out, i am not able to click it?!
SubJunk (Post author)
June 17, 2014 at 12:14 pm

@Sean Check the FAQ section 🙂
Stephen
June 18, 2014 at 12:54 am

Hi, I was wondering if it is possible to create a batch such that you can convert multiple videos? Any help would be greatly appreciated.
Trendle
June 18, 2014 at 11:57 pm

Why aren’t you allowing my comments? I don’t get it.
SubJunk (Post author)
June 19, 2014 at 11:01 am

@Stephen Check out InterFrameGUI at http://highframerate.wordpress.com/interframegui-download/ 🙂
jeffro
June 23, 2014 at 8:08 am

I’m suddenly getting the error “Direct Show Error – Unable to render the file. You probably don’t have the correct filters installed” in the AviSynth script creator. This happens when using AviSource. Seems to work fine with a video that uses DirectShowSource. The thing is though, it was working previously! I have no idea what changed, how to see what filters are installed and of course it doesn’t mention what filter is missing. Any suggestions?
Brian
June 27, 2014 at 7:45 am

Hi SubJunk!

I really want this tutorial to work because it looks amazing but I’m having some problems. When I’m installing the plugins for MeGUI it keeps asking me if I want to overwrite the existing files or skip it. Is that normal? Also once I restart MeGUI after installing the plugins, every time I run MeGUI a message says “MeGUI cannot find at least one required component. Without these components, MeGUI will not run properly (e.g. no job can be started).”
HEEEEEEEEEEEEEEELP
SubJunk (Post author)
June 27, 2014 at 3:25 pm

@Brian Sounds like MeGUI didn’t install correctly, maybe try uninstalling and installing it again. It should be ok to let MeGUI overwrite files 🙂

@jeffro I’ve fixed that error before by re-installing or updating K-Lite Mega Codec Pack, hopefully that works for you 🙂
Ian
June 28, 2014 at 1:06 am

Hi SubJunk,
Thanks for the guide, very useful and it works a treat, but can you help me please. Is there any way to keep the size of the encoded file to around 4.0- 4.5gb.
Thanks
SubJunk (Post author)
June 28, 2014 at 10:14 am

@Ian you can use a higher CRF value to lower the filesize 🙂
Mando
July 2, 2014 at 12:28 pm

Can anyone that has figured it out make a youtube video for this? Please?
Donder
July 2, 2014 at 10:19 pm

So I’m running into a weird behavior you may have seen. I’m encoding a video, and it’s gotten through 99.9% of the file, then it just freezes and does nothing. It has maybe 12 seconds left of estimated time, and only a few frames to process, but it never finishes. I’ve seen this happen a larger MP4 file that’s about 3.4 GB, and then on an 80 MB avi. I’ve tried tuning the encoder mode from 16 to 23 and a few in between just to see if that may kick it into gear, but no luck.

Any help or suggestions would be appreciated.
Ezequiel
July 4, 2014 at 3:48 pm

Hello SubJunk, I seem to have a bit of an issue, at least I think it’s one.

I’ve followed the steps correctly past Queueing and conversion. Now, with the part of Muxing. I have the original video and converted video in a folder alone, and when I mux, with the audio, it seems that the framerate doesn’t change at all. Am I missing something?

Would I need to specify a target framerate? I used the copy pasta you provided for the script with a few minor additions, mainly just the addition of the GPU usage.
Stefan
July 5, 2014 at 7:48 pm

Hello!

Big thanks for the tutorial! Already got 2 great Videos out of it.

Unfortunately most of the videos I try to convert don’t finish. MEGUI always Stops on “encoding Video” at 99.xx% and doesn’t keep on going.

Do you have an idea what that problem is?
Best regards!
SubJunk (Post author)
July 6, 2014 at 1:07 pm

@Mando Great idea. If someone does it I’ll be happy to link to the video from the article 🙂

@Donder @Stefan It seems to be a codec configuration issue. I’ve fixed it in the past by reinstalling K-Lite 🙂

@Ezequiel It probably means there was some mixup with the filenames, make sure you really are using the output video 🙂
Lodvib
July 8, 2014 at 8:01 am

I did everything i was suppose to do (apparently not) and when i choose the video input on step 9, which is a 4k video i get this error http://puu.sh/a11Tq/9b6c48329a.jpg

AviSynth Script error:
DirectShowSource: Timeout waiting for graph to start.
Heyrwq
July 9, 2014 at 10:37 am

Dont know why but when I get up to step 9, I select my video input and hit “Save” but I get this error “FILENAMEHERE.avs can not be opened. Please make sure its a valid AviSynth script and that AviSynth is properly installed. Error message for your reference. Can’t read the video stream.”

I checked the 3rd line on the 60FPS preset I made and it does bring me to the correct location, However I do seem to be missing svpflow1.dll in the avisynth_plugin folder. Any ideas?
Donder
July 10, 2014 at 3:31 pm

@Donder It seems to be a codec configuration issue. I’ve fixed it in the past by reinstalling K-Lite 🙂

That didn’t seem to fix it. Think it might be with the format the video is in originally? One of the files it does it consistently on is a .m4v, and it’s a 3.53 GB file as well. Whereas the majority of the others that I’ve succeeded with are .mkv’s and .avi’s, but those are generally between 6 and 8 GB files.

Thoughts?
SubJunk (Post author)
July 10, 2014 at 4:23 pm

@Lodvib That could be a codec issue or a computer memory/speed issue

@Heyrwq It’s possible there’s a special character in the path, MeGUI doesn’t like special characters
Trendle
July 11, 2014 at 8:42 am

I have the same problem as Lodvib… only happens with 4K video.
SubJunk (Post author)
July 11, 2014 at 10:08 am

@Trendle I just opened a 4k video on my computer and it took about 600MB of memory to do it. Do you have enough free memory when you attempt it?
zed026
July 13, 2014 at 11:43 pm

@SubJunk. I am having a problem. The problem is that my GPU uasage is only about 1-2% at max and not more than that. So i was wondering if there was something wrong with the script or not. The script that i am using is as follows:

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

InterFrame(Cores=4,GPU=true)

Any and all the help is much appreciated.
Nic727
July 14, 2014 at 4:58 am

Hi,

in MEGUI, When I click “save” after clikcing on “Direct show source” etc… I have this error :

The file C:\Users\____\Videos\_____.avs cannot be opened. Please make sure it’s a valid AviSynth script and that AviSynth is properly installed
Error message for your reference : Can’t read the video stream

My video is in MP4 format. Do I need to change for MKV?
Nic727
July 14, 2014 at 5:55 am

I found what was the problem. I just have to copy some Avisynth tool to Avisynth pluging in MeGUI.
Isaac Verdugo
July 16, 2014 at 8:34 am

So if I wanted it encoded for 12o frames the code would like this

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

InterFrame(Cores=4)
InterFrame(NewNum=120000,NewDen=1001)
?

is this right?
SubJunk (Post author)
July 16, 2014 at 11:37 am

@zed026 that’s normal, the GPU is just so powerful for this type of thing it doesn’t need to try hard to do its job

@Isaac Verdugo almost. The bottom two lines should be merged, like this:
InterFrame(Cores=4, NewNum=120000,NewDen=1001)
ShinyZealot
July 16, 2014 at 11:53 am

Have the same problem as Nic727, cant open the avs in MeGUI, its driving me crazy. I checked and already copied all the tools, the files are there. Also when I try to open the .avs in MeGUI again after the error, it says unable to load library in “compose” and shows the locations of the files thereafter. They are there, im not kidding.

Can I do step 10+ with another program that doesnt bitch around so much at my PC?
Q
July 16, 2014 at 7:15 pm

I know that nic asked this already, but what do you need to do to fix the “Can’t read the video stream” error?
zed026
July 17, 2014 at 8:08 am

@SubJunk thanks for the info. Is there any i can force the gpu to work harder or something. Also if I use preset as medium it takes around 5-6 hours to finish a movie. The movie in question is say of 8-10 GB size from the original file. So is the time required to complete normal?
Thanks again.
Peter
July 18, 2014 at 10:44 am

Hey guys, i just wanted to know if the final bit rate for the encoded files affect quality at all? i’m relatively new to this & if possible would like to make sure that no quality suffers what so ever.
Niteesh Pandey
July 19, 2014 at 1:26 am

@SubJunk I am new to this post and I definitely want to convert some of my favorites to the smooth 60 fps version. I have downloaded the tools : MEGUI 0.35, K-Lite Codec 1060 Megapack, mkvtoolnix-amdx64-7.0.0.
I have a Lenovo Y510p with I5 4200M (2 Cores) and GPU (Nvidia GTX 755M 2 GB) and 8 GB RAM on windows 8. Can you please provide a precise script as per the specifications for me to use. Please, I will be greatful for this help.
Niteesh Pandey
July 19, 2014 at 3:42 pm

@SubJunk The output video of the conversion has a bit of a glitch wherever there is some fast paced action in the movie. You can actually see the trail of hands and legs when character is running or doing kung-fu. Can you suggest some modification to the script?I used your original one with GPU = True and core = 2.
asd
July 22, 2014 at 11:54 am

MKVMerge makes my videos 22 fps again after successfull conversion.
SubJunk (Post author)
July 22, 2014 at 12:56 pm

@ShinyZealot Maybe there is a special character in the path to the files. Sure you can use any program that supports AviSynth like VirtualDub for example.

@Q Sounds like there’s a missing codec so try installing K-Lite Mega with the “Lots of Stuff” setting

@Peter The final bitrate is one factor in quality but other things matter more like codec settings. If you want visually lossless then use a CRF value between 12-16.

@Niteesh Pandey Please see the FAQ for the answer to your question 🙂

@asd Are you sure you’re putting the output file into MKVMerge and not the original file?
sadkl
July 24, 2014 at 12:12 am

I get this error Please make sure it’s a valid avisynth script and that avi synth is properly installed.
CAN’T READ THE VIDEO STREAM.

plz help?
sadkl
July 24, 2014 at 2:17 am

ok I fixed my problem but after conversation my videos look exactly like there were before.Why is that? when I go to options it says that it’s 60fps but it doesn’t look 60fps
sadkl
July 24, 2014 at 2:27 am

I did it I think you felt it and sent me the power to accomplish this.I love you!!
Jon
July 25, 2014 at 11:23 am

Hey I’ve followed the guide and am currently converting an hour long video I’m looking at about a 15 hour conversion time is there anything I can do to potentially speed this up?
Jon
July 27, 2014 at 9:10 am

I just spent two days converting a full movie over to 60fps but notice that I get some buffering issues when I try and stream it over my network to my roku box. Is there any settings in the conversion process to help with this or no?
Esoterin
July 27, 2014 at 10:37 am

Your Process is impressive, but in your sample output file 20110618-Sample-InterFrame when Jax Flips his lighter at about third frame at 25 seconds, there is some pretty sever video garbling around his lighter and hands especially right when he flips open the top of the lighter is there a way to reduce that? I have tried the file in MPC-HC 1.7.6.71, VLC, WMP, and PowerDVD 13. Also why does MKV use Haali I had read in the K-Light forums that LAV works better. Thank you for your time and thoughts
zed026
July 28, 2014 at 5:52 am

@SubJunk bro any suggestions for making the GPU work extra hard to decrease the time required for the overall process. Thanks in advance. Please check my previous comment for details of the script that i am using.
TenFilip
August 4, 2014 at 4:55 am

Hi,

quite a call for muscles – my 2500k@4,8 GHz struggles for about 3 h with 6,3 GB 720p mkv file!
So it looks like that if I’m to convert my current collection, I would finish with PC running like ~6 days on a high power usage. 5$ at power usage, if I count well 🙂

The following would be nice:

1/ Increase the use of GPU and SSD – both of these weren’t the bottle neck at any moment. Yeah, I get it that this is how currently the thing are – however, improvement would be great. I recall there was pro-software doing something like that on GPU but not sure about the name.

2/ Ambilight simulation – option to add the effect would sweet. I have a lot of movies in format other than 16:9, and that means either zoom (blah) or loss of ratio (blah!!),or – my usual choice – black borders.
I watched a movie using SVP with this ambilight effect and I like it – unlikely, my Openelec XBMC cannot simulate this effect (and I cannot connect my PC to my living room PC).
So – it would be nice if the movie good by given this “ambilight” effect, even it that would mean that the overall movie size would increase.

3/ Well, it could be a little easier, but it is not bad already 🙂

Cheers

TenFilip
excaliburn
August 4, 2014 at 5:39 am

I’m getting an error at line 153 and 57 for interframe2.avsi

Any ideas?
Maximus
August 4, 2014 at 6:06 am

I’m getting “not a valid win32 application” errors. What’s causing this?