Sections:
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
February 26, 2011 at 9:27 am
I cant check “Prefer DSS2 over DirectShowSource” in extra setup tab ://
any idea why?
February 26, 2011 at 10:31 am
@ondrejw: Please check the FAQ section 🙂
March 4, 2011 at 9:00 am
Ok, thanks SubJunk, I have converted my first video and I have to say, the difference is huge!!
Anyway, may I ask one more thing, when choosing quality convert, where I can chose 16-26, I take 16- best quality, but there is one more option down there called Presets, where I also can chose from faster to placebo – what exactly is this?
Thanks again .)
March 4, 2011 at 9:31 am
@ondrejw: Glad you like it! 🙂
That slider balances 2 things: encoding speed and filesize.
So the video will look the same at any slider setting, but the “fast” settings will encode more quickly but produce larger files, while the “slow” and placebo settings will encode slower but produce smaller files.
March 4, 2011 at 9:52 am
Again, thank you!
I go try some very slow or placebo preset, so I can tell you like in week or such :)) haha
regards
Ondrej
March 7, 2011 at 1:41 pm
Nice Guide but i have some remarks and questions.
First, i cant get MT to work on Windows x64, Avisynth simply crashes. However, the script works in single threaded mode.
Further, i tried to gather the dlls for the 64 bit version of avisynth but failed as the x64 FFTW dll is not accepted by mvtools. I appreciate if anyone can post all DLLs for a working 64 bit avisynth version in case someone gets it working. The x64 version of x264 and Avisynth is simply faster ;-). Most people who do serious encoding use a 64 bit OS anyways.
Next questions is the difference between 60 FPS and 6000/1001 FPS assuming i have 23.976 FPS as input. Shouldn’t pure 60FPS work for 23.976 FPS input as well or is there a catch? . As far as i can see, MVTools simply speeds up the movie to the desired frame rate in the last step of the script.
Last, id like to ask if anyone knows a good codec that handles extreme input as well. Right now i managed to encode a 5 min sample with 3840×1080@60 FPS in x264 and it stutters at some points….
March 7, 2011 at 2:33 pm
@ondrejq: Hahaha 🙂
@lenny: I don’t recommend using a fully 64-bit installation since the quality can suffer and the development lags behind the 32-bit versions. The fact is that many of the great developers are on ancient computers so it often falls to a third party to make things 64-bit, and sometimes they make mistakes that makes the 64-bit version inferior to the 32-bit one.
There is however an option to use the 64-bit version of x264 in the 32-bit MeGUI, it’s in the program options. I use it and it works well.
Using 59.94FPS instead of 60FPS – using a divisible framerate – allows for less artifacts. If you use a non-divisible framerate like 60FPS it never fully lines up.
The x264 settings can be tweaked for faster decoding. You can use the built-in “Tuning” for “Fast Decode”, or go even further by going into the advanced settings and changing the relevant settings manually (trellis, b-frames, etc)
March 10, 2011 at 5:49 am
I converted another video, but there are no subtitles :/
I know where I can add external subt. but when subt. are included in original video, they didnt convert :/
March 10, 2011 at 7:53 am
Subjunk
I wonder why in some very moving scenes occurs in a blur
contour images. Some seem a kind of ghost. Thank you and congratulations
sript quality.
March 10, 2011 at 10:05 am
@ondrejw: Hi ondrejw 🙂 You can use MKVMerge to mux subtitles into the new file. It’s almost never a good idea to convert subtitles into the actual video track 🙂
@Christiano: Hi Christiano 🙂 Sometimes that just happens. We are always working on ways to improve it but the process can never be perfect 🙂
March 10, 2011 at 7:41 pm
ok, thanks again SubJunk!
March 14, 2011 at 12:40 pm
Thank you very much for your work. Just keep it up.
March 14, 2011 at 12:42 pm
@ondrejw: Cool, hope you got it working 🙂
@Binh Le: Thanks! 😀
March 17, 2011 at 9:44 pm
Absolutely awesome script. Been using it on a lot of music videos and I can’t stand watching the originals anymore, haha.
A couple of questions:
Firstly, does the script affect the way audio should be synced ? I noticed that some videos are synced fine but there’s quite a number of videos where I have to pull the audio forward by around 400 milliseconds (or around that ballpark) to sync it correctly with the converted video.
Secondly, a few of videos that I’ve converted for some reason have 2 solid green frames inserted at the start of the video. The MeGUI preview never shows these green frames – they only show up on the actual encode. So far I’ve been adding Trim(2,0) for all my encodes to deal with it. I don’t know exactly how the script works, but I’m assuming it’s attempting to compare the first frame with a nonexistent previous frame thus creating this anomaly.
March 17, 2011 at 9:55 pm
@JaeCee: I’m glad you like it, I know what you mean about not being able to watch the originals! 🙂
1) The script shouldn’t affect audio sync except for variable-framerate content. Maybe the container specified an audio offset but MeGUI didn’t detect it.
2) I think it’s a codec thing. I’ve seen it before, too, but I think it goes away after restarting the computer? It doesn’t seem consistent, anyway.
March 17, 2011 at 10:33 pm
Mm .. I figured as much. Was trying to put the avi source through programs like AVIcodec to try and look for an offset variable or whatnot but no luck so far.
I encoded a particular video a couple of times and the green frames appeared every time, so I’m thinking it’s only on specific videos. At any rate, adding Trim(2,0) to the template makes sure they never come up (and 2 frames is pretty negligible).
March 18, 2011 at 9:32 am
This is an incredible script! I tried it once and got a weird rainbow thing going on the video, probably an apsect ratio thing, but I trashed that video after not really wanting it. All the others I’ve done are just amazing. It’s like going from a prime time drama style “film” look to almost like watching live TV.
Thanks for posting this as I had seen one or two vids on the web that were 60fps and I always wondered how they did it. My next test will be to use an AVS script that makes like a fake 3D using any video, and then running that output through this one. Should prove interesting.
Thanks again!
March 18, 2011 at 10:00 am
@Casshern: Thanks for the feedback, I really appreciate it 🙂
March 18, 2011 at 3:04 pm
Can you believe that all of a sudden none of the mp4 files I throw at MeGUI work? Get the unable to render error. Even the ones I already did. Any ideas? Tried rebooting.
March 18, 2011 at 3:23 pm
@Casshern: It sounds like a codec problem. Try uninstalling any codecs and installing the latest K-Lite. Sometimes the codecs screw themselves up and need to be reinstalled, never understood why myself but it works
March 18, 2011 at 4:01 pm
SubJunk, that was it. Thanks. I’m in IT…my boss is always saying…”I hate computers” LOL Just one of those things, huh?
March 18, 2011 at 6:15 pm
Can i use “add pre-rendering job” function??? this improve the video quality right….
March 18, 2011 at 6:27 pm
@Casshern: Yup exactly man! Mysterious things sometimes 😉
@Luiz: You can use it, but it won’t increase quality if you are using CRF mode 🙂
March 20, 2011 at 7:31 pm
just wow…every single WMV file gets stuck at the very end. Guess I’ll encode to 264 before before applying this script. 🙁
Other than that, I’m all crazy about it. 🙂
March 22, 2011 at 4:18 am
SUBJUNKE: Good day! When comparing the quality of the video with the original cast, I noticed that the original has more definition images. The cast seems to get blurred. Another thing: in the beginning there was no ghost in the contour of the images is now much more visible. what could it be? thanks
March 23, 2011 at 6:30 am
Avisynt script error:
RemoveGrain: Only Planar color space are supported
(C:\Program File\MeGUI\tools\Avisynth_plugin\Interframe.avsi. line 26)
How to solve?
thanks
March 23, 2011 at 8:23 am
Following Step 1:
Then extract the tools folder over the top of your MeGUI tools folder, which for most people will be C:\Program Files\MeGUI\tools\.
I don’t have MeGUI tools folder in the first place. What should I do then?
March 23, 2011 at 9:18 am
@Casshern: Hey 🙂 I’ve had that before, too. It’s a codec thing 🙁 Usually with those things, reinstalling codec packs (restarting the computer between each step) fixes them.
@Christiano: Hi 🙂 First, if the original is sharper you can try using a lower CRF number. CRF 14 is almost lossless.
Secondly, try moving the last line “ConvertToYV12()” to after the resize line (before the InterFrame() line)
@Jun Long: Welcome 🙂 If you run MeGUI the folder should be created
March 23, 2011 at 9:30 am
AviSynth script error: Load Plugin: Unable to load “C:\Program Files\MeGUI\tools\avisynth_plugin\mvtools2.dll”
It came out after pressing the save button in Step 9.
Can anyone help me with this?
March 23, 2011 at 9:33 am
@SubJunk: Thanks for replying me so quickly. I’ve created the MeGUI folder and had some problems with Step 9. Please help me with it. Thank you. 🙁
March 23, 2011 at 9:36 am
@SubJunk: I’ve already did the following step:
“Then extract the tools folder over the top of your MeGUI tools folder, which for most people will be C:\Program Files\MeGUI\tools\.”
But somehow there still seemed to be some problems.
March 23, 2011 at 10:18 am
I liked to use placebo preset, but how can i configure the script and about EEID2.
Thanks in advance
March 23, 2011 at 10:21 am
@Jun: Are you running a 64-bit operating system? Did you check C:\Program Files (x86)\MeGUI…?
@Luiz: Please comment in the InterFrame post, since the Placebo setting isn’t used in this guide 🙂
March 23, 2011 at 3:33 pm
SubJunk, no doubt about the codec thing. Another funny thing, when I load an mp4 or avi I sometimes get a white form and then MeGUI crashes. But if I load an MKV and then an AVI or mp4 it works. odd but I get to encode! 🙂
Also, on some videos that are 852×480 (avi) I get that rainbow effect in the video. Any ideas?
Thanks again for what you’ve done here. It is universally appreciated!
March 23, 2011 at 5:40 pm
@SubJunk: Yes. I’m running a 64-bit operating system. I’ve put the files inside Program Files(x86) already but it cannot work though..
March 23, 2011 at 5:52 pm
@SubJunk: Oh, I found out the problem. I had to change the script to suit the file directory of MeGUI. Thanks! I think I solved the problems for now. Trying to convert to first. 🙂
March 23, 2011 at 6:33 pm
@Casshern: That’s really strange! I hate to sound like a broken record, but they all seem like codec-pack related problems. If you use K-Lite, look in the start menu and choose the Codec Tweak Tool in the K-Lite Codec Pack folder. That will show some options and maybe you can change the default settings for those problem containers to see if it fixes them.
There are also other codec packs that might have better default settings (I don’t know but it’s worth a try), like Vista Codec Package (they also do a Windows 7 variant), then there’s CCCP, etc.
Sorry for the non-specific answer but whenever I try to figure out codec packs I just become more confused than when I started so I usually just switch to another pack 😉
@Jun: I’m glad you figured it out in the end 🙂
Maybe you can help me make the guide more usable. I had tried to include that information in Step 6 below the scripts, do you think I should use different words, or make that part bold, or any other suggestion?
March 23, 2011 at 6:40 pm
@SubJunk: It seemed that I forgot to look at that after copying the script. Maybe you could type out another set of codes with (x86) there for us to look at. Btw, it stucked at 99.41% for a long time. 🙁 What should I do?
March 23, 2011 at 6:56 pm
@Jun: Was the source a .wmv file? It so, then you have the same problem as Casshern. My last reply to him might be useful for you, too.
March 23, 2011 at 7:00 pm
@SubJunk: Nope, it was a mp4 file.
March 23, 2011 at 7:29 pm
@Jun: It is a codec problem
March 23, 2011 at 7:37 pm
@SubJunk: Hmm, what should I do then? I’ve installed K-Lite Codec Pack already before that.
March 24, 2011 at 4:00 pm
@Jun: You could try looking for codec support forums since I don’t know how to fix it; it is a problem that is outside the scope of this guide
March 25, 2011 at 10:29 am
Nice to see some real progress !
However, i still haven’t solved out my MT issues. The most recent Avisynth version further breaks 3d playback and crashes after 2 minutes at 60fps playback, so i stick to AS 2.5 ST for now. I guess nobody else tried full HD 3D playback at 60 FPS yet?
I further wrote a small Python script to iteratively encode small parts of my projects to be less effected by errors and to be more flexible with my PC usage. It also allows parallel encodes so Avisynth ST is no issue after all. Some encodes apparently take weeks…
March 25, 2011 at 12:07 pm
@Lenny: I haven’t tried it with 3D content so I don’t know for sure.
Often crashes can be fixed by changing the value of SetMemoryMax. Try values between 500 and 1000 to see if that helps.
March 25, 2011 at 2:00 pm
@Sunjunk
I’m not even sure if SetMemoryMax is required in AV 2.5 as my script works fine without it and 8GB RAM should be sufficient.
My problem is actually 60FPS playback. I encode a 3D movie into 2 full HD Streams, one for each eye. For playback i use avisynths stackhorizontal operation to create a single uncompressed stream for my 3d player. The catch is actually the decoding as you need a decent PC to decode a full HD movie at 60 FPS and at least twice the power for 3d. To my knowledge there is no hardware accelerated codec yet, so it all comes to raw processing power.
Right now i encoded the first 10 minutes of Avatar and noticed some strange artifacts when the shuttle flies trough the clouds. However, these rare and extreme movement sceens are hard to interpolate.
Keep up the good work!!!
March 26, 2011 at 7:43 pm
I just tested out this script and wow, what a big difference. There’s no more judder in my videos. Everything is silky smooth. Not as smooth as the 120/240 Hz stuff (because it’s only 60 FPS), but I wasn’t going to give up my plasma for an LCD/LED to get it’s motion interpolation. Not to mention, the Infinite Blacks and 5M:1 contrast ratio on the Panasonic G25.
For me 60 FPS is enough to get rid of pretty much all the judder. Having a LCD/LED with 120 Hz+ would be overkill. Figured there has to be another way.
Well, this seems to be the solution I’ve been looking for for the past year or so.
Thanks SubJunk for this wonderful script. It really helped me out.
March 26, 2011 at 11:02 pm
@Jeff: Thanks a lot for the feedback, it has made my night! 🙂
March 27, 2011 at 3:56 pm
@ SubJunk
Still haven’t decided on a good setting though. I’ve tried CRF 16 @ medium, but I had some compression artifacts occasionally. I know this thing goes as low as placebo, but I have a lot of stuff to do. Placebo would probably be overkill. Would you think slower is good enough to get rid of most of the artifacts? Say CRF 18 with the slower preset? I have a Sandy Bridge based Core i7 2600K, so I have the power for those extra settings.
March 27, 2011 at 4:58 pm
@Jeff: The x264 Presets slider doesn’t affect quality; CRF 16 @ Ultra Fast is the same quality as CRF 16 @ Placebo.
The CRF value is the quality, and the Preset is the speed of the encoding and the filesize.
So to increase quality just lower the CRF value. CRF 14 is practically lossless.