Search options (Page 40 of 55)

The problem is that Bulldozer's general performance was worse than even a Phenom II x6 in several cases, so considering how much faster the likes of an Intel i7 was, devs saw no reason to purchase such a processor and to develop for it.

I believe a similar thing is going on with HSA currently - devs see no reason to purchase a Kaveri APU when it'll be sub-par at everything else that they do, so they don't even bother.  In this case we probably won't see more widespread usage of HSA until we have Zen APUs, and that's assuming that Jim Keller is as good as he has been in the past (a game console or server using an HSA-enabled APU would also very likely take advantage of HSA, but that's beside the point here).

Set SVP shader to "Complicated" - note that it will artifact on thin lines however, so for footage with lots of thin lines keep using the Standard shader.

....uhhh, my point was just pointing out a possible reason why mashingan could have been having issues.

Also I'm not sure why you're bringing up old CPU architectures like the Pentium 4 in regards to my mention of processor models that are only a year old or so like the Pentium G3258...

Another thing I forgot - using D3D Fullscreen and only using Bilinear (normal, non-PS 2.0) in MPC-HC also helps reduce CPU utilization...which means getting away with higher settings in SVP.

Take note that the settings I posted are optimized for minimal artifact since the 25fps content I watch is highly susceptible to said artifacts (motorsports).  For 24fps and 30fps I normally use Uniform + Simple Lite instead which is actually smoother but gives more artifacts, though they're not really noticeable on the 24fps and 30fps content I watch.

Another key thing is that, since you're doing software decoding of the video stream itself, using a codec that's light on the CPU (i.e. MPEG2, FLV1, etc) can allow you to use higher settings in SVP.  In particular, I can get away with using Uniform + Standard for 30fps, 25fps, and 24fps content in such situations.  Heck, if I don't plan on watching a video for a while, I'll even sometimes re-encode a video, such as a 1080p VP9 video from YouTube, into 720p FLV1 @ Quantizer 2 (the filesize is like 6-8x larger, but it doesn't matter when I don't plan on keeping it anyway)

This is all assuming 720p videos and 60hz monitor refresh rate of course.

EDIT: Just remembered one last thing - you can also save a few more percent of CPU utilization by making sure that yous "Default Sampling Rate" in the Windows control panel matches the sampling rate of the audio stream in whatever video you're watching.

EDIT 2: For most use-cases H.263 is probably the best choice in terms of re-encoding since, at Quantizer 2, if only has 2% more CPU utilization than FLV1 on SVP-intensive content and 8% smaller filesize, plus for other devices it has compatibility with the MP4 container not to mention HW decoding capability if available.

EDIT 3: ...except if you're encoding directly from VP9 via Avidemux, then there's some weird issues with SVP not working correctly with specific codec-container combinations.  The ones I find work are Mpeg4 ASP (xvid4) with MPEG Quantization or Mpeg4 ASP (ff), both in an MP4 container (and only an MP4 container, using MKVtoolnix after-the-fact does not work correctly) or FLV1 into an FLV container (which does work with MKVtoolnix, so that'd be the most flexible).  Just remember that Avidemux doesn't like Opus audio, so you usually have to deselect it via "Audio" -> "Select Audio"; for MP4 you'll need to provide an external AAC/M4A/MP4/MP3/AC3 audio stream for Avidemux to add to the video.

EDIT 4: Just realized another one - setting processing threads in SVP to "5 threads" seems to give the lowest CPU utilization without resulting in decreased SVP performance (like if you set "2 threads", SVP won't run at full speed even when your CPU utilization is like 30%).

EDIT 5: Go figure, it turns out that non-PS 2.0 bilinear in MPC-HC is actually less CPU-intensive with weak GPUs, so use that instead!

Your definition of "low-end" hardware must not be the same as mine, because on my 2.4GHz Core 2 Duo without any GPU acceleration nor HW decoding, I can get much less artifacting with SVP 3.1.7 due to the fact that SVP 4 insists on using a higher-end interpolation mode like "Adaptive" combined with a low-quality shader setting like "2. Sharp" along with a low-resolution vectors grid like 28px; meanwhile in SVP 3.1.7 I can choose to instead use 1m + Standard + 16px.

Thread I made regarding the subject:
http://www.svp-team.com/forum/viewtopic.php?id=2699

TDP does not equal performance - and easy example is Broadwell which is only 65w TDP yet has slightly better IPC than Haswell and has the fastest iGPU Intel has ever made.

Heck, even the i7-3770k has a TDP of only 77w.

Few people use Xeons, so you probably would have been better asking for the performance difference between an i5-4590 and an i7-4770.

The idea is that people might see that your thread title says "Xeon" and they decide to not even click your thread because they have no idea about Xeons even though they're pretty much the same as an i7 but without overclocking, lower clockrate, and have more features.

However, a Xeon does lack an iGPU which could be useful if you're going to use MadVR - that way you can have SVP use your iGPU while MadVR uses your discrete GPU.  In that case maybe it'd be better to ask about an i7-4770 but mention that it's actually its Xeon equivalent and therefore doesn't have an iGPU.

Uhhh, so what am I supposed to do with this file?

I'm not using GPU-acceleration in SVP 3 either seeing how the PC in question only has a lowly Intel 965GMA iGPU from 2007 which is low-end enough that it can't even smoothly do 60fps at 1080p in MPC-HC unless I enable "D3D Fullscreen".

And for reference, the iGPU also doesn't support h.264 hardware decoding.

I figured it was something like this.  I noticed while testing various settings in SVP 3 that I can achieve similar settings but that it's definitely more artifact-heavy which I particularly attributed to the low quality shader setting; this is the main reason why I use 1m for my interpolation mode (which also lets me use 16px)

Yeah, maybe lower-end than a modern desktop CPU, but that thing is easily still at least twice as fast as my 2.4GHz Core 2 Duo due to considerably better IPC, SMT, and an iGPU that SVP can actually use and has h.264 HW decoding.

One thing to note regarding thin lines is that you'll get wavy squiggly lines if you use "Complicated."

No, you don't want frame crop.

Instead, you want "Outer lighting" with it set to "Fill black bars only".

OK I've attached the script.

I've also attached a very short real-world video clip that gives the kind of artifacts I'm talking about.  Now if that was all that occurred in the full video then it'd be fine, but they happen quite frequently and consistently (that corner shown in the video is particularly offensive in that regard).

I was looking closer at the video and I noticed that the actual panning background and the like looks perfectly fine, but that it's on-screen UI and the cars themselves that are artifact-ridden.  It seems to be cases of objects that are moving against a camera-pan that become artifact-ridden.

Oh and BTW, regarding my SVP 3 settings, for heaver videos I may need to set the shader to "Simple", but even "Simple Lite" gives fewer artifacts than SVP4 and only gives me like 65% CPU utilization with the full video that the attached test footage was taken from.

Maybe it's something with audio bitstreaming then?