Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules.

 Doom9's Forum working to get the most out of SVPFlow (getting rid of smudginess)
 Register FAQ Calendar Search Today's Posts Mark Forums Read

 18th January 2018, 15:36 #1  |  Link a1s2d3f4 Registered User   Join Date: Nov 2010 Posts: 72 working to get the most out of SVPFlow (getting rid of smudginess) (This is posted already on the SVP-team forum, but it's not very active there.) I have used MVTools for 7 years converting PAL or 24fps videos to 60fps. I use AVISynth with VirtualDub My MVTools part of the script would go something like this: Code: ```#currently I have PAL 25fps video as my last operation num_frames = 12 super = MSuper(pel=2) backward_vec = MAnalyse(super, overlap = 4, isb = true, search = 3) forward_vec = MAnalyse(super, overlap = 4, isb = false, search = 3) v100=MFlowFps(super, backward_vec, forward_vec, num = num_frames * FramerateNumerator(last), den = FramerateDenominator(last)) v200 = ConvertToY8(v100).AssumeFPS(300).ChangeFPS(60)``` Now, with SVPFlow, I have: Code: ```num_frames = 12 super = SVSuper("{pel: 2, gpu: 1}") vectors = SVAnalyse(super, "{overlap: 4}") forward_vec = SVConvert(vectors, false) backward_vec = SVConvert(vectors, true) super_mv = MSuper(pel=2, hpad=0, vpad=0) #padding should be zero here! v100 = MFlowFps(super_mv, backward_vec, forward_vec, num = num_frames * FramerateNumerator(last), den = FramerateDenominator(last)) v200 = ConvertToY8(v100).AssumeFPS(300).ChangeFPS(60)``` I can already see the improvement: mvtools: https://drive.google.com/file/d/1mX4...ew?usp=sharing SVPFlow: https://drive.google.com/file/d/1qdk...ew?usp=sharing What I am wondering about is can I do something else to further improve the "smudginess"? I am including the original frames from the 25fps footage between which the interpolation occurs. I wish there was a way to get the interpolation algorithm to recognize the non-moving background (piano keys) and the moving object - hand. https://drive.google.com/file/d/12_w...ew?usp=sharing https://drive.google.com/file/d/1nT3...ew?usp=sharing Speed is not an issue as I export to a separate file and can let the computer sit overnight if necessary.
18th January 2018, 16:57   #2  |  Link
hello_hello
Registered User

Join Date: Mar 2011
Posts: 4,473
Quote:
 Originally Posted by a1s2d3f4 I wish there was a way to get the interpolation algorithm to recognize the non-moving background (piano keys) and the moving object - hand.
That sounds like the holy grail of frame interpolation.

This isn't perfect, but based on my limited experience, it's generally better.
FrameRateConverter

PS You probably should use it with these versions if you're not using them already:
https://github.com/pinterf/mvtools/releases

Last edited by hello_hello; 18th January 2018 at 17:16.

 19th January 2018, 14:27 #4  |  Link a1s2d3f4 Registered User   Join Date: Nov 2010 Posts: 72 Cool. Lots of reading. Hopefully, I can find some time over the weekend to read and try applying. @johnmeyer Yes, I agree that if I figured out a way to use these "block sizes" correctly (I am a bit slow, and even though I have read through MVTools website, I haven't figured out what to do with all the parameters) things would improve. Thanks for the replies.