AdrianGaming wrote:

SVSmoothFps(super, vectors, "{algo:23,
    mask:{cover:100,area:40},
    scene:{mode:0}}", mt=9, url="www.svp-team.com")

There comes the error:
SVSmoothFps: Invalid URL!

Could someone help me? Thanks!

Try that adding 

, url="www.svp-team.com"

  to to SVSmoothFps. See above edit sample.

2

(12 replies, posted in Using SVP)

Alex wrote:

Last update for tonight I think.

The only thing I'm unsure of is if ReClock is being used - ReClock isn't listed anywhere in the filters section or anything and no icon in the tray appears (though that's something I've just noticed about this codec pack in particular - KCP always showed it but I can't know if it's working with this one).

ReClock is 32-bit only sad

Nintendo Maniac 64 wrote:
MistahBonzai wrote:

Vizio P50-C1

Bu-but... that's still an LCD. D:

I've spent countless hours researching. I don't watch content, I create it smile The typical viewing distance is 18-24 inches. Text resolution is very important to me. Had an opportunity to view the 55" curved and flat LG OLEDs straight on with text at 18-24 inches a couple of weeks back. Unfortunately the pentile (actually RGBW) subpixel arrangement utilized in these displays (to create a brighter display) just doesn't cut it when viewed close-up - kinda like an OLED phone display at 100 dpi sad

Now 50 inch is about a large as I can go at my viewing distance without going beyond the width comfort zone. However the curve could work wonders for use as a monitor so I looked very hard to justify the ragged pixel arrangement which resulted in blurry definition in fine text . I was prepared to part with ~$2500 but low and behold the best display I have evaluated so far that fits the bill is the new Vizio P50-C1. True 10-bit panel and all. And text reproduction is outstanding! I was pleasantly surprised (actually shocked).

The low latency (gaming) HDMI port supports 2160@60, 4:2:0, up to 10-bit per color and 1080p@120, 4:4:4, up to 10-bit per color. Overall the standard HDMI ports tops out at  2160@60 4:2:0, up to 12 bit per color. And there is of course Dolby Digital HDR.

Hey, I haven't been there in like..forever smile I started using Jan Willems fork of MPC-HC quite a few years back cuz he supported 10-bit and color management. Eventually I found myself more often using the main version of MPC-HC along with madVR once madshi added so many sweet processing and scaling options. My HD-7850 is getting kinda long in the tooth and I'm eagerly awaiting the AMD Polaris series GPUs (thus an upgrade to the Vizio P50-C1 from my trusty, but 10 year old, Sony Bravia 40w3000.

Yes, I was unduly pessimistic. The HEVC H265 material I have tested has been, for the most part, 2160p HEVC (Main 10@L5.1@High) displayed full screen (exclusive mode). The display is 1080p/59.940/10-bit and all input runs through madVR by default. Went back and tested with some of that material (2160p/29.970) using EVR(CP) and discovered it plays smoothly although output is of course 8-bit. My goal is to eventually upgrade to a '4K' display. The Vizio P50-C1 does all that I want in the way graphics editing and the like. Sorry again about being overly pessimistic as I had overlooked all possibilities other than my goal which is full 2160p/10-bit processing.

Not to drag this thread down a rat hole but..it takes a fair amount of decoder (CPU) 'horsepower' - more than most folks have on hand. It is more efficient to do it with dedicated hardware. Bottomline is that the dedicated hardware support is found only on the latest offerings...

  • Intel 6th-generation ‘Skylake’ Core processors or newer
    AMD 6th-generation ‘Carizzo’ APUs or newer
    AMD ‘Fiji’ GPUs (Radeon R9 Fury/Fury X/Nano) or newer
    Nvidia GM206 GPUs (GeForce GTX 960/950) or newer
    Other Nvidia GeForce GTX 900 series GPUs have partial HEVC hardware decoding support
    Qualcomm Snapdragon 805/615/410/208 SoCs or newer
    Nvidia Tegra X1 SoCs or newer
    Samsung Exynos 5 Octa 5430 SoCs or newer
    Apple A8 SoCs or newer
    Some MediaTek SoCs from mid-2014 onwards

7

(138 replies, posted in Using SVP)

Chainik wrote:

> mpc-qt

check this out: link big_smile
(a mingw-64 build with Qt 5.5 + mpv-1.dll with vapoursynth + "input-ipc-server=mpvpipe" option hardcoded into mpc-qt sources)

I realize this isn't the place for a configuration question but I can't find any Windows configuration hints... I have the latest 64-bit versions of VapourSynth and Python installed and can verify the VapourSynth installation via Python "print(c.version())" - returns "core R32". I'm not real savvy at this sort of thing but I do OK with scripts to work from and pros like you to point me in the right direction.

I DL'ed mpc-qt-svp-20160517 pkg and unziped it in a standalone folder. When I attempt to run mpc-qt.exe from that folder the following error is returned "The program can't start because VapourSynth.dll is missing from your computer".

Does it need VapourSynth.dll in C:\Windows\System32 - like AviSynth.dll? Do I need to register it ()

Better yet..if you have the time and it's not much of an effort would you please offer up some suggestions that would help me try out MPC-QT?

8

(5 replies, posted in Using SVP)

Many years ago I used to be a codec pack kinda guy. The more codecs the better wink  Then, when things got kinda sketchy, I was left troubleshooting some very convoluted issues which proved near impossible to solve without some lengthy uninstall/reinstall sessions. What I learned was that more is not always better - infact is is usually worse.

What I do now, assuming a 64-bit windows OS, as far as MPC-xx/LAV/MadVR/SVP is concerned is install them in sequence - MPC-xx/LAV (32 and 64-bit) and insure it works - LAV will have most of what you need for decoding formats. Then MadVR (it is a unified 32/64-bit install) and working from defaults tweek it to your video watching needs. Finally get SVP4 and select the 32 and 64-bit options. Test it out for proper operation in 32-bit and move on to 64-bit is applicable. No codec packs needed and a lot less aggravation than the throwing everything against the wall approach and seeing what sticks.

Or better yet start from scratch after uninstalling all the various bits, pieces and patches you have accumulated and start fresh following one of the associated install guides. ex: HOW TO -Set up madVR for Kodi DSPlayer & External Players (http://forum.kodi.tv/showthread.php?tid=259188). Remember google is your friend wink

9

(186 replies, posted in Using SVP)

I think you'll find that taking Frames_interpolation_mode   = "3" (the 'adaptive' default setting) down to 2 will give you a little bit of that 24Htz film look.

10

(52 replies, posted in Using SVP)

Roberto Rossi wrote:

Complicated was indeed terrible, I've had bad times watching movies with it... it should be removed from the menu!

Was attempting to use SVP 4 x64 with Complicated last night on a video (1080P/25) that used to run without issue on SVP 3.1 (x32 layout) with Complicated and performance was horrible. Jittering and judder, massive frame drops - it appeared that more than simple performance issues were at fault.

To me it appeared that something was 'broke'. Keep in mind I run SVP via AviSynth/ffdshow raw video. I discovered if I dropped the CPU hog settings it would run but was taking a surprisingly high toll on the CPU (i7-3770@3.4GHz). Comparing SVP shader 21 with 23 (complicated) showed that the CPU ran about 30% higher with 23.

But the real issue was that 23 caused sudden CPU spikes (like 95-99%) when the video got busy (like a close pan over leaves in a tree). SVP shader 21 was a lot more stable in that regard. I suppose this is to be expected but I don't recall 23 being so demanding in SVP 3.1.

11

(52 replies, posted in Using SVP)

starks wrote:

I got everything working with Crimson drivers on my laptop.

Completely removed AMD 15.7.1 (last pre-crimson) and cleaned up afterward. Keep in mind that this version worked fine with SVP 4 although it created the following SVP error log warning

FFDShow: can't find system-wide installation

the video played well and GPU acceleration appeared by all events to be working. Have now reinstalled AMD Crimson 16.2.1 from scratch and it's back to no GPU acceleration and it errors out with the

AVS - SVSmoothFps: unable to init GPU-based renderer - code 65536

entry and the two \AppData\Roaming\SVP4\scripts\ errors with line 43 & 64. See attached SVP 4 error log file for details.

On a more positive note the weather underground gadget can now access the internet - no idea what fixed that issue since last AMD 16.2.1 driver install which broke it.

12

(52 replies, posted in Using SVP)

Fixed! Rolled back my AMD Crimson driver pack to pre-Crimson 15.7.1.

Looks like AMD still hasn't fixed the Open CL library issue even in the latest Crimson 16.2 hotfix driver pack sad . From my experience GPU acceleration doesn't buy me all that much - GPU load goes up ~5% and CPU load drops slightly. That's not a bad thing cuz I can use the extra GPU capacity for more madVR headroom and I do have extra CPU (i7-3770) capacity. So in the end it helps balance it all out in my case. Back to Crimson 16.2.1 hotfix.

FYI: Weird side effect of latest Crimson pack (not seen in 16.1.1) is that it somehow blocks my 'Weather Underground gadget' from internet access in the 'Sidebar' - yeah, I still use that functionality for GPU, CPU and Weather gadgets even though it's no longer supported.

13

(52 replies, posted in Using SVP)

mashingan wrote:
MistahBonzai wrote:

Anyone using ffdshow 64bit with SVPflow Avisynth+ scripting like the ones posted by yan04000985 http://www.svp-team.com/forum/viewtopic … 410#p57410 with MPC-HC? (he uses MPC-BE x64)

Wasn't your problem already over?
http://www.svp-team.com/forum/viewtopic … 265#p56265

Yes, but but even cleaning ffdshow 64-bit completely out and letting SVP 4 'upgrade' to ffdshow x64 it isn't helping this time. I think the issue reappeared when I re-upgraded from old Radeon to Crimson - now @16.2 hotfix. I'm gonna revert to 15.71 again and see how it plays out. I'm collecting all pertinent logs along the way. I wasn't gonna comment until done until I saw the post from Biff but I see he has NVIDIA/Windows 10. I'm AMD/Windows 7. Back to running more diagnostics...

14

(52 replies, posted in Using SVP)

biff wrote:

Hi: I'm getting the following error using MPC-HCx64 and SVP 64bit for Windows:

SVSmoothFps: unable to init GPU-based renderer-code 255(C:\Users\kbumm\AppData\Roaming\SVP4\scripts\d0990.avs, line 43)(C:\Users\kbumm\AppData\Roaming\SVP4\scripts\d0990.avs, line 60)(ffdshow_filter_avisynth_script, line 3)

I don't feel so alone now wink Same here. You don't happen to be using AMD 'Crimson' drivers?

15

(52 replies, posted in Using SVP)

SVP 4 (x64) is working fine with MPC-BE x64 smile However with MPC-HC x64 it continues to throw the same error concerning not being able to init the GPU sad (see attached screen clip). Just to recap..I had the same issue when running a manual config utilizing AviSynth scripts (MPC-BE x64 is fine while MPC-HC is a no-go with gpu:1 - fine with gpu:0). It's starting to look like a MPC-HC issue but no one else is complaining. Anyone using ffdshow 64bit with SVPflow Avisynth+ scripting like the ones posted by yan04000985 http://www.svp-team.com/forum/viewtopic … 410#p57410 with MPC-HC? (he uses MPC-BE x64)

Question(s):

  • Anyone using the new SVP 4 x64 variant with MPB-HC x64 with success?

  • If so did you use the complete manifest of SVP 4 optional software?

yan04000985 wrote:

Thanks svp-team update
Plugins, Script, reg setting download link:
https://mega.nz/#F!EVg1VDoR!tOVzSq1IptehyoKAbUvpeQ

Woot! Just made my day smile Gave the x64 a quick spin and works the balls. Your value selections are very close to what I've zeroed in on so it makes me warm and fuzzy about that. Your new scripts will take me a while to evaluate... Thanks again smile

I believe that one needs a MoBo and BIOS designed to support multi-GPU functionality. Otherwise, assuming one gets it working, they will end up as I did with 2 separate video streams with no sharing of the load.  I included 2 screen clips, one from the 'main' display and one from the extend display. The main display is connected to the AMD HD 7850 while the extended display is connected to the Intel HD500 (MoBo HDMI).

I can reverse the main/extended displays in the windows screen resolution settings and the GPU follows it - it interchanges the taskbar and such. Anyway, see the attached screen clips showing the status of the SVP 4 application settings. Bottomline is that it's kinda fun to mess around with but it does nothing to help share the video load. I have become really good at switching inputs on my Sony Bravia with the remote cool

After many hours performing countless GPU configuration tests (integrated intel HD4000 and discrete AMD HD 7850) I have come to accept that under windows 7/Direct X 11 the integrated & discrete GPU resources can't be shared but only assigned to specific displays. This means in my configuration I can enable GPU acceleration in SVP 4 in either display but the GPU assigned to that display does all the work while the other GPU sits idle driving the other display. Got That? wink

However Direct X 12 (Windows 10) brings a feature called Multiadapter will will allow DirectX 12 to use multiple GPUs. I guess that this is but one more reason to upgrade to Windows 10 (which, from past experiance, I know will bring new 'challenges'... Dammed if I do and left behind if I don't.

Nintendo Maniac 64 wrote:

The only thing is, I never know whether to install the integrated GPU drivers first or the discrete GPU drivers first...

Integrated 1st, make it primary then discrete GPU. Intel published a paper Hybrid Multi-Monitor Support: Intel® Embedded Platforms which can be found here: http://www.intel.com/content/www/us/en/ … paper.html

I'm beginning to think that this experiment might *not* be worth it considering the limitations it imposes upon my single monitor configuration. So far my tests are based on using 2 inputs and switching back and forth as GPUs are assigned to 'displays' (inputs). What i'm seeing is that in order to use the integrated GPU I need to launch the application from that input. Note: Drag and drop results in 'blue screens' - something I haven't seen in a long time.

Nonetheless I'm gonna try the 'official' installation procedure for the GPUs just so I know how it works in the real world smile

Nintendo Maniac 64 wrote:

Also, you do know that you can select which GPU to use in SVP, right?  It's in the same menu when you can disable GPU acceleration.

That's my problem - the Intel HD4000 doesn't appear in the SVP 4 > Application Settings > GPU Acceleration menu. The AMD HD 7850 is the only choice. It's like I somehow need to 'turn on' the HD4000. It shows as 'working properly' in the Device Manager. I'm not sure how to go about configuring it... Keep in mind that although I'm an old hand with PC building and repair I've yet to configure a rig with integrated and discrete GPUs. Thanks for all your help - I needed it smile

Nintendo Maniac 64 wrote:

I don't really know about your exact situation; all I know is that when you have the Intel GPU drivers installed then SVP can use the integrated Intel GPU while your discrete GPU can be used for things like MadVR.

Hey, thanks for the speedy reply! That's exactly what I want to know. Any idea where I might find a 'tutorial' or at least a place to get me going? I have the drivers installed and Intel QuickSync shows up now in the LAV Video Decoder as an available hardware decoder - I always select 'none' there 'cuz it seems like software does a better job (less issues). I have selected intel QuickSync and get no errors but it looks like the AMD HD 8750 is the only gpu (according to GPU-Z) with a load. QuickSync is there as well but no load when playing video. Once again a big THANK-U goes out to you smile

Nintendo Maniac 64 wrote:

If you have a CPU with integrated graphics, you could possibly use that instead of your discrete GPU...

My i7 3770 has integrated HD4000 however the MoBo BIOS has no toggle for internal/external graphics - the only means to enable the hD4000 was to disable (remove) the AMD HD 8750. I looked into Lucid Virtu back when I got the rig 4 years back and after reading the reviews I couldn't see a reason it was worth it.

However after your reply I looked into BIOS updates again (as I have many times in the past when so inclined). You see the AMI 7.* default (and only) BIOS for the h9-1180 Phoenix doesn't allow for anything other than the standard HD configs, power and security settings. Neither does the AMI 8.1 custom modded BIOS I acquired along the way.

Then last night I cross referenced the Pegatron MoBo against other HP desktop configs and came up with an HP specific version of the AMI 8.1 BIOS for a newer model.  Ah..what the hell..go for it... And it worked - so now I can see both GPUs in the device manager at once smile

Question: Is there a way to use both at once? Say use the HD 7850 for the display and the HD4000 for graphics pre rendering? Or vise versa?

I can confirm that the following error

While attempting to use the SVP 4 dlls (SVPFlow1 3.0.2.0 1/12/2016 - SVPFlow2 3.0.6.0 1/12/2016) from the latest 'free' download (4.0.0.60) within an avisynth script an access violation is returned by svpflow2.dll while attempting to read from the avisynth script (see the attached screen clip for the exact error message.

is fixed in svpflow-4.0.0.128 under windows 7 64-bit. Tested in x32 and x64 configs w/AviSynth+0.1 (r1779)

super_params     = "{pel:2,scale:{up:2,down:4},gpu:1,rc:true}"

with rc:true and rc:false. Thanks guys (Chainik?) smile

Now if I could only get the GPU:1 switch to work with x64 when using a HD 7850 w/Crimson 16.1.1. Running w/o GPU enabled is kinda lame with high resolution files when the x86 config with gpu:1 blows right by it sad I could revert back to pre-crimson but I really like the virtual resolution capability with Crimson.

BTW: I find that the x64 configuration is 'more stable' in the madVR-MPC-HC-ffdshow-avisynth chain than x32 variation so I'm hoping AMD gets their act together..and soon!

Fixed Change: rc:true to rc:false in the following script line...

super_params     = "{pel:2,scale:{up:2,down:4},gpu:1,rc:true}"

25

(8 replies, posted in Using SVP)

tac wrote:

Avisynth 2.6MT
SVP4 Free (4.0.0.60) (core.flow32 1.2.2)

5. Edit test.avs
      global super_params="{scale:{up:0},gpu:1,rc:true}"
        -> global super_params="{scale:{up:0},gpu:1,rc:false}"
6. Preview with AvsPmod. -> Success

HoLeeShit!! That is the 'tweak' I needed to know. My Avisynth scripts now run perfectly with the new SVP 4 svpflow dlls. For a couple of years I have wondered what functionality re:true/false toggled but could never find an answer in the documentation so I have always left it enabled. All I had to do was ask...  Thank you smile