1

(5 replies, posted in Using SVP)

Thanks, QuickSync is even better. It's actually crazy how much performance I'm getting.

2

(5 replies, posted in Using SVP)

Specs: i5-6600k at 4.3 ghz, 16 gb ram at 2600 mhz, 980 Ti at stock, win 10. Using MPC.

A few months ago I got a 1440p 144hz monitor, and since then I've struggled with frame drops. Running both SVP and madVR with some exotic upscaling is quite taxing, but even though CPU and GPU were never above 80% usage I would sometimes get up to ~30 frames dropped every second depending on what I was watching, even if I turned a lot of settings down. My guess is that this is some memory bandwidth limitation somewhere.

Today I find something of a solution, if I turn off hardware acceleration in the LAV video decoder instead of using DXVA copy-back I get no frame drops unless I really crank up SVP/upscaling settings.

I haven't noticed any issues yet, but I'm just wondering if there's likely to be some problem with it. I thought I remembered reading somewhere that copy-back is required.

3

(13 replies, posted in Using SVP)

Seems the latest drivers fix it, but if they don't or you don't want to update the fix seems to be to turn on "optimise for compute performance" (under "manage 3d settings") and set physx to use your GPU (under "configure surround, physx", you should do this anyway regardless of SVP)

4

(0 replies, posted in Using SVP)

I saw Chainik question the use of ffdshow audio in this thread and it got me thinking about my own filters. I'm using ffdshow audio but I have no idea why. I don't remember setting it up, same story with AC3Filter which I don't even remember ever using before. Some time ago I uninstalled everything and did a fresh install of SVP, so I don't know why these things are here.
Are these leftovers from something else? How do I get rid of everything I don't need and just use defaults?

Filters currently loaded:
  - Default DirectSound Device
  - madVR
  - Audio Switcher
  - ffdshow raw video filter
  - AC3Filter
  - ffdshow Video Decoder
  - ffdshow Audio Decoder
  - LAV Splitter (internal) (low merit)
  - File Source (Async.)

These are the settings I came to after a lot of tinkering http://i.imgur.com/lvLVIkn.png
The only time I really notice artifacts is around the edge of the screen when it pans very quickly.
You can try masking off completely but I feel like weakest is pretty good, you can also try complicated shader but it sometimes misbehaves for me.

But really, it's pretty personal what looks good to each person so maybe play around with it.
Yes I set my monitor to 71.928 Hz to watch anime.

edit: oh I should have mentioned, I have an overclocked 6600k and a 980Ti. In your SVP settings go to application settings > gpu acceleration > choose your GPU.

6

(70 replies, posted in Using SVP)

Completely agree.

Very good points. For your 3rd point, you can still use restart.exe while you are testing out, it's a pain to do a full restart every time you change the refresh rate by just a few Hz.

Edit: as to the risk, it's really not as much a risk as overclocking other things. I've never heard of anyone overclocking a monitor and breaking it.

8

(45 replies, posted in Using SVP)

Nintendo Maniac 64 wrote:

You are only working with exact multiples, right? (x2, x3, x4, etc).

Yep.

This guide is mostly for windows users with a 60 Hz display, but hopefully others will find it useful as well.

Most video source frame rate is 23.976, but most displays are 60 Hz. How do we get from 23.976 to 60?

SVP will multiply by 2.5 to get 59.94 which is not the best. Ideally we want SVP to be able to multiply by a nice round number.

This is where Custom Resolution Utility comes in.

The first thing to do is find out how high your monitor can be overclocked. Most 60 Hz monitors can be overclocked to around 75 Hz.
Start CRU, at the top make sure the drop-down is set to your monitor, and if you use an Nvidia GPU at the bottom change "default extension block" to "custom extension block."
In the Detailed Resolutions box delete anything that isn't 60 Hz, then click Add.
Change the Timing to LCD reduced, then in Refresh rate enter some starting place, you might want to try 75.
Click OK, and OK again to close CRU. Run the tool that comes with CRU called restart.exe, this will restart your display driver so you can use the new setting without a system restart.
Change your Windows settings to use the new refresh rate.

If your monitor shows an error like "outside of range" or similar, or you see artifacting, or this test reveals ghosting, then your monitor can't handle that refresh rate.
Go back to CRU, edit the detailed resolution you added, change to LCD reduced again, and change the refresh rate up or down. Repeat until you find your maximum refresh rate.

Once you know your max, you want to take the source frame rate of whatever you're watching and multiply it by an integer to find a number below your max. For me in the case of a 23.976 fps video, this is 23.976 x 3 = 71.928.
In CRU create a new detailed resolution for this refresh rate. You'll notice on the right of where you enter the refresh rate it says the actual refresh rate you will get, you might need to target slightly lower with what you enter, if it gets you closer to your desired refresh rate.

That's pretty much it! When you are watching something change your refresh rate to the one that suits your source frame rate. If you're watching something that has variable frame rate or weird encoding that confuses SVP, change your SVP settings to use the multiplier rather than using "to screen."

10

(45 replies, posted in Using SVP)

I've done a lot of tinkering and found that these are the best settings for anime. You do get a little bit of artifacting around moving objects occasionally, but I find that easily ignorable and well worth the tradeoff. These settings are quite demanding for some anime, they do tax my system which is an overclocked i5-6600k and 980 Ti.

I've actually found that complicated shader is worse in most circumstances, it can cause panning shots to stutter and other weird effects.

11

(12 replies, posted in Using SVP)

Well that's a real bummer, I'll have to work out some way of getting a non-admin cmd running at will.

12

(12 replies, posted in Using SVP)

Huh, that's weird. There's no mpc-hc in my system32.

Oh wait... aha, it's because I was running it from elevated command prompt. When I run from a normal limited command prompt it works fine.

13

(12 replies, posted in Using SVP)

It's the version that comes with SVP, located at E:\Program Files\SVP\MPC-HC\mpc-hc.exe

That's the location of the executable that task manager gives me, and it's the location configured in livestreamer's settings. It's the same version as when I play a local file.

14

(12 replies, posted in Using SVP)

Oh and this is what it looks like when it works normally with a local video file:

23:17:43.861; Performance statistics:
  Waiting for ffdshow video
  CPU usage 2%  Duration: 0:47  SVP Index 0x
  Memory used at start:0 at end:0 stable
23:17:43.864; ===== Detected playback with ffdShow. AppName: mpc-hc.exe, PID: 6844, supports 4GB RAM
23:17:43.875; used avisynth.dll: Avisynth MT, 2.5.8.6 (SVP edition) (CRC32:5ED58E27) from e:\Program Files\SVP\MPC-HC\
23:17:43.878; GetDimensionAndFPS_fromOSD start. Duration: 150 ms
23:17:44.028; GetDimensionAndFPS_fromOSD result: 1280x720 23.976 1/1
23:17:44.032; T1T: begin
23:17:44.035; T1T: GetAllMediaParams
23:17:44.038; ### CorrectStereoModeByAppAndFilename: test.mkv
23:17:44.040; T1T: SettingsPrepare. Duration: 6 ms
23:17:44.046; T1T: Preparing smooth playback...
23:17:44.049; T1T: WriteAllMediaParamsToIni
23:17:44.051; SVPMgr: play "C:\ProgramData\SVP 3.1\" avs x86. Duration: 66 ms
23:17:44.117; Selected profile: 1280x720@24. Duration: 7 ms
23:17:44.124; ===== Playback
23.976 * (5 : 2) = 59.94 fps
23:17:44.126; SetPriorityPlayer: 2. Duration: 700 ms
23:17:44.826; frame #4 crop detected: 0 0 0 0
23:17:44.829; frame #5 crop detected: 0 0 0 0
23:17:44.833; frame #6 crop detected: 0 0 0 0
23:17:44.836; frame #7 crop detected: 0 0 0 0
23:17:44.839; frame #8 crop detected: 0 0 0 0
23:17:44.842; frame #9 crop detected: 0 0 0 0
23:17:44.922; frame #10 crop detected: 0 0 0 0
23:17:44.926; frame #11 crop detected: 0 0 0 0
23:17:44.929; frame #12 crop detected: 0 0 0 0
23:17:44.933; SVPMgr: play "C:\ProgramData\SVP 3.1\" avs x86. Duration: 57 ms
23:17:44.990; Selected profile: 1280x720@24. Duration: 9 ms
23:17:44.999; ===== Playback
23.976 * (5 : 2) = 59.94 fps
Auto crop: [0:0:0:0] . Duration: 1202 ms
23:17:46.201; ===== Playback
23:17:50.700; FalseVFR ffdShow-framerate: -Dwn-> 18.859 -Dwn-> 15.415 -Up-> 22.247 -Up-> 23.729 -Up-> 23.976 fps
23:17:50.703; express clear interval
23:17:50.705; stabilized ffdShow-framerate: 23.976 fps. SVP Index: 1.01/1.02
23:17:55.858; RefreshSVP
23:17:55.861; Performance statistics:
  Playback: 1280 x 720 @ 23.976 * (5 : 2) = 59.94 fps
  CPU usage 31%  Duration: 0:10  SVP Index 1x
  Memory used at start:719 at end:719 stable
23:17:55.870; ===== Waiting for ffdshow video

15

(12 replies, posted in Using SVP)

OK log below, at 21:18:06 21:25:22 and 22:23:43 I started a twitch stream using pipe (default settings).
At 23:02:24 I played a youtube video (default settings).
At 23:06:09 I started a twitch stream using http.
All through livestreamer.


13:46:19.552; Start: SVPMgr 3.1.7 (70) starts...
13:46:19.552; AppDataPath: C:\ProgramData (ANSI)
13:46:19.552; Start: read settings file settings.ini
13:46:19.552; Start: load language file - English. Duration: 329 ms
13:46:19.881; Start: check Avisynth installed
13:46:19.881; Start: clear Logs folder. Duration: 15 ms
13:46:19.896; Start: CPU and threads count detection
CPU: Intel Core i5-3470 @ 3.20GHz [4 threads] (1338)
13:46:19.896; Start: SVPMgr folders prepare. Duration: 141 ms
13:46:20.037; Start: read settings file SVPMgr.ini
13:46:20.037; Start: GPUs settings detection
GPU_11: AMD Radeon HD 7800 Series (3200)
13:46:20.709; Start: monitors settings detection
Display#00010001: 1920 x 1080 @ 59
13:46:20.709; Start: disable LNG-file write when UAC enabled
13:46:20.709; Start: change SVP-manager priority
13:46:20.709; Start: register hotkeys. Duration: 234 ms
13:46:20.943; Start: get versions of modules used
ffdshow.ax: 1.3.4533
avisynth.dll: Avisynth MT, 2.5.8.6 (SVP edition) (CRC32:5ED58E27)
svpflow1.dll: 2.0.4
svpflow2.dll: 2.0.2
13:46:20.943; Start: refresh autostart state in registry
13:46:20.943; Start: some more work with registry
13:46:20.943; Start: create menu. Duration: 63 ms
13:46:21.006; Start: update settings file settings.ini. Duration: 15 ms
13:46:21.021; Start: prepare "About the program" window. Duration: 125 ms
13:46:21.146; Start: enable ffdShow waiting mode
13:46:21.146; Start: prepare to work is complete
13:46:21.146; RefreshSVP
13:46:21.146; ===== Waiting for ffdshow video

19:20:25.048; Screen mode change detected
Display#00010001: 1920 x 1080 @ 59
19:20:47.755; Screen mode change detected
Display#00010001: 1920 x 1080 @ 59
19:21:45.098; Screen mode change detected
Display#00010001: 1920 x 1080 @ 59
19:33:50.352; Screen mode change detected
Display#00010001: 1920 x 1080 @ 59
19:37:46.964; Screen mode change detected
Display#00010001: 1920 x 1080 @ 59
19:43:37.278; Screen mode change detected
Display#00010001: 1920 x 1080 @ 59
19:56:45.449; Screen mode change detected
Display#00010001: 1920 x 1080 @ 59
20:00:04.556; Screen mode change detected
Display#00010001: 1920 x 1080 @ 59
20:00:31.417; Screen mode change detected
Display#00010001: 1920 x 1080 @ 59
20:01:06.938; Screen mode change detected
Display#00010001: 1920 x 1080 @ 59
20:23:27.816; Screen mode change detected
Display#00010001: 1920 x 1080 @ 59
20:23:28.394; Screen mode change detected
Display#00010001: 1920 x 1080 @ 59
20:50:08.163; Screen mode change detected
Display#00010001: 1920 x 1080 @ 59
21:02:46.024; Screen mode change detected
Display#00010001: 1920 x 1080 @ 59
21:02:46.540; Screen mode change detected
Display#00010001: 1920 x 1080 @ 59
21:18:06.281; Performance statistics:
  Waiting for ffdshow video
  CPU usage 9%  Duration: 7:31:45  SVP Index 0x
  Memory used at start:0 at end:0 stable
21:18:06.283; ===== Detected playback with ffdShow. AppName: mpc-hc.exe, PID: 4916, supports 2GB RAM ONLY. Patch video player executable with "4GB Patch"
21:18:06.408; used avisynth.dll: Avisynth MT, 2.5.8.6 (SVP edition) (CRC32:5ED58E27) from C:\WINDOWS\system32\
21:18:06.414; GetDimensionAndFPS_fromOSD start. Duration: 729 ms
21:18:07.143; ===== The player is in pause state

21:25:22.148; Performance statistics:
  Waiting for ffdshow video
  CPU usage 9%  Duration: 7:15  SVP Index 0x
  Memory used at start:0 at end:0 stable
21:25:22.150; ===== Detected playback with ffdShow. AppName: mpc-hc.exe, PID: 4788, supports 2GB RAM ONLY. Patch video player executable with "4GB Patch"
21:25:22.162; used avisynth.dll: Avisynth MT, 2.5.8.6 (SVP edition) (CRC32:5ED58E27) from C:\WINDOWS\system32\
22:23:43.158; Performance statistics:
  Waiting for ffdshow video
  CPU usage 6%  Duration: 58:21  SVP Index 0x
  Memory used at start:0 at end:0 stable
22:23:43.161; ===== Detected playback with ffdShow. AppName: mpc-hc.exe, PID: 4560, supports 2GB RAM ONLY. Patch video player executable with "4GB Patch"
22:23:43.172; used avisynth.dll: Avisynth MT, 2.5.8.6 (SVP edition) (CRC32:5ED58E27) from C:\WINDOWS\system32\
23:02:24.658; Performance statistics:
  Waiting for ffdshow video
  CPU usage 8%  Duration: 38:41  SVP Index 0x
  Memory used at start:0 at end:0 stable
23:02:24.661; ===== Detected playback with ffdShow. AppName: mpc-hc.exe, PID: 5680, supports 2GB RAM ONLY. Patch video player executable with "4GB Patch"
23:02:24.672; used avisynth.dll: Avisynth MT, 2.5.8.6 (SVP edition) (CRC32:5ED58E27) from C:\WINDOWS\system32\
23:06:09.158; Performance statistics:
  Waiting for ffdshow video
  CPU usage 6%  Duration: 3:45  SVP Index 0x
  Memory used at start:0 at end:0 stable
23:06:09.161; ===== Detected playback with ffdShow. AppName: mpc-hc.exe, PID: 6872, supports 2GB RAM ONLY. Patch video player executable with "4GB Patch"
23:06:09.173; used avisynth.dll: Avisynth MT, 2.5.8.6 (SVP edition) (CRC32:5ED58E27) from C:\WINDOWS\system32\

16

(12 replies, posted in Using SVP)

pipe, I did try http but only one time, so it could be both

17

(12 replies, posted in Using SVP)

It happens with any Twitch stream, when it breaks again I'll test streams from other sources.

Where do I find SVP's log?

This is my livestreamer config (again, I'll test default settings when it breaks):
player="E:\Program Files\SVP\MPC-HC\mpc-hc.exe"
ringbuffer-size=64M
hls-segment-threads=3
hls-live-edge=4

18

(12 replies, posted in Using SVP)

When I first install SVP, it will correctly work whenever I open any stream through MPC with livestreamer. However, after a short time (maybe 1 day) it will stop working. When I open a stream the SVP icon will either say "waiting for ffdshow video" or it will say something like "the player is in a paused state" (I don't remember exactly the wording it uses).

I don't touch any settings at all and this happens. I don't even restart my PC and it happens. To fix it temporarily all I need to do is reinstall SVP.

There are no other codecs or filters installed on my PC other than what comes with SVP.
I'm using the MPC that comes with SVP, there are no other copies on my PC.
Windows 8.1 x64.