Search options (Page 3 of 3)

PROBLEM SOLVED: When reloading SVP 3.1.6 Core to get an old version of the svpflow dlls I overlooked reapplying the hotfix (I screwed-up).  All fixed now. Works very well - perhaps 'smoother' (less jitter) than with the old svpflow dlls with MPC-BE.  I'll perform some controlled testing and report back with CPU/GPU utilization values.

Something isn't playing nice... Swapped in the new svpflow1.dll and svpflow2.dll files.

• Fired up SVP and configured a 3840x2160/25fps profile using the values I've been using right along while conducting my tests.

• Rendered the 4K video file (it ran smoothly with ~25% CPU and GPU) and exported the SVP script (just to make sure that nothing had changed with the new SVPflow dll files).

• Then copied the SVP script into the Avisynth scripts I've been using for AviSynth 2.6 MT and AVS+. Made sure the avisynth.dll files were in the proper folders and the SVP svpflow dlls were in the PluginPath.

Keep in mind I'm using the 4K file with out downsizing. Under AVS+ the CPU was ~65% and GPU ~60% (about what I have been seeing with the 'old' svpflow dll files after I jacked-up the SVP config and video rendering settings), System memory utilization was ~1.4GB. However I was dropping frames all over the place - it was a disaster.

Edit: Tried lowering Threads and Prefetch values from 8 to 6 but no difference with the performance - still dropping frames like crazy.

Swapping over to AviSynth 2.6 MT I experienced the same performance issues running both MPC-BE and MPC-HC as well.  Swapping back to the 'old' svpflow dll files and SVP script solved the issue.

Something ain't quite right. Got any ideas? I'll gladly supply system config details and script samples.

Using MPC-BE/AVS+ I tried your suggestion about D3D fullscreen. With EVR-CP I enabled D3D Fullscreen, 10-bit RGB output, 32-bit FP Surfaces and Michell-Netravali spline (PS 2.0). CPU unchanged at ~34%. GPU now ~67%. and I gotta tell ya..it's slick as snot on a door knob.

Not only that but being downsized from 4K to 2K on my 40" 1080P Sony Bravia at arms length (it's my monitor) it's looking good. This is starting to be fun    However, I agree with Chainik, I doubt that the 'average' consumer would think as much.

Thanks Chainik and Nintendo - this little experiment has given me a lot of new stuff to contemplate.

To satisfy my curiosity I conducted some comparisons with SVP running on AviSynth (AVS+ and AviSynth 2.6 MT). Using MPC-BE and MPC-HC on my Windows 7 64-bit OS.

• The test video was the "SONY F55 4K Blue Shanghai Zhen Wang Wei 150mbps.mp4" file mentioned earlier.

  All tests were conducted using an AviSynth script with the SVP configuration embedded within that script. The SVP values were identical in all cases with the global resize_string="". The 4K video (3840x2160/25FPS) was the input to the SVP script. As I have a 1080P display (40" Sony Bravia) set at 60FPS the GPU downsized 3840x2160/60FPS output from SVP to 1920x1080/60FPS.

  The MPC-BE and HC video renderers were EVR-CP 8-bit Integer set to "Nearest Neighbor". I utilized that particular Video Rendering configuration because I quickly discovered that anything more would max my HD-7850. I believe this to be the case due to using "gpu:1" in the SVP values. I tried gpu:0 but it maxed my CPU (Intel i7-3770@3.4GHz).

  The same filters/latest revisions (LAv Video, LAV Splitter, ffdshow raw video, File source async and EVR-CP) were used in all cases.

  Global threads=8 with AviSynth 2.6MT. Prefetch(8) was used with AVS+. Note: As you know the # of 'threads' make a large difference with memory useage. I was a 'set threads to 15 and forget it' kinda guy with AvisYNTH 2.6MT but have now rethought that setting after running these tests.

  Both MPC.** executables were patched for "4K". I did note that I had to re patch them once when changing test configurations - more testing needed to see if that was a result of changing the AviSynth .DLLs. Speaking of which..I simply moved the appropriate AviSynth.dll to the requisite MPC-BE or MPC-HC folder along with changing the AviSynth script when reconfiguring them for AviSynth 2.6MT or AVS+.

Bottom Live:

All tests with MPC-BE and HC yielded similar GPU and CPU utilization (in my case ~50% GPU and 32% CPU).
MPC-BE consistently used ~ 20% more system memory with both versions of AviSynth.
MPC-BE was a bit smoother - less jitter (+/- ~1MS versus +/- ~2MS with MCC-HC)

Actual average memory utilization was:
MPC-BE ~1.84GB with AVS+ -- ~2.27GB with AviSynth 2.6MT
MPC-HC ~1.44GB with AVS+ -- ~1.82GB with AviSynth 2.6MT

In no cases did anything crash and system memory utilization would level out after 5-10 seconds and then remain fairly constant.

Edit: SetMemoryMax(1024). When using "SetMemoryMax(512) with either MPC-BE or HC it will crash.

Yup, that's the one I just tested prior to the latest (r1780) from James D. Perhaps the difference between or CPUs is an issue.  When choosing a DLL I go for the vanilla Win7 build as I've run into issues (not unlike this one) with using ones optimized for processor specific support routines.

BTW: What's a good utility for verifying the AviSynth.dll being used? I most likely already have it but I got so many 'tools' I've lost track...

Standard SVP install has been working trouble free. With your changes I get instant crash on my i7-3770 (quad core - 3.4GHz) , HD 7850 and win7 64 bit.  With MPC-BE(x86) and HC(x86) with 4GB patch. SVP 3.1.6.1052 with 4GB patch. Appears to be AviSynth.dll related. Was already up to date with svpflow*.dll. Looking forward to a vanilla AviSynth.dll build.

I had similar issues with logo overlays causing motion defects when the video panned.  My test file: https://vimeo.com/51322829 I run 'SVP' via avisynth so I don't have the SVP settings off the top of my head.  But here is the pertinent part of the avisynth script I use. Basically I reduced the block size to 16 (H&V) and set overlap to 2.  It didn't completely cure it but it's 'not all that bad' now.

BTW: These are settings for a 720P/23.976 video displayed at 59.938

nnedi3_rpow2(rfactor=2,cshift="Spline36Resize",fwidth=1920,fheight=1080,nsize=0,nns=2,qual=1)
global crop_params=""
global resize_string=""#spline36resize(2560,1440)  lanczos4resize(1920,1080)
global super_params="{pel:2,scale:{up:0},gpu:1,full:true,rc:true}"#pel:1 full:false
global analyse_params="{block:{overlap:2,w:16},main:{search:{coarse:{distance:-10},distance:0}},refine:[{thsad:250}]}"#overlap:0,w:32
global smoothfps_params="{rate:{num:5,den:2},algo:13,mask:{cover:80},scene:{blend:true,limits:{scene:6000,zero:100,blocks:51}}}"
#global smoothfps_params="{rate:{num:24000,den:1001,abs:true},algo:23,mask:{cover:80},scene:{blend:true}}"