Search options (Page 3 of 24)

Thank you

SVP Pro won't do offline conversion and encoding. You need to follow guides explaining the process with Avisynth.

You'll also get better quality by using FrameRateConverter although it will be much slower.

Easiest way is to run it through my Yin Media Encoder (part of the Natural Grounding Player package) and it will do everything automatically. I'm working on a new version that converts using FrameRateConverter but that's not yet released.

How much do you offer? I could run your video through it and send you the output if it's worth it, but if it's $20 and would take 1 day of computer processing, that wouldn't be worth it.

In theory, SVP should produce the same results as Avisynth MvTools. In practice, there are more blurs and ghost effects due to a nasty bug somewhere.

This has been discussed in-depth here.

Sure

I don't really have 20+ mbit videos, but I have this

function SVP(clip Input) {
    SuperString = "{scale:{up:0,down:4},gpu:1,rc:false}"
    VectorsString = "{block:{w:8,overlap:2},main:{search:{distance:2,coarse:{satd:false,distance:2}},penalty:{lambda:20.0}},refine:[{thsad:100}]}"
    SmoothString= "{gpuid:11,rate:{num:2,den:1,abs:false},algo:23}"
    Super   = SVSuper(Input, SuperString)
    Vectors = SVAnalyse(Super, VectorsString)
    smooth_video = SVSmoothFps(Input, Super, Vectors, SmoothString, url="www.svp-team.com", mt=1)
    smooth_video
}

FrameRateConverter()

I have a i7 quad-core in my laptop. It does the job fine.

Click "Preview in MPC-HC" and you'll see the error message in the player. It generates "NaturalGrounding\Temp\Preview.avs". Something else you can try is run AVSMeter.exe utility on that script file. it will check if there are dependencies missing.

avsmeter.exe preview.avs

This should be easy enough to add; I just don't want to make the UI more complex. If ffmpeg supports xvid and vp8, then why not.

Wrong. You can change it yourself. Click on the Script tab and edit the Interframe parameter to the desired values. The UI does the best in the most simple way, and then you can customize the script for anything the UI doesn't do automatically.

ffmpeg parameters are different though; that's fully managed by the code so it has to expose the options. But then if I allow XVid and VP8, I need to allow additional container formats, so it adds to the complexity or I need to redesign the whole section. Then there are lots of other encoding options I'm not exposing -- so I have to decide what level of complexity I want to expose to the user.

Same as above.

Thanks

hum...

If you look at the script difference between the two, there are huge differences between both versions that impact the quality. The next version will have further changes that will considerably improve frame interpolation results.

I haven't figured out what's wrong with SVP, but this script has HUGE improvements over SVP.
https://forum.doom9.org/showthread.php? … ost1804515

Chainik, you might want to investigate this. You might have overlooked a setting that is considerably lowering the quality.

.. but as you say, finding it might not be so easy.

Chainik, back to that thread on Doom9, how would I go about applying the same settings? SVP and MvTools have a completely different syntax, I can't easily switch between one and the other.

I did comparison here. Very notable quality improvement.
https://forum.doom9.org/showthread.php? … ost1802157