1

(6 replies, posted in Using SVP)

dlr5668 wrote:
kona64 wrote:

yeah, because i use plex so i encode all my files beforehand... and like there are threads to help people chose hardware for plex, there should be some data to help ppl chose hw for svp!

thats easy. Wanna play with new optical flow or better NVENC quality -> pick cheapest turing card (RTX 2060 is the best) / else pick used Pascal

do you have any idea how AMD cards perform? just got my hands on an RX580 and wonder how it'll perform VS my 960 :shrug: AFAIK NVENC uses some separate HW IC and iirc maxwell and pascals NVENC hardware are pmuch the same, it's just turing's thats far far better.

2

(6 replies, posted in Using SVP)

yeah, because i use plex so i encode all my files beforehand... and like there are threads to help people chose hardware for plex, there should be some data to help ppl chose hw for svp!

3

(6 replies, posted in Using SVP)

Hey guys, so I've been having a hard time finding good data on what kind of GPU's people should but for SVP, and the only thing stated on the website is the kind of driver you gpu should use (in nvidia case).
So i was thinking we could all kinda pitch in an make a benchmark thread! anyone have any video we could all try encoding at idk 8mbps using NVENC and the AMD equivalent to try and see what kind of GPU's people should go for?
i use a 960 for most of my encoding on my plex machine(quite fast), and have encoded on my 2080ti just for kicks(very fast).

4

(2 replies, posted in Using SVP)

@MAG79
Issue solved with DDU removal of intel drivers, thanks a lot!

5

(2 replies, posted in Using SVP)

Hello; i recently reinstalled windows, running a clean windows 10 install on a high end PC and for some reason SVP won't open. Reinstalled several times, restarted several times as well; i'm at my wits end!
Event viewer gives me these two messages:

Faulting application name: SVPManager.exe, version: 4.3.0.157, time stamp: 0x5c13a849
Faulting module name: igdrclneo32.dll, version: 0.0.0.0, time stamp: 0x5a67b26c
Exception code: 0xc0000005
Fault offset: 0x00025fe4
Faulting process id: 0x3fcc
Faulting application start time: 0x01d4a114ce729221
Faulting application path: C:\Program Files (x86)\SVP 4\SVPManager.exe
Faulting module path: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_150c36a550ed11f0\igdrclneo32.dll
Report Id: 0db56b40-4262-48b0-9084-bc6129741f86
Faulting package full name:
Faulting package-relative application ID:


Faulting application name: clinfo.exe, version: 0.0.0.0, time stamp: 0x5bdae2ee
Faulting module name: igdrclneo32.dll, version: 0.0.0.0, time stamp: 0x5a67b26c
Exception code: 0xc0000005
Fault offset: 0x00025fe4
Faulting process id: 0x2fc4
Faulting application start time: 0x01d49f868804a712
Faulting application path: C:\Program Files (x86)\SVP 4\utils\clinfo.exe
Faulting module path: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_150c36a550ed11f0\igdrclneo32.dll
Report Id: 4d14cb02-04f5-47d1-9be3-9ffb9bbeda0d
Faulting package full name:
Faulting package-relative application ID: