You are not logged in. Please login or register.
SmoothVideo Project → Posts by Mystery
I did comparison here. Very notable quality improvement.
https://forum.doom9.org/showthread.php? … ost1802157
He's talking about the "Natural Grounding Player" which somewhat simplified converting videos to 60fps, but it's CPU only. Further, much like the AviSynth guide, it doesn't work in Windows 10.
By default it enables GPU if madVR is activated under the Natural Grounding Player's settings -- this definitely should be changed, especially now that the media encoder is a separate app.
Without knowing this, you can custom-edit your script to add the GPU parameter.
And yes it works under Windows 10. I'm aware however that some x86 Visual C++ dependencies aren't currently being installed during setup, this will be fixed in the next release.
We're investigating how to optimize frame interpolation for quality instead of for real-time processing in this thread.
https://forum.doom9.org/showthread.php? … ost1800439
This code does give significantly better results than SVP/Interframe ... *when* it behaves.
function jm_fps(clip source, float "fps")
{
fps = default(fps, 25.000)
fps_num = int(fps * 1000)
fps_den = 1000
prefiltered = RemoveGrain(source, 22)
super = MSuper(source, hpad = 16, vpad = 16, levels = 1) # one level is enough for MRecalculate
superfilt = MSuper(prefiltered, hpad = 16, vpad = 16) # all levels for MAnalyse
backward = MAnalyse(superfilt, isb = true, blksize = 16, overlap = 4, search = 3, dct = 0)
forward = MAnalyse(superfilt, isb = false, blksize = 16, overlap = 4, search = 3, dct = 0)
forward_re = MRecalculate(super, forward, blksize = 8, overlap = 2, thSAD = 100)
backward_re = MRecalculate(super, backward, blksize = 8, overlap = 2, thSAD = 100)
out = MFlowFps(source, super, backward_re, forward_re, num = fps_num, den = fps_den, blend = false, ml = 200, mask = 2)
return out
}This has no artifact masking, and produces considerable artifacts.
My question is: how does artifact masking work in SVP, and how could it be added to this script?
Then I'm thinking, artifact masking could fall-back on frame blending instead of disabling frame interpolation altogether.
Then, this algorithm most likely will still will result in some serious artifacts that must be removed manually (replacing these frames with a clip using frame blending).
This is slightly off-topic but not so much because it allows easily re-encoding videos to 60fps, while also optionally upscaling them with very good quality (and applying a few other filters).
You can get x265 output with Opus audio if you want; or simply copy the source audio without re-encoding it.
I posted about this a while back, and now I just released v1.4 that has major improvements in every area.
This software also does a whole bunch of other cool stuff.
Note: the output would be further improved if SVP would support YV24 format, because now I'm downscaling from 16-bit YV24 to 8-bit YV12 in the middle of the processing before doubling the resolution again.
... I have an octacore from 3.5 years ago. They still aren't common?
It rocks at video encoding, couldn't believe it the first time I saw it. Unfortunately performance went backwards after that.
What about YV24 videos? Would it be difficult to support it?
10-bit would be nice, sure, although ffdshow doesn't support.
I know the focus is on live playback, but this is also useful for AviSynth manual processing. Since I run SVP in the middle of the script, the ability to process in YV24 and not downscale the chroma into YV12 before further upscaling the image would considerably improve the image quality in my case. I don't think this would be hard to implement.
Then, could the algorithm itself be further be improved or it's mathematically doing the best it can already? Comparing with various other products doing a similar job (including Abobe Optical Flow), it's already doing a great job, yet there's always room for improvements.
Hey, I haven't been much active around here for a while but I see you got busy with customer support since releasing SVP 4 
You've done a full rewrite of the management UI... but the core really hasn't changed for a long time AFAIK. Are there any plans for further improvements to the core DLLs and the video processing itself?
Feature-wise, would it be difficult to support YV24? For sure it would be slower and require more memory, but for manual processing with AviSynth I don't think it would be an issue. How much more memory and processing would it require?
uh... it means the AviSynth script is not returning valid data...
If you click "Preview in MPC-HC", is the video loading correctly? If not, what error message do you get?
In the Media Encoder window, there is a "Script" tab that allows you to see and customize the auto-generated script. You select your desired settings, then go to the Script tab, then you can fine-tune the script. If you go back to the Settings tab, however, you lose your custom changes.
On a side note I'll mention I made a *lot* of improvements to the media encoder (and the overall software) but never finished those changes... not sure when I'll get back into finishing that.
I am however blown away that the software still gets downloaded over 150 times per week!!
In comparison, with my blog and work, I get about 1 subscriber per day.
Oh, so I can get 72fps. Could you please give me instruction on how to do so, I don't have a clue, even thouh I did check the interframe documentation.
Change NewNum
InterFrame(Cores=8, Tuning="Smooth", NewNum=72, NewDen=1, GPU=true)
I tried the media encoder but.....when i select the file and then i click "encode" the cmd appear and disappear after 1 sec.....what should i do?
i think that this is the error: LoadPlugin: unable to load "C:Progamfiles ecc ecc LSMASHSource.dll",Module found.
Install missing library?
(C:/NaturalGrounding/Temp/Jobi_Script.avs,line 2)
You can try an utility like this to install all VC++ redistributable
http://appnee.com/vc-redist-installer/
1. As MAG79 said
2. You can get 72fps by editing the script manually and changing the parameters of InterFrame (see InterFrame documentation)
3. Yes.
For LSMASHSource.dll not loading, the only thing I can think of is missing VC++ redistributable; not sure which version is required for this.
For failing to load h265 video, LSMASHSource is failing. As an alternative, you can use the option to convert the video to AVI and it will load just fine.
I've been doing some experiments with doing OpenCL processing with my 2 graphic cards with KNLMeans denoiser.
I'm wondering. Could SVP benefit from using both graphic cards on a dual-graphics system?
Although SVP is a lot more CPU-intensive and the CPU is often the bottleneck.
Press 'O' for Options. Playback, Output. DirectShow Video: select System Default instead of madVR.
Adobe Premiere CC 2015.1 introduced Optical Flow to do pretty much what SVP is doing. How does it compare?
SVP
Adobe Premiere Optical Flow
The clip isn't exactly the same; the SVP clip is zoomed in a little bit more, but it's good enough for a comparison. Optical Flow creates UGLY artifacts.
SVP team wins!
I have rules setup based on the various video formats. It works fine, EXCEPT for Interleaved videos. The reason is that a 720p Interleaved video gets seen as having a height of 360 in SVP and thus it selects the wrong profile. Since the manager has rules for whether it is interleaved, it knows it. In that case, it should evaluate rules based on the *real* height of the video, not half as it does right now.
I know this wouldn't be useful to many, but I'd like to hear form the developers. Would it be hard to implement?
Would it be difficult for SVP to support YV24 and/or RGB24 formats with AviSynth?
Sure the performance will be lower, but it can be useful when doing manual encoding.
Hey Chainik, I've been trying to run scripts in AVS+ with InterFrame and there has been several weird issues. Which is strange since SVP itself is running better than ever.
Perhaps you'd want to take a look at this thread and bring your insights
http://forum.doom9.org/showthread.php?t … mp;page=78
Plus I'm working on a software that manages video playback for average users. Integrating an "expert-only" video like MVP that needs to be configured from the command-line is out of the question. It's something I could do myself but I can't expect others to do that.
Oh, I just got a "freeze on seek". These are now rare but still happen.
MAG79, how complicated would it be to rewrite a "ffdshow lite" version that only serves as a bridge for AviSynth? Because right now that code is a dead unmaintaineable mess that does a whole bunch of things.
The person currently working on AviSynth+ has been discussing the possibility of adding high-bit-depth support to the AviSynth engine. I think it would make more sense for SVP to support it based on a native implementation instead of hacking around.
It does seem a bit more stable with 4.0.0.60 as the latest version was causing random crashes in the middle of playback which didn't happen before.
As to whether MPC 1.7.9 helps, I'm not sure.
SmoothVideo Project → Posts by Mystery
Powered by PunBB, supported by Informer Technologies, Inc.