76 Reply by brucethemoose

(17 replies, posted in Using SVP)

Devourer wrote:
Blackfyre wrote:

Keep SVP Shader on Standard, since Complicated introduces a lot of artifacts. But change Frame Interpolation Mode to Uniform (Max Fluidity) instead of Adaptive. Definitely increases smoothness significantly without introducing much, if any artifacts at all; especially since you have artifact masking set to strong like myself.

EDIT: Also I use MPC instead of PotPlayer. And in Madvr settings go to Smooth Motion and enable it and set it to ALWAYS. Then Go back to SVP and instead of setting it to "Fixed Framerate 60 FPS", change that to "Movie Frame Rate x 4", which would make 24FPS movies run at 96FPS.

You have the CPU power to do it, and so do I using my 4790K @ 4.7Ghz. I find it running much smoother than setting it to a fixed framerate of 60. Even though at the end of the day, media player classic is throwing out all the extra frames and using only 60 of them, I find that the 60 used by MPC to have less artifacts then setting SVP to a fixed 60 frame rates.

OK you're right, I did some testing with linked  test video and with some movies and it's improved by changing the Frame Interpolation Mode to Uniform (Max Fluidity) but I have problems of dropped frames changing from 60 fps to "Movie Frame Rate x 4".
The processor reaches a maximum of 30%, the gpu is always at 95%. I think the cpu is bypassed by madvr. I don't know why.

MadVR does basically everything on the GPU. 95% load means you need to turn down the MadVR settings a bit.

Go to forum: Using SVP

77 Reply by brucethemoose

(45 replies, posted in Using SVP)

Chainik wrote:

> since SVP's version of mpv uses ANGLE (aka DXVA)

ANGLE != DXVA

Oops, you're right. Misread that in MPVs documentation.

Go to forum: Using SVP

78 Reply by brucethemoose

(45 replies, posted in Using SVP)

Maphuse wrote:
brucethemoose wrote:

You sure? It says they're from November 9 on the website.


Whenever I get a new laptop, I like to wipe it and clean install Windows to get any bloatware and iffy drivers off.


That would've been the right thing to do. It's kinda too late now since I already installed so much software and some of it is a hassle to install because it has to be done by my employers IT.

Either way, you were right, the website drivers were newer than the windows ones. They still don't work properly, but at least I'm back to "normal".

Theoretically, all you have to do now is wait for the devs to update the version of MPV that ships with SVP, and (possibly) edit the config file so it uses a renderer that doesn't crash your system.

That should happen before Intel puts out another driver update. Heck, it might even work right now, since SVP's version of mpv uses ANGLE (aka DXVA) by default where default mpv doesnt.


These are probably the sections you want:

https://mpv.io/manual/master/#options-hwdec

https://mpv.io/manual/master/#video-out … o-defaults

Go to forum: Using SVP

79 Reply by brucethemoose

(138 replies, posted in Using SVP)

KibaNoOu wrote:

I've got a lot of audio desync lately, I can't figure out why, though, I've got a quite fast PC.

Can you post your mpv.conf? Or at least the parts related to the sync feature?


I have a theory that this is related to mpv's video-sync feature, but I can't test it atm.

Go to forum: Using SVP

80 Reply by brucethemoose

(45 replies, posted in Using SVP)

Maphuse wrote:

Thanks again for all the helpful advice. It's been quite Sisyphean again since I last posted.

The short version is that SVP is now crashing every time I try to assess system performance and basically doesn't work at all again.

The slightly longer version is that I have now an older driver than before, because my laptop apparently shipped with a version that is newer than what is provided by Windows update. I didn't even try the one from the Intel website, because it lists driver version 15, whereas my version is 20. Regarding SVP, it starts with MPV, but is completely laggy and unwatchable. It doesn't start at all with MPC-HC.

I guess my best bet is to just wait it out and hope that the drivers get updated soon?

You sure? It says they're from November 9 on the website.


Whenever I get a new laptop, I like to wipe it and clean install Windows to get any bloatware and iffy drivers off.

Go to forum: Using SVP

81 Reply by brucethemoose

(8 replies, posted in Using SVP)

robert.patrician wrote:

If there's a realtime solution I'll probably go for that. I'll also dig into my makeMKV settings next time to see if there's an option to not interlace when ripping. I'm still very new to the whole SVP stuff, will look into avisynth/vampusynth tomorrow


MakeMKV's job is to rip video files from DVDs without changing them at all, and that's exactly what it does. The DVD is interlaced, you'd get the same results playing the file straight off the disc.


A few video players have deinterlacing options, but personally I would just find the SVP script (normally in the ffdshow raw video filter during playback) and insert a deinterlacing line before it. TIVTC if it's telecined, or Faster/Very Fast QTGMC if it isn't.


Also, I should mention that this is a minor flaw with SVP. MadVR is very good at deinterlacing, but unfortunately it runs after SVP. As of now, integrating them to let MadVR do the deinterlacing is impossible.

Go to forum: Using SVP

82 Reply by brucethemoose

(8 replies, posted in Using SVP)

robert.patrician wrote:

How would I un-interlace it?

That, my friend, is a long rabbit hole to go down.


In a nutshell, first you have to identify what kind of interlacing it has, then apply the appropriate deinterlacing. Re-encoding is one option, but you can also apply it in real time with an AviSynth/VapourSynth script, or even the ffdshow raw video filter SVP comes with.


I'd offer to analyze a test clip myself, but I'm on a phone atm sad

Go to forum: Using SVP

83 Reply by brucethemoose

(8 replies, posted in Using SVP)

It's probably interlaced. You need to process it before SVP can work with it.

Go to forum: Using SVP

84 Reply by brucethemoose

(45 replies, posted in Using SVP)

Gotta love Intel's IGP drivers...

Well then, uninstalling your IGP drivers, cleaning out the leftovers with DDU, and letting Windows Update grab fresh ones isn't a bad idea.

http://www.wagnardmobile.com/forums/vie … bd2e21a0a7


You could also grab the drivers from their site:

http://www.intel.com/content/www/us/en/ … s-620.html


EDIT: Also it could be 0.21, I actually haven't checked SVP's version of mpv's build number myself. I just assumed that might be the case tongue

Go to forum: Using SVP

85 Reply by brucethemoose

(138 replies, posted in Using SVP)

dsiOne wrote:

Has anyone figured out how to stop audio desync? SVP + MPV runs beautifully otherwise...

Don't seek too much.

And if desyncs persist between relaunches, delete the "watch_later" folder in %appdata%/mpv.

Go to forum: Using SVP

86 Reply by brucethemoose

(45 replies, posted in Using SVP)

Chainik wrote:

> I don't have any on hand
http://www.svp-team.com/files/demo/space_60.mkv

> the version of MPV that comes with SVP doesn't play anything well, even with SVP turned off, whereas the standard version works absolutely flawlessly

"SVP's version" differs from "standard" in the default config file which contains

vo=opengl-hq:backend=angle

did you tried different video renderers in MPC-HC, I mean all of them one by one, starting from "system default"?

That, and SVP ships with an older build of MPV.


My suspicion is that bleeding edge versions of MPV (like the one I linked) support Kaby Lake, while the older version SVP installs does not. What about the newest version of plain MPC, does that work with and without SVP?

EDIT: And OP did try MadVR and MPC without MadVR  which means EVR I assume.

Go to forum: Using SVP

87 Reply by brucethemoose

(45 replies, posted in Using SVP)

Maphuse wrote:

OK, so first I tried all the suggestions that I hadn't tried yet, i.e. the large motion vector grid setting, which did nothing to help my performence.
Just for the heck of it, I used ThrottleStop to disable turbo and did another SVPmark, and while the results were worse than before, they were enough for 60fps at "good" settings.

After that I uninstalled all my video players and codecs, including SVP, restarted, and installed the latest version of mpv, and the playback is flawless.
I haven't reinstalled SVP yet, because I fear that it will mess everything up again and I maybe you guys have other ideas.

Good, so playback is OK! It's an SVP issue then.

"and codecs"

You said it before, but just to be clear... you aren't installing anything besides SVP, right? "Codec packs" are a relic of the past, you shouldn't install anything beyond what SVP installs.

Try a clean install of SVP 4 Pro, including MPV and LAV Filters for now. If MPC and MPV with SVP still don't work, that will narrow down the issue considerably.

Go to forum: Using SVP

88 Reply by brucethemoose

(45 replies, posted in Using SVP)

Maphuse wrote:

James D, just a quick question before I get the time to try your suggestions: Shouldn't the throttlestop monitor SHOW that throttling is active by displaying values less than 100 in the CMod or Chip column?

Also, I already mentioned that I even have issues playing files without SVP, in MPC, VLC and MPV. I'm currently stuck using Windows Media Player because it's the only player that plays everything smoothly. Everyone seems to be ignoring that so far.

Oh, I missed that bit in the 3rd post. Something else is screwed up if things don't work without SVP.

Kaby Lake is really new, so my first suspicion is that your video decoders aren't up-to-date enough to use it. SVP's versions are a bit out-of-date, so the newer version may add Kaby Lake support.

1st, uninstall SVP and everything else it installed. Then try manually downloading the latest MPV build:

https://sourceforge.net/projects/mpv-pl … ows/files/

And/or the latest MPC (which should use the latest version of LAV to decode):

https://mpc-hc.org/2015/11/14/1.7.10-released/




If playback is still buggy, that suggests video decoding/playback is borked on your system. I would suggest a clean Windows install.

Go to forum: Using SVP

89 Reply by brucethemoose

(45 replies, posted in Using SVP)

Maphuse wrote:

Start with a large motion vector grid and 2 pixel precision, just to see if it works.

Sorry for the n00b question, but I'm not sure how to do that. I see the entry for mv_grid in my settings, but I can't change it.

Did you buy pro? You have to reinstall it if you do, I believe.


The settings menu looks like this:


https://imgur.com/a/R8nld

Go to forum: Using SVP

90 Reply by brucethemoose

(45 replies, posted in Using SVP)

James D wrote:
Maphuse wrote:

Start with a large motion vector grid and 2 pixel precision, just to see if it works.

Sorry for the n00b question, but I'm not sure how to do that. I see the entry for mv_grid in my settings, but I can't change it.

Sheesh, it hurts me seeing how this troubleshooting still continues while everything was cleared since the beginning and real answer was already posted.
Your own screenshot clearly shows 28% CPU load at playback resulting 0.3 index score (which is literally what means throttling) while your title claims it's "high load" and you say you were not mislead by marketing? The real CPU clocks were even less than 20% because overall score is miscalculated due to Hyperthreading and you still look for a magic fix which is not related to this issue?
Did you follow my advice about ThrottleStop? Where you could see CPU behavior while playback and possibly tinker with adjusteable TDP settings? Because another real advice aside this would be... don't buy ultrabooks for SVP.

Except throttlestop was already tried, and didn't work.

From what I understand, the real problem is that SVP doesn't run the benchmark long enough for ultrabook CPUs to reach their stable, non turbo speeds.

The solution isn't to try and lock the CPU in a power state it can't safely sustain under a constant load, or to buy a new computer. The solution is to manually configure SVP's settings.

Go to forum: Using SVP

91 Reply by brucethemoose

(45 replies, posted in Using SVP)

Maphuse wrote:

Thanks for all the suggestions.

  • James D, I'm not sure what you mean by "2 times smaller" - do you mean half? Using rough numbers, I entered 400, 150 and 500, but it didn't really change much.

  • brucethemoose, you're completely right, the problem starts rightaway, when the processor speed reads 3.4 GHz. About your suggestion, I finally bought the pro version (I've been enjoying SVP for long enough to feel justified in paying for it). MPV performance is kind of the same as MPC, it definitely doesn't fix my problem. If I find a USB stick and some time, I'll see what Linux does if we can't find another solution to this problem

Thanks everyone for your input so far. I'd be quite happy if we could solve this together.

MPV is significantly faster for me. I can decrease the motion vectors grid by 1 or 2 notches over what my CPU can normally handle.


Anyway, you should try manually decreasing settings too. Start with a large motion vector grid and 2 pixel precision, just to see if it works.

Go to forum: Using SVP

92 Reply by brucethemoose

(45 replies, posted in Using SVP)

I agree, I'm 99% sure performance isn't your issue. Even if it is throttling to, say, 2ghz, it should still be faster than my 4 ancient Stars cores at their stock 1.5ghz.

On top of that, it sounds like the issue happens immediately. If it really were throttling, it wouldn't happen until a minute or a few minutes later.


There is an alternative, surefire way to test: dual boot any Linux disto, and install SVP 4 for Linux.

This not only rules out any possible Windows issues, it takes MPC, ffdshow, LAV and Avisynth SVP out of the equation. If SVP 4 on Linux doesn't work, then it's an issue with the core SVP code itself or a performance issue. If it does, then it's likely an install issue or some weird incompatibility somewhere in the chain.


If it turns out to be an incompatibility, SVP 4 Pro on Windows would likely work, as the core is essentially the same as SVP 4  Free on Linux. So think of Linux as a way of demoing SVP 4 Pro.


EDIT:

However, as someone else mentioned, that 2nd screenshot does look alot like a throttling issue... I get what you're saying, but just keep that in mind and don't rule it out just yet. SVPmark and the SVP benchmark that sets settings could be finishing before the throttling, which means the latter is setting your default SVP settings too high.

Go to forum: Using SVP

93 Reply by brucethemoose

(45 replies, posted in Using SVP)

You don't have Pro, do you? I'd be interested to see how well mpv works.


I'm 99% sure that CPU is faster than my old A8-3500m, which I know fast enough for 1080p SVP. Try a clean install, something funky might be going on.

Go to forum: Using SVP

94 Reply by brucethemoose

(10 replies, posted in Using SVP)

Nintendo Maniac 64 wrote:
brucethemoose wrote:

Just use DXVA scaling.

That's even worse for performance because SVP will be trying to interpolate at 1080p then rather than at 720p.

And for reference, I already use DXVA scaling for upscaling.

You can sort of compensate for that by increasing the block size.

AFAIK, bigger block sizes at high res is similar to smaller sizes at lower res.

Go to forum: Using SVP

95 Reply by brucethemoose

(10 replies, posted in Using SVP)

Nintendo Maniac 64 wrote:

Exactly 1 month later, I figured out why my GPU utilization was higher than expected...

It turns out that not using D3D Fullscreen increases both the CPU and the GPU utilization - it was my impression that D3D Fullscreen reduced CPU utilization but increased GPU utilization, not decreased both.


So yes, I can confirm that SVP's downscaling algorithm does in fact use the CPU.  Unfortunately for me, it seems like this downscaling algorithm is actually kind of demanding on the CPU since I have to reduce my SVP profile settings considerably.

Presumably there's no way to use a lighter-weight algorithm, correct?

Just use DXVA scaling. If you're trying to save resources, it doesn't actually use your GPU's shaders: it uses a separate encoding block on it, and won't have any impact on other things you do on the GPU.

There are lighter weight AviSynth algorithms too, but AviSynth scripting is one heck of a rabbit hole to go down...

Go to forum: Using SVP

96 Reply by brucethemoose

(30 replies, posted in Using SVP)

Nintendo Maniac 64 wrote:
Alex wrote:

I know hardware decoding isn't possible with this GPU - it doesn't support ShadowPlay much for the same reasons - only 6xx and onward had HW-Accelerated H.264.

Wait wait wait, decoding, not encoding?

My NVS 3100M (essentially the Quadro version of the 210M) supports hardware h.264 decoding via DXVA2 just fine (tested via the LAVfilters built into MPC-HC).

Are you sure it's not just something borky with your drivers?  Have you tried completely uninstalling the drivers via Display Driver Uninstaller and then re-installing your drivers?

I think Alex meant to say encoding, which is indeed a new thing.

Go to forum: Using SVP

97 Reply by brucethemoose

(30 replies, posted in Using SVP)

Alex wrote:

Oh and Bruce, forgot to mention but my computer is too old and doesn't support any GPU H.264 encoding. I really need a new computer.

My GPU is really too old and low-grade (560M) to be any use at all. It doesn't help at all in encoding and Team Fortress 2 is about the most resource-heavy game it can play, hahaha. That's why I keep saying that I probably just need to upgrade system - the software you guys sent me probably doesn't work on my computer just because the hardware is just too damn old and unsupported. The only reason the system is bearable is because the CPU is so impressive for it's age - it was bleeding edge at the time of being bought and is heavily overclocked. I'm honestly impressed it's lasted this long when the GPU already had to be replaced once - Intel must do a good job of quality control, or maybe the Sandy Bridge chips were especially stable or something.

I used to have a 580M in this but it died 2 years ago and when I called the manufacturer they said it's not made anymore and they only had 560M in stock and that I was lucky because they're almost out and the computer isn't compatible with anything else. If any more hardware on this dies I'm basically out of luck on repairing it because it's all too old.

It's either that or the Windows 10. Or both. It's an odd combination to have the latest OS on such an old machine I suppose. Could cause some confusion in software I guess. Windows 7 was still new and shiny when I got this thing, just to give you an idea.

I run a llano APU (that's AMD 5xxx/Nvidia 5xx-era graphics, just like your cards + an even older CPU core) on Windows 10, and StaxRip works just fine. Even fancy OpenCL vapoursynth filters work without much hassle.

Go to forum: Using SVP

98 Reply by brucethemoose

(30 replies, posted in Using SVP)

Nintendo Maniac 64 wrote:
brucethemoose wrote:

CPU VP9 if you want the smallest possible file size optimized for YouTube

Even if you encoded in VP9 YouTube will still re-encode it for their VP9 formats.

Dang.

So (slightly off topic) whats the best way to upload for a given file size? H.265?

Go to forum: Using SVP

99 Reply by brucethemoose

(30 replies, posted in Using SVP)

It could be better, but it's really not that bad now

* download staxrip

* open video in vapoursynth staxrip

* set audio to "mux only"

* Right click SVP -> information -> additional information -> generate last used AVS script.

* Copy it. Right click source in Staxrip, and paste it in there.

* Set your encoding settings (I recommend the AMD/Nvidia h.264 encoders if you're looking for speedy encoding, or CPU VP9 if you want the smallest possible file size optimized for YouTube)

* Click next, wait, and it's done!

If you're really selling this as a serious product you might wanna try streamlining and presetting it as much as possible so that regular technologically-inept Joe Blows can get everything set-up with just a download and install - coming with a pre-configured player and everything.

+1, but for video playback I'm thinking that's what MPV will eventually be. Just install SVP, click MPV, and it should play dang near anything pretty well without any extra clicking or installing.

MPV just needs a GUI better than SMPlayer (which is hopefully coming soon with MPC-QT).

For video conversion, that isn't really practical because of the WIDELY varying encoding settings. Sure you could have 1 click, but the results would be less than optimal for the majority of the population, and I don't think the devs want to re-invent StaxRip.

EDIT: Maybe they could bundle StaxRip + a default SVP template in the installer? That would work.

Go to forum: Using SVP

100 Reply by brucethemoose

(2 replies, posted in Using SVP)

Well you could use AviSource and cut the first 3 frames of every video.

Go to forum: Using SVP