InterFrame 2.8.2 (Updated 21 May 2015)


InterFrame is an AviSynth script.
Its main use is to give videos higher framerates like newer TVs do. Common names are framedoubling, smooth motion, HFR (high framerate) and 60FPS conversion.
High framerate (HFR at 48fps) was used in The Hobbit and will be used in upcoming films like the Avatar sequels, which will use HFR at 60fps, so why not watch all your movies at higher framerates?



Here is a before and after video comparison:
Original File
InterFrame (default settings with GPU=true)

Code Samples:

Here is a sample of what the AviSynth script could look like.
It shows the recommended syntax and should be used with SET’s AviSynth 2.6 build from here.

SetMTMode(3, Cores)
dss2("video.mkv", fps=23.976).ConvertToYV12()


Dependencies are included in the download.

To use it in your script just call the function InterFrame(Cores=x) (replacing the path with the path to the flow DLL files) and it will automatically choose a good framerate and preset for you.
There are more specifics like optional parameters and examples on this page, which is also included in the download.

There is also a complete guide on how to use it for those with no knowledge about any of this stuff here.
If you have any questions about it please check the guide first, there is a FAQ section and everything πŸ™‚


21/05/2015 – 2.8.2:

  • Updated to SVPflow 1.1.15, which increased speed (thanks, SVP!)

02/05/2015 – 2.8.1:

  • Updated to SVPflow 1.1.14, which increased speed by up to 15% (thanks, SVP!)

10/03/2015 –

  • Updated to SVPflow 1.1.13, which fixed the unused SVConvert function (thanks, SVP!)

05/03/2015 – 2.8.0:

  • Updated SVP libraries (thanks, SVP!) which:
    • Increased speed by up to 20%
    • Reduced memory usage
    • Removed 2 dependencies (from 4 to 2)
  • Updated documentation

03/01/2015 – 2.7.0:

  • Added “fastest” preset, for even more speed but lower quality.

09/09/2014 – 2.6.0:

  • Added new boolean option “FrameDouble”, which when set to “true” will always double the framerate of the input video, unless NewNum is greater than 0.
  • Updated the “Recommended” script in the documentation

11/05/2014 – 2.5.2:

  • Updated SVP libraries (thanks, SVP!) which:
    • Improved quality
    • Fixed bugs

16/12/2013 – 2.5.1:

  • Minor code cleanup
  • Updated SVP libraries (thanks, SVP!) which:
    • Improved quality
    • Improved GPU support
    • Fixed bugs

18/02/2013 – 2.5.0:

  • Minimized artifacts (thanks, Widezu69!)
  • Made motion smoother by default (only in GPU mode)
  • Updated libraries which improve scene-change detection, thanks to SVP

24/01/2013 – 2.4.0:

  • Updated libraries which improve scene-change detection, thanks to SVP

16/01/2013 – 2.4.0 RC1:

  • Fixed the presets Weak and Faster when not using GPU (thanks, Motenai Yoda!)
  • Fixed the Animation tuning (thanks, HolyWu!)

11/01/2013 – 2.4.0 Beta 1:

  • The “Medium” preset is back to what it was in 2.2.0
  • The “Fast” preset is the same as “Medium” was in 2.3.0
  • The new “Faster” preset is the same as “Fast” was in 2.3.0
  • The “Animation” tuning has been changed a lot based on SVP recommendations
  • The “Weak” tuning has been changed a lot based on widezu69’s recommendations
  • The “Smooth” tuning is smoother

24/12/2012 – 2.3.0:

  • Increased speed
  • Decreased blobs/artifacts in high-action scenes
  • Updated libraries which optimise memory use and support more video cards, thanks to SVP

13/11/2012 – 2.2.0:

  • Fixed a syntax bug that appears to have had little-to-no effect (thanks to HolyWu for reporting it).
  • Tweaked scene-change detection again (tightened this time to improve artifacts).

27/06/2012 – 2.1.0:

  • Improved smoothness in high-action scenes by loosening scene-change detection.

05/06/2012 – 2.0.2:

  • Better interpolation stability.
  • Supports more video cards.
  • Better compatibility with AviSynth 2.6.
  • Thanks to SVP.

05/05/2012 – 2.0.1:

  • Updated libraries to support new video cards like GTX 680, thanks to SVP.

03/05/2012 – 2.0:

  • Updated libraries, thanks to SVP.

17/04/2012 – 2.0 RC1:

  • Updated libraries, thanks to SVP.

12/04/2012 – 2.0b4:

  • Reduced instances of warping by fixing usage of SAD mask, thanks to Bernardd for reporting the bug.
  • Further reduced instances of warping by lowering area_sharp (sadgamma).

11/04/2012 – 2.0b3:

  • Updated libraries, thanks to SVP.
  • Changed some fields from string to int (NewNum, NewDen, OverrideAlgo and OverrideArea).

30/03/2012 – 2.0b2:

  • Updated libraries, thanks to SVP.
  • Fixed 3D modes.
  • Fixed “overlap must be even” error.

24/03/2012 – 2.0b1:

  • Rewrite which no longer uses MVTools2 and has better quality and is faster.

23/03/2012 – 1.14:

  • Allow any value for OverrideAlgo.
  • Lots of documentation updates.

29/02/2012 – 1.13:

  • Added the “OverrideAlgo” option for users who wants to override the recommended algo value.
  • Added the “OverrideSadML” option for users who wants to override the recommended sadml value.
  • Updated FFTW to 3.3.1 from 3.2.2.
  • Updated MVTools2 (SVP Build) to from, thanks to SVP.
  • Updated libflowgpu to 1.2.7 from 1.2.6, thanks to SVP.

31/12/2011 – 1.12.3:

  • Updated libflowgpu to 1.2.6 from 1.2.5 which improves ATI GPU compatibility, thanks to SVP.
  • Code reshuffle (no changes)

03/11/2011 – 1.12.2:

  • Updated MVTools2 (SVP Build) to from which improves speed by 2-15%, thanks to SVP.

16/09/2011 – 1.12.1:

  • Updated MVTools2 (SVP Build) to from which synchronises the build with the official beta release.
  • Updated libflowgpu to 1.2.5 from 1.2.0 which improves GPU compatibility, thanks to SVP.

12/09/2011 – 1.12:

  • Improved some warping.
  • Added new UltraSmooth tuning and changed the Smooth tuning. Smooth now has more error-correction than before, while UltraSmooth is roughly what Smooth was before.

05/07/2011 – 1.11:

  • Increased quality of all presets. This change makes fast panning less smooth, but also decreases errors in general.
  • Fixed bug with Placebo preset (thanks to Alek93j and Gavino).

18/06/2011 – 1.10:

  • Increased quality of all presets. Thanks to DeathTheSheep for collaborating.
  • Increased speed of “Ultra Fast” and “Super Fast” presets.
  • “Animation” tuning is now much better and recommended for cartoon/anime inputs.
  • What used to be the “Animation” tuning is now called “Weak”.

23/05/2011 – 1.9:

  • Added support for 2 more types of 3D inputs (Half-SBS and Half-Over-Under).

20/05/2011 – 1.8.1:

  • Fixed stuttering motion particularly visible in cartoons.

04/05/2011 – 1.8:

  • Improved support for 2 types of 3D content – SBS (Side-By-Side) and OU (Over-Under), AKA Top-to-Bottom. This new feature is controlled by the new parameter InputType.

30/04/2011 – 1.7.1:

  • Increased the speed by roughly 40%, thanks to SVP

28/04/2011 – 1.7:

  • Increased the quality of all presets

20/04/2011 – 1.6:

  • Updated libflowgpu from 1.1 to 1.2 which improves the quality of GPU=true mode, thanks to SVP
  • Added more presets (“Faster” and “Super Fast”) based on some realtime user’s suggestions, so now there is a smoother step between presets

13/04/2011 – 1.5.2:

  • Set GPU=false by default instead of true, because of slight quality loss with GPU=true

13/04/2011 – 1.5.1:

  • Fixed bug with GPU=false mode

11/04/2011 – 1.5:

  • Improved the quality of the default, Fast and Placebo presets
  • It now checks for the existence of the mandatory value for FlowPath and displays an alert if it isn’t defined
  • Added the GPU parameter (true for GPU-acceleration, false for CPU-only)

10/04/2011 – 1.4:

  • Added custom mvtools2 and GPU-acceleration thanks to SVP
  • Improved the quality of all presets
  • Updated the sample videos in this post

01/04/2011 – 1.3.1:

  • Added input validation for Tuning and Preset values with descriptive error messages

30/03/2011 – 1.3:

  • Added new Tuning value called Smooth
  • Improved detection of scene-changes

24/03/2011 – 1.2:

  • Renamed Fast preset to Ultra Fast
  • Added Very Fast and Fast presets
  • Increased quality of Placebo and Medium presets
  • Added Tuning variable
  • Improved detection of scene-changes
  • Added the file dependencies to the download since a couple of them were confusing some people
  • Added links to the dependency websites in the help file

22/03/2011 – 1.1:

  • Renamed Quality preset to Medium (default)
  • Renamed Speed preset to Fast
  • Increased quality of Medium (default) preset
  • Added Placebo preset (little quality gain with big performance hit, not recommended)
  • RemoveGrain is now required for Medium (default) preset
  • EEDI2 is required for Placebo preset

21/03/2011 – 1.0.2:

  • Increased speed of both presets

20/03/2011 – 1.0.1:

  • Slightly faster
  • Scene-changes no longer fade/blend

17/03/2011 – 1.0:

  • Initial release


  1. How can i configure the script for “placebo” preset, and about EEDI2

  2. SubJunk

    March 24, 2011 at 5:09 pm

    @Luiz: Hi πŸ™‚ Thanks for posting the comment here.
    In the 1.2 download I have added the dependencies, so all you need to do is download the new zip file and get EEDI2.dll from there and then include it in your script the same way as RemoveGrainSSE3.dll πŸ™‚
    Then to use the Placebo preset, or any other preset, you just use syntax like:
    Hope that helps

  3. Torsten Enderling

    April 4, 2011 at 3:02 am

    I’m not sure if I get the purpose of InterFrame correctly; are you using it standalone, or as an addition to PS3MS (seeing as you are a PS3MS coder). As this is an AviSynth script, is it possible (when using the AviSynth/MEncover transcoder in PS3MS) to configure PS3 Media Server to transcode into a higher framerate on the fly, or do you re-encode all your videos in advance?

    What would the script for PS3MS look like?

    Kind regards,

  4. SubJunk

    April 4, 2011 at 10:03 am

    @Torsten: It’s separate from PS3MS. I encode videos in advance πŸ™‚ PS3MS may support the feature at some stage, but not right now.

  5. @SubJunk

    Is it possible to make a quick and dirty Version with Ps3MS. Only with a on/off switch. I ask because i want to know if i saw a difference on my 50″ TV(witch and without “tv optimations”. Yeah i saw a differenz @ my 24″ isp Monitor, but how is it with sound and @Stream?!?.

    Yeah i ask you unhuman things, but hey you are a smart coder :D.


    and MEGA THANKS for PS3MS.

  6. SubJunk

    April 13, 2011 at 5:17 pm

    @Master: It is on my to-do list πŸ™‚ I don’t know when it will be done though πŸ™‚

  7. Thanks for creating such great tool, I always dislike the 25/30fps of my 5D Mark II as the pan motion is not smooth, now there seems to be a good solution. While playing with interframe, I found a problem clip, don’t know if it was my setting problem:

    While the org plays very smooth on my Panasonic PT-AE4000 frame insertion mode.

  8. SubJunk

    May 31, 2011 at 3:36 pm

    @C.H.Ling: You’re welcome, I’m glad you are enjoying it πŸ™‚ With regards to the clip, I assume you mean the glitch with the windows on the plane? To fix that, try using Tuning=”Animation” πŸ™‚

  9. Yeah! “Animation” works much better, thanks! I had tried “Smooth” but it didn’t work. Require more caution to look at the result to decide if alternate setting needed for future conversions.

  10. Guys-

    Thanks for your work with PS3 Media Server and Interframe as well. I’m having an issue with Interframe and I’m hoping you can help. I was following along with your instructions to configure everything and got to the point where I was about to begin encoding my video. However, after loading the video file in MeGUI, I receive an error that says something about not having the “SetMTMode” set in line 2 of the script. Obviously, since I copied/pasted the script you provided, it’s there.

    Here’s the script I’m trying to use:

    PluginPath = “C:\Program Files (x86)\MeGUI\tools\avisynth_plugin\”
    LoadPlugin(“C:\Program Files (x86)\Haali\MatroskaSplitter\avss.dll”)
    dss2(“I:\Videos\Paul (HD).mkv”, fps=23.976).AssumeFPS(24000,1001).ConvertToYV12()

    I tried to add the total number of processor threads (7) to the SetMTMode line – SetMTMode(2,7) as well as the GPU=true piece at the end – InterFrame(FlowPath=PluginPath, GPU=true) but they didn’t work due to same error. That’s when I decided to try the unchanged scripts you provided.

    Any idea why I’m getting this error?

    The only change I made to your instructions is that I downloaded the latest version of AVIsynth. Everything else was done as instructed.

    Thanks in advance for the help. Keep up the great work!

    ~ Sko

  11. SubJunk

    July 3, 2011 at 7:24 pm

    @Sko: Hi πŸ™‚ Your answer is in your question: You said “The only change I made to your instructions is that I downloaded the latest version of AVIsynth”, so please try it with the version that is included πŸ™‚ (which is the latest, by the way)

  12. @SubJunk-

    Thanks a bunch for your reply! I will try again – this time – using the version of AVIsynth you provided.

    With that said, unless I’m missing something, the version of AVIsynth you’re providing is now an older release. The title of the file in your download package is “AviSynth_090927.exe” and is version

    There is now an updated version available through AVIsynth’s Sourceforge website titled “AviSynth_110525.exe” and is version Therefore, the version in your download package is not the latest anymore. πŸ™‚

    The reason I used the more recent version is because I had downloaded/installed it literally just a couple days ago while trying to work with a few different versions of PS3 Media Server. I didn’t want to uninstall a newer version just to try your scripts.

    On a side note, shouldn’t the scripts work regardless of the version being used? Your notes didn’t indicate anything about them not working with other versions. You just said the 2.6 release was more stable and offered faster multithreading than the previous 2.5 releases. My perception is that the scripts should still work with other releases.

    Lastly, there’s a part missing from Step 9 of your walkthrough. After I load the video file (by clicking on the “…” button on the script creator screen), I’m presented with a pop-up window asking me to select one of 3 options/buttons – One Click Encoder, File Indexer or DirectShowSource.

    This pop-up window is not mentioned in your tutorial so, by trial and error, I ended up selecting the “DirectShowSource” option as it was the only one that would allow the video screen to open (as stated in your tutorial).

    Maybe I’m not selecting the right choice on this pop-up screen???

    Thanks again for your assistance. Your efforts to help are very much appreciated!

    I look forward to hearing from you again soon.

  13. SubJunk

    July 4, 2011 at 1:14 pm

    @Sko: The “latest” version you refer to has no multithreading support, so this is the latest build for users who want that.
    Without getting into too many details, the version included in this download was made by SET, who wrote his own multithreading patch for AviSynth that improves upon the official code. He has since gone inactive which is why it hasn’t been updated to the latest alpha release, but to my knowledge there was nothing great added in this year’s alpha.
    You can see the list of most available builds at the AviSynth Wiki at where ST means single-threaded and MT means multi-threaded. The one included in this download is the bottom one, “v.2.6 MT”, with a slight modification to the version information by me because SET forgot to add it.

    The scripts do work with most versions of AviSynth if you are willing to give up multithreading.

    You’re right about Step 9, that step was added to MeGUI recently and I haven’t got around to updating the guide. Thanks for reminding me πŸ™‚

  14. How can i use UltraSmooth tuning???

  15. SubJunk

    September 13, 2011 at 11:19 am

    @Luiz: Tuning=”UltraSmooth”

  16. Hello SubJunk!

    At first a big thanks for developing this fine script! It works great! I have converted some of my own movies and it is nice to see them in 50/60FPS without so many artefacts πŸ™‚

    I would like to make real slow slowmotions too. Have you some tips for me what i can change to optimize it for slowmotions? Or have you planned to add an preset for this?

    At the moment i use this in my own script, canΒ΄t find any better. And your script i donΒ΄t understand, its too complex for me at the moment πŸ˜€

    prefiltered = DeGrainMedian()
    super = MSuper(hpad=16, vpad=16, levels=1)
    superfilt = MSuper(prefiltered, hpad=16, vpad=16)
    backward_vec = MAnalyse(superfilt, overlap=8, isb = true, search=3,searchparam=4,blksize=16,dct=5)
    forward_vec = MAnalyse(superfilt, overlap=8, isb = false, search=3,searchparam=4,blksize=16,dct=5)
    forward_re = MRecalculate(super, forward_vec, blksize=8, thSAD=100)
    backward_re = MRecalculate(super, backward_vec, blksize=8, thSAD=100)
    forward_re2 = MRecalculate(super, forward_re, blksize=4, thSAD=100)
    backward_re2 = MRecalculate(super, backward_re, blksize=4, thSAD=100)
    MFlowFps(super, backward_re2, forward_re2, num=SlowFPS,den=100, blend=false)

  17. SubJunk

    October 26, 2011 at 12:16 pm

    @S3NS3: I think InterFrame will work well for slow motion if you just run:

    AssumeFPS(half framerate)

  18. Yes, i tried it this way but the results donΒ΄t look good as the short script above!
    I have used the smooth preset, slowdown to 100FPS-200FPS, and the frames mostly blend instead of interpolate on my clips.

    At the “normal use” to double the framerate your script really works great – and fast too πŸ™‚
    So i assumed that i should alter some internal parameter to optimize it more for slowmotion where i see much more interpolatet frames instead of real ones?

    I will try it again with different presets!

    Thanks for input! πŸ™‚

  19. I converted a few videos and some of them of them suffer from bad analog to digital conversion (telecine warp) and some frames are doubled. Example:
    Normally it is not so noticeable but after conversion it looks really bad. Would you like to add to Interframe parameter and function to deal with such videos? Here is script to that which would be helpful:

  20. SubJunk

    November 15, 2011 at 11:12 am

    @dzid: I have considered adding extra things like that to InterFrame but in the end I decided it’s best that people clean the videos before using InterFrame.
    By the way, do you use InterFrame for the conversions on your high framerate blog?

  21. The reason I’ve asked about that particular function is that removing telecine warp is strictly related to frame interpolation. Integrating it with interframe won’t cause such many additional calculation as calculating it separately. Now I don’t have even idea how to do it so I stick with your concept.

    Yes, I use InterFrame. Right now I am working on gui for Interframe/x264/mkvmerge to automate process of conversion. I am doing this for my friends now. I also would like idea of sharing converted movies to be legal..

  22. SubJunk

    November 15, 2011 at 2:32 pm

    @dzid_: Cool blog, I might write a post about it πŸ™‚
    P.S. I recommend using WEB-DL releases instead of HDTV releases. The web ones are better quality and have no logos in the corner. For example, for Castle S04E08 there is Castle.S04E08.720p.WEB-DL.DD5.1.H.264-NFHD

  23. Of course, you can write about it.
    After four nights I’ve made a very beta of InterFrameGUI. It has limited functionality now but it is already more automated than MeGUI. I need probably a few more nights to make it more usable.

  24. Hi SubJunk,

    I really love your filter.
    I want to use this filter in the post production workflow of footage from canon dslr.
    Yesterday I posted this teaser that explains what we do.

    Now we use interframe to interpolate missing frames. like this:
    A = FFVideoSource(“RAW.MOV”)
    A = ConvertToRGB(A, matrix=”PC.601″, interlaced=false)
    A = Converttoyv12(A) # convert to yv12 needed for Interframe
    A = selecteven(A) # select even or odd frames and interpolate them
    A = assumefps(A, 25) # Interframe doesn’t work with 12,5 fps
    A = InterFrame(A, NewNum=50, NewDen=1, GPU=false, FlowPath=”C:\Program Files\AviSynth 2.5\plugins\”)
    A = assumefps(A, 25)
    A = trim(A, 1, 0)
    A = ConvertToRGB(A)
    A = ImageWriter(A, “frames\A%07d.jpg”, type = “jpg”)

    B = FFVideoSource(“RAW.MOV”)
    B = ConvertToRGB(B, matrix=”PC.601″, interlaced=false)
    B = Converttoyv12(B) # convert to yv12 needed for Interframe
    B = selectodd(B) # select even or odd frames and interpolate them
    B = assumefps(B, 25) # Interframe doesn’t work with 12,5 fps
    B = InterFrame(B, NewNum=50, NewDen=1, GPU=false, FlowPath=”C:\Program Files\AviSynth 2.5\plugins\”)
    B = assumefps(B, 25)
    B = ConvertToRGB(B)
    B = ImageWriter(B, “frames\B%07d.jpg”, type = “jpg”)

    return Interleave(A,B)

    So now interframe interpolates the missing frames from separate even and odd streams.
    What would be great is that interframe would use the motionfactors from the opposite frame and tries to recreate that frame as good as possible. I think it could improve quality a lot! Especially on locating walking leg positions or stuff like that.

    Please tell me your thoughts on this.
    Bart van den Boogaard

  25. SubJunk

    December 23, 2011 at 11:19 am

    @Bart, it looks great.
    Your suggestion is good and it has been developed, along with other upcoming improvements. It is in the private beta stage right now and will be supported in InterFrame 2.0.
    I guess it will be ready in a month – or two considering the busy time of year.
    Feel free to link back to this blog anywhere you want, traffic is nice πŸ™‚

  26. That is so great, thanks. Can you email me so we can discuss the possibilities?

    Bart van den Boogaard

  27. wow thats great! any thoughts to make that private beta a little less private?
    either way, thank you very much.

  28. Hello,

    I tried Interframe and it is very interesting plugin for AviSynth. Especially I like stereoscopic options you added as well. However, do you have any guidelines what is the type of footage is useful for increasing framerate? My first test was on the following clip (inside zip file is original and increased fps footage):
    However, the result is not as good as expected (when checked frame-by-frame). Namely, I would use Interframe for decreasing the speed of the footage. I suppose that moving violin bow is not the best case for Interframe, is it? Or maybe I made some wrong settings
    (InterFrame(Preset=”Placebo”, NewNum=48000, NewDen=1001, FlowPath=”C:\Program Files (x86)\AviSynth 2.5\plugins\”)).
    I tried it on one very slow pan as well and the result was much better.

  29. SubJunk

    February 15, 2012 at 7:59 am

    @Damir: Yes, panning performs much better than thin, moving things. A lot depends on contrast, like if the moving thing is similar to its background InterFrame will make more mistakes than if it is different to its background.

  30. Just one more question… Is it possible to make a version if Interframe which resuts in the same frame-rate, but which introduces the same time-shift regarding to the original footage? Namely, if we have 25FPS clip long 100 frames, I would like to get 25FPS clip also 100 frames long. However, each resulting frame should be e.g. 5ms “forward” than the corresponding frame in the original clip.

    I suppose that this should not be very difficult, since Interframe should alreadyc do that by finding in-between frames at different positions if output frame rate is not exactly 2-times the input frame rate. However, such solution could be highly appreciated in stereoscopic community where one of the clips should be partially shifted in time in order to make synchronous 3D clips. Of course, in this case quality of transformation should be very high. Maybe there are already some avs scripts available??

  31. some posts ago Bart suggested that interframe could use the motionfactors from the opposite frame to recreate that frame as good as possible. that would really help the HDR functionality of magic lantern.

    and you answered that his suggestion is good and it has been developed and will be available in version 2

    i havent found anything about it.
    how could one access this functionality?

  32. How would I use Interframe to tell it to insert a new frame every 6 frames or so. I used the cinema mode on my sony dcr-pc1000 and it skips a frame every 6 frames or so.

  33. SubJunk

    May 7, 2012 at 10:14 pm

    @Elliot: That probably means your camera recorded the video at 29.97fps but with only 23.976fps actual frames (1 in 5). If that’s the case InterFrame isn’t the right tool, but it’s a very common thing for AviSynth to do, just Google AviSynth tdecimate

  34. @SubJunk: What I noticed is when I view the 2 fields, the motion stops in one at frame 5 for example, picks up on 1 frame in field 2 and catches up to field 1, and than you have another 5 frames. I read that my video is a hybrid mixed progressive and interlaced frames or something, its wierd. I used this script in avisynth, but the frames blend together, I thought the motion would be smooth since their is motion in the other field.

    LoadPlugin(“C:\Program Files (x86)\AviSynth 2.5\plugins\decomb.dll”)


  35. Hi,

    First, thanks to SubJunk for providing a great tools. I am a newbie πŸ˜€ and I have tried to converting an mkv file using the following script.

    PluginPath = “C:\Program Files (x86)\MeGUI\tools\avisynth_plugin\”
    LoadPlugin(“C:\Program Files (x86)\K-Lite Codec Pack\Filters\Haali\avss.dll”)
    dss2(“D:\HD-Samples\The.Dark.Knight.2008.1080-001.mkv”, fps=23.976).AssumeFPS(24000,1001).ConvertToYV12()
    InterFrame(GPU=true, Cores=15, Tuning=”Smooth”)

    It gave me conversion rate around 23 fps. I am using i7-2700K, 4GB Ram, Win7 64. Is it fast enough or is there any parameter to speed up conversion process?



  36. Hi SubJunk,

    Great to have a new release. Do you remember my request for DSLR hdr video? With two exposures altering eachother every frame. I can’t find the setting which recreates the image of the opposite stream. Can you look into that?


  37. SubJunk

    May 16, 2012 at 5:54 pm

    @Bart: Sorry for not replying sooner, I had misunderstood your original request. There are no plans to make that feature in InterFrame, sorry for the mislead!

  38. Hi SubJunk,

    According to,_params_string%29 , bad:{sad:2000} should be enclosed in coarse:{}, but you enclosed it in search:{}. I think that should be wrong?

  39. @Holy: It looks like you’re right. Having said that though, I compared the current version with a fixed one and I couldn’t find any scenes that were affected, so it seems to have very little effect. I will release an updated version soon, thanks!

  40. Hey all!

    I love this program, have converted a couple videos lately to show friends and family what is coming down the pike.

    Question I have is that some of the videos I try to convert seem to hit a specific frame and then just stop, cpu stops crunching and nothing happens regardless of how long I leave it. This is the case with a few mp4, and a few other extensions. Is there anything I can run the file through to ‘fix’ what ails it at that frame? Thanks for any feedback,

    Appreciate all the hard work into the program.


  41. @Jason: Glad you like it πŸ™‚ I’ve had the issue sometimes with MP4s too, and usually it’s a codec problem. I suggest uninstalling all codec-related programs from your computer, restarting it, then installing the latest K-Lite Mega Codec Pack (not the 64-bit version). That has fixed it for some users.

  42. @SubJunk – followed your suggestion, and also started the script over from the one you post with the new Interframe and all is working like a champ! I converted an animation short before, went live action tv this time, and the natural shaky cam they use sure is accentuated, takes a bit to get used to it, but I love it. Looking forward to seeing the Hobbit in 48fps. Thanks again for the help.


  43. Hello
    I have tried everything and read all the comments but i still get this error
    InterFrame(“C:\Program Files (x86)\AviSynth 2.6\plugins\”
    and i get the same error = Interframe does not have a name argument “flowpath”
    i have tried with all avisynth versions including the mt ones. flowpath and OverrideArea are the only commands megui has problem reading. and i have the latest version of interframe.
    any suggestions?

  44. @Ramon: FlowPath is an old command that is no longer used. See the Code Samples section of the article πŸ™‚

  45. Easy way to use your own avisynth script in either UMS or PMS, for Avisynth/Mencoder that is, you’ll have to go to expert settings for Mencoder and add following line: vcodec == h264 :: -ofps 60000/1001

    You can also use encoder, and ofc change the frame ratio to whatever you need to. The regular interframe script provided with UMS gives incredible lag and is just unwatchable, so I have to use my own custom optimized script which works flawleslly on my comp, so just some advice if you’re looking to do it on your own. You can also use Avisynth/FFMPEG(which I found much more stable, and can also use subtitles with Haali) custom interframe script, but you’ll need to edit SubJunk’s source code in there, and add your own.

    Anyways, I also wanna give a big thank you to SubJunk for his great work on the Interframe script as well as UMS.

    Also, for anyone wondering what my optimized script is, I’ll post it here, note you’ll likely have to tinker with it for your own comp, I used MPlayer Classic to test out various configurations, this script has no lag and no a/v desync on my comp while live streaming, and it’s a pretty old comp, OC’d Q6600 + GTX260:


    InterFrame(Cores=4, GPU=true,NewNum=60000,NewDen=1001)
    GetMTMode(false) > 0 ? distributor() : last

  46. SubJunk

    January 14, 2013 at 9:21 am

    @Dnice: That script is no different to the one UMS uses…?

  47. Well you may notice the Import and LoadPlugin functions are omitted, and from my reading about avisynth scripts, if you include them in the AVS script as it was within UMS, they keep getting reloaded while the script is processing. That omission + having SetMTMode(3,12) rather than SetMTMode(3, CPU#) was enough to make all the difference. From being unable to play videos interframed in realtime, to being even able to add on additional filters such as sharpeners.

    Just trying to show what people may consider to be an insignificant change, how great of a performance difference it’s made.

  48. Hello, i’m experimenting with interframe plugin, this is a really cool piece of software for restoring some old 15 fps movies taken with very old cameras.
    There is only a thing that i cannot understand: the output movie (i’m not working realtime, i’m recoding the files for later use) has a different gamma, like a little exagerated contrast, say like some “tehatre” effect that comes with some graphics drivers. I don’t understand if it is due to my pc configuration or to the color conversion that is needed to work with interframe. My movies are 1024×768 avi from old canon powershot, my graphics device is an ATI mobile radeon 5xxx series. I’d like to only have frames doubled but not image correctins. Any hint? Than you! Umberto

  49. SubJunk

    January 21, 2013 at 4:19 pm

    @Umberto: I haven’t seen this issue before, but it may be related to your codecs. Try uninstalling all codecs and installing K-Lite Mega (no 64-bit versions)

  50. @SubJunk: I think i fixed my issue adding a ColorYUV(levels=”PC->TV”) to the script directly after the YUV color conversion. Playing both files side by side doesn’t show any noticeable detail loss and the luma matches the original movie. Moreover i noticed that using InterFrame twice i obtain a really good 60 FPS from a bare 15 FPS that is a joy to watch at! You deserved my (small) donation. Thank you!

Leave a Reply

Your email address will not be published. Required fields are marked *

© 2023 Spirton

Theme by Anders NorénUp ↑