Search options (Page 20 of 24)

With the 4GB patch, you could advertise SVP's ability to "finally make your 8GB RAM useful" as a feature!

MaXimus, regular builds don't support MT which tend to be less stable. Multi-Threading is generally only supported in special builds. SVP requires Multi-Threading to do its job in real-time.

SEt is saying the MT will be there, so there you'll have your better alternative! (finally)

The videos that causes issues are generally 1080p 29.97fps.

One option is to create a new profile for those to make sure it uses a 2:1 ratio.

Or another option would be to disable SVP in this profile as 29.97 could be considered smooth enough and madVR would then do a better job.

For now I'll probably leave it to 2:1, and if I run into further issues with those videos, I might consider Plan B

Ok... in any way, I want my setup to work on both 768p display and 1080p display (where there would be no downscaling to reduce CPU load).

So in this case, I might be better off disabling the resize option so that madVR can do its job properly. And then see what quality difference I get.

One feature request for SVP: it builds profiles based on video types, but it would also be good if could make different profiles depending on the output type (768p or 1080p)

What anti-virus (and/or firewall) are you using?

When I re-installed Kaspersky Anti-Virus, at first I couldn't open PayPal because it hadn't yet updated its database of certificates.

Just looking at the file size (twice bigger than 2.5.8), I'm not sure I want to look at it.

It's definitely not working with resize functions. Just create a basic script that has a Spline32Resize function and it has lots of serious visual glitches.

I get what you're saying... and perhaps your time is better spent working on SVP itself while you let others figure out AviSynth MT. That's a WHOLE other project in itself.

Now it's working with either v2.5.8 or v2.6. Perhaps you could give the option during installation as to which version to use. I'd probably recommend v2.6 if they have over 3GB of RAM.

If they want SVP to work in x64, then someone will have to first make a proper AviSynth MT work in x64 first. THEN you can rewrite your assemblies in x64. But for now, most video components are still working in x86. Might be different a few years from now.

When I was looking into testing x64 AviSynth, the people in the community were under the impression that you weren't interested in providing a x64 version of SVP. That's not actually the case. You want to support that, but there just is no version of AviSynth that supports x64, MT and ffdshow. You just have to let them know that. As soon as any version supports x64, MT and ffdshow, you'll be more than happy to provide x64 SVP binaries for it. Until then, there's no point in spending time there.

That's what the 'Thanks' button is for

For now I'll stick to 2.6 MT for video encoding. With MT enabled, it gives better performance than the official AviSynth+ which also works well just not for SVP.

Development-wise, I think the memory leaks of 2.6 MT would be easier to fix than all the bugs in AviSynth+ MT!

And does SVP really have to work on top of ffdshow and avisynth, which are 2 very old pieces of codes not well maintained? Could it run as a rendering filter like madVR, or in some other way? And if you were to make SVP do its job *after* madVR, what would need to change in its structure?

This isn't good either.

Clock deviation was -2% and was gradually going down (-0.65% on the screenshot)

"1 frame drop every 1.16 seconds" isn't good either; although those don't show up in "dropped frames"

I have done some performance tests with SVP encoding via Interframe

For each version I tried with and without the first command "Setmemorymax(512)"

2.5.8 MT:   0m45
2.5.8 MT 512MB:   0m41
2.6 MT:   0m43
2.6 MT 512MB:   0m49
+ MT:   1m20
+ MT 512MB:   1m20

AviSynth 2.5.8 / 2.6 MT Script

SetMTMode(3,4)
PluginPath = "Encoder\"
AviSource("Job3_Input.avi", audio=false).ConvertToYV12()
SetMTMode(2)
Spline36Resize(384, 288)
LoadPlugin(PluginPath+"svpflow1.dll")
LoadPlugin(PluginPath+"svpflow2.dll")
Import(PluginPath+"InterFrame2.avsi")
InterFrame(Cores=8, NewNum=60000, NewDen=1001, GPU=true)

AviSynth+ MT Script (not sure I got this right)

SetFilterMTMode("",2)
SetFilterMTMode("ffdShow_source",3)
PluginPath = "Encoder\"
AviSource("Job3_Input.avi", audio=false).ConvertToYV12()
Spline36Resize(384, 288)
LoadPlugin(PluginPath+"svpflow1.dll")
LoadPlugin(PluginPath+"svpflow2.dll")
Import(PluginPath+"InterFrame2.avsi")
InterFrame(Cores=8, NewNum=60000, NewDen=1001, GPU=true)

Oh it doesn't even have a compiled version! Thanks, I really wasn't interested in compiling it myself.

So far it's working, with memory usage between 600-1000MB (similar to 2.5.8)

There might be a slight additional lag when initializing videos.

Anything I should pay attention to when testing it?

The main problem with 2.5.8 MT is that especially when controlling MPC-HC via API, it crashes very regularly and I need to scan the process every few seconds to detect a crash to auto-kill the process.

One question about SVP... if I wanted to patch 'generate.js' during setup, is there a way for me to programmatically know in which folder SVP was installed? MPC-HC has a registry key with its installation path, but I haven't found anything to indicate SVP's location.

And another quick question (perhaps off-topic): when using SVP with Interframe, what happens if I always specify to use the GPU and it runs on a computer that doesn't support it?

That's madVR's smooth motion that is off. You want to keep it that way.

If it doesn't play at 60 or 120fps, you'll know by looking at the image.