Thanks, but still not working here. I'm using James D's "beta of x64 build."

Unchecking priority for ffdshow raw video filter and enabling built-in video processing filter (Always use) combined with "main.setup.potplayer.native = true" still doesn't work for Potplayer64 on my rig. Set it to "false", however, and it works fine.

Same issue here. Resetting it back to "false" gets Potplayer64 working again, but whether it's doing what its supposed to is anyone's guess.

On my computer, LAV "CUVID" works fine in the 64bit version of PotPlayer with SVP with every recent NVIDIA driver (I just tested this again on my computer with the latest NVIDIA driver). Alternatively, don't use LAV Video Decoder at all. LAV is more efficient but ultimately it doesn't appear necessary.

29

(3 replies, posted in Using SVP)

On my rig, PotPlayer 64bit runs fine with LAV video decoder set to "NVIDIA CUVID," whereas it freezes on the 32bit version. Besides that, sound is a bit better with the 64bit version.

Me too. Years ago, I had the same issue with my i5-3570k CPU. As I recall, I changed the PCI-E clock/timing/something-or-other, maxing it out to fix the problem.

31

(5 replies, posted in Using SVP)

Chainik's right no doubt, but I've been using the latest avisynth build for a few days now and it works great for me. Also, just installed the latest 24212 runtime packages and that also sped up performance significantly too for me.

See here for more:  http://forum.doom9.org/showpost.php?p=1 … count=2229

I'll give it a whirl. Cheers!

I'm not "handy with command line and/or coding" and I found the online how-to pages for MPV incomprehensible. If its going to be a royal PITA to set up properly, which is what it looks like so far, then I'll just stick with Potplayer 64bit for now. Thanks anyway guys.

Hey Chainik, any simple advice on how to get MPV to play 5.1 audio?

Potplayer in 64bit is fine. MPV does look better though, less haloing, for example.

Hi, I'm running the same Windows 10 build, same GTX 970, same Nvidia driver, same Potplayer, etc.
No problems here, so it's not those particular items causing the issue. Good luck.

37

(26 replies, posted in Using SVP)

Hi, I downloaded this file too and it seemed to played perfectly for me too with SVP.

I've had a similar experience. A few months ago when I applied the 4gb-patch to SVP 4 Pro Maintenance Tool, the anti-virus software Avira called it infected and deleted it automatically.

39

(12 replies, posted in Using SVP)

I use the 64bit version of PotPlayer with SVP and the results have been very good (lower CPU use, better picture quality) except for last week when it crashed my system three times and finally gave me a BSOD.

I don't know what caused that. It could have been the latest Nvidia driver, the latest Windows 10build, or a conflict between PotPlayer's DX11 option (which I no longer have set to "on") and SVP. Because the 64bit version works so much better than the 32bit version, I clean installed Windows 10 build 14342 and am running the 64bit version of PotPlayer on it again.

In a nutshell, I love the 64bit PotPlayer and SVP, but it may crash your system. If it does crash even once, my advice is don't persist and instead go back to the 32bit version or else you may get the BSOD which required me to do a clean install.

BTW, PotPlayer has its own internal version of something like ReClock in both the 32bit and 64 bit versions so I don't install or use ReClock anymore.

Also, I don't use MadVr anymore either because PotPlayer usually achieves nearly the same quality of picture using only 10% to 20% of my GTX970. MadVr will eat up 50% or more to achieve the same quality. Of course sometimes MadVr is better, but usually the quality is identical (I'm using a 55" 4k Samsung TV as my monitor, about one or two arms length from my face). Of course beauty is in the eye of the beholder so the decision to use it is up to you.

40

(10 replies, posted in Using SVP)

As I recall, only SVP 4 Pro and the earlier 3.1.7 version (which has more artifacts) offer the option of "uniform (max fluidity)" when it comes to frames interpolation mode. That's a deal breaker for me, because only the option of "adaptive" is available on SVP 4 Free. I want total smoothness and the difference is significant to my eyes so going pro was the way for me to go.

By the way, the latest versions of Potplayer (both 32bit and 64bit) act as if they have their own home-grown ReClock feature. They seem to now automatically provide the same smoothing function as ReClock.

64bit Potplayer, Madvr, and LAV works great for me. Worth giving it a try. (As MAG79 says, ReClock only works on 32bit Potplayer.)

Hi, I use PotPlayer.

ReClock + MadVR + Nvidia Driver 364.72 + 32bit Potplayer versions after version 1.6.6006 (released a couple of weeks ago) always crashes for me. The 64bit version of PotPlayer works fine and has better sound reproduction so that's what I use.

44

(8 replies, posted in Using SVP)

Watching movies using SVP and with my TV set to "59Hz" hugely removes artifacts for me too. A much improved viewing experience compared with 60Hz. Thanks for the heads up!

45

(6 replies, posted in Using SVP)

"Vapoursynth x64 for windows is coming. But 2160p will still require insane CPU"

So what would be the recommended CPU for this? 6 cores and above?

I think I encountered that memory leak using SVP 64-bit. After using it to watch a video, if I then open the Google Chrome browser and then try to open a new tab, my computer freezes and must be restarted. So it goes. A work in progress. I'll try again when SVP 64-bit is updated. Cheers...

Fixed! Rolled back my NVIDIA driver to version 361.43  Thanks for the input guys.

Nah, I'm using NVIDIA 362.00 on a GTX970

So, Chainik, is this a Windows 10 issue, maybe? (I'm using the latest build 14279)

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)

Correction: solved most of my slowdown issues. Not all. Busy scenes on some movies go into slow motion still. Oh well...