26

(122 replies, posted in Using SVP)

blabb wrote:

Interestingly I haven't had a single crash with 4.0.0.74 so far. Although I'm not sure if that's due to the version or I finally found a combination of settings/components that work for me.
I have sent you a bug report through SVP, maybe that helps.

You mean that after forcing "Animation" on as Chainik proposed you did not experience crashes anymore?
I would also check this tonight but I was a little bit afraid since launching 4.0.0.60 (the one provided by Chainik) instead of installed 4.0.0.74 at windows start-up and make it persistent was a real pain for me

27

(122 replies, posted in Using SVP)

Hi, any news on this front?

28

(122 replies, posted in Using SVP)

One dumb question though: x64 is supposed to work also for 4.0.0.60? I'm asking this because the version supplied by Chainik only works with x86 for me ... when I try to launch in MPC-HC x64 I see that ffdshow raw is used but SVP is saying "No active playback" !?

29

(122 replies, posted in Using SVP)

@blackfyre

I can try all this tonight. However I'm afraid that increasing the queues size (for this one I'm not sure), using frames presented in advance and un-ticking everything in TQP might be too much for my Haswell based iGPU HD 4400. The best config. for me, with 1 drop frame every 2-3 hours, was with backbuffers and old path D3D9, everything ticked up to "scale chroma separately" in TQP, exactly the opposite for the first 2 options in general settings meaning to be un-ticked and automatic fullscreen exclusive mode to be ticked.

30

(122 replies, posted in Using SVP)

Hi again,

Just a small update: I've used the 4.0.0.60 version provided by Chainik and everything is butter smooth now, GPU acceleration is ON in SVP, I can use more aggressive madVR options and ... no more crashes at all. It still show however "No active playback" for MPC-HC x64 although ffdshow raw is active but anyway I'm using it with the x86 version and everything seems ok now.

@MAG79 Looking forward also for an updated version with the bug fixed. Thanks for all your efforts!

31

(122 replies, posted in Using SVP)

My point also, w/o GPU acceleration I'm quite borderline considering the very weak CPU. However what I struggle to understand is why lowering madVR settings helped also here since that is pure GPU bound ... Could it be that w/o the help of GPU SVP needs more time to interpolate frames to 59,940 and thus madVR which comes after is more squeezed with rendering times? I've noticed higher render times and even spikes above the 16ms threshold now while when GPU was used for SVP the render times in madVR were significantly lower ?! All in all I only see 2 options here for me: either downgrade to a working SVP with GPU acceleration or put everything to bare minimum in madVR.

32

(122 replies, posted in Using SVP)

Blackfyre wrote:

This type of crash with GPU Acceleration started happening between version 4.0.0.60 and version 4.0.0.73 (I don't know when or where, but it happened in that time frame, and it's also related to processing threads). Changing some settings around I can make it start hanging instead of crashing, but the problem is there. It never happens with 4.0.0.60 (not for me, and not yet anyway, for almost a week now I've been using 4.0.0.60 Pro, with my custom settings).

Ok, I will give a try to 4.0.0.60.

Since I disabled GPU acceleration I've also noticed some "strange things": instead of helping madVR by releasing more resources it was exactly the opposite, I've noticed a lot of glitches / "shaking frames" with 1080p material until I've made some aggressive changes in madVR settings like:
- no dithering,
- check all boxes to the bottom in trade quality for performance,
- use old path D3D9 and backbuffers
- and even dropping Bicubic 75 AR for chroma scalling / every scalling is now forced to DXVA
(anyway even with all the above is a night and day difference between madVR and EVR-CP quality / my best guess being that by using DXVA scalling on Intel iGPU which is very similar to Lanczos 3 Taps the image gets more crisp which I kinda like it ...)

The thing gets more weird since GPU-Z only shows 24% GPU usage in windowed mode so I assume that in fullscreen mode it cannot go too much higher which mean there are still plenty of resources left for madVR but I cannot use them ... is like  SVP magic done only on my poor CPU (dual core Core I3 1.7 GHz) do not get along very well with madVR.

Anyway with all the above now everything is working smooth with 1 frame repeat / drop every 2.4 hrs in madVR stats.

Other strange stuff noticed is that during my mumbling with the settings in SVP I have noticed that it was sometimes interpolating 1080p23 movies at 64,1.. instead of 54,940. Only a PC restart is fixing the problem.

33

(122 replies, posted in Using SVP)

Chainik wrote:

ionutm80

could you post a report via the Manager just after the crash will occur next time?

Hi Chainik,

I have sent the report via the Manager (e-mail signed ionutm80) and also inserted the crash log:

ntdll!RtlpAllocateHeap+0x1b1b
ntdll!RtlpAllocateHeapInternal+0x27b
ntdll!RtlAllocateHeap+0x2e
WARNING: Following frames may be wrong.
svpflow2!AvisynthPluginInit3+0xaa73
svpflow2!AvisynthPluginInit3+0x88d1
svpflow2!svpGetVersion+0x23d4e
svpflow2!svpGetVersion+0x1af49
svpflow2!svpGetVersion+0x182b9
svpflow2!svpGetVersion+0x18261

However I think that I have narrowed down the problem. I have deactivated GPU acceleration with the trade-off of being forced to lower the quality / moved the slider one step backward ... but no more crashes anymore and tested twice with 3 resolutions: 1080p, 720p and 576p movies all on my 768p 60Hz TV.
Maybe madVR and SVP were fighting on resources?

34

(122 replies, posted in Using SVP)

Chainik wrote:

ionutm80

could you post a report via the Manager just after the crash will occur next time?

Ok, I will try tonight.

35

(122 replies, posted in Using SVP)

Hi,

I want to join the topic by sharing the same problem referring to crashes linked with SVP.
So here is mai config:
Intel NUC Core I3 4010u, HD Graphics 4400, 8 GB DDR3 1600, Win 10 x64.
SVP 4 Pro 4.0.0.74 (updated last night), GPU acceleration used.
Everything clean installed through SVP installer: MPC-HC, madVR, avisynth, etc.
TV Sony resolution 1366x768, 60 Hz
The crashes occur when playing 1080p on my TV, I haven't noticed any crash with mkvs from 576p PAL DVDs.
madVR is using only DXVA scalling and is optimized at max for performance, all queues are below 16ms needed for 60 fps after SVP so no issues here (by the way w/o SVP playback is butter smooth).
My guess is that the issue is somehow related to playing higher res movies on lower res displays with Intel VGAs (like in my case 1080p --> 768p or 2160p --> 1080p like in the posts above ...).
Similar error as posted by user blabb:

kernelbase!RaiseException+0x58
WARNING: Following frames may be wrong.
svpflow2!AvisynthPluginInit3+0x8960
svpflow2!AvisynthPluginInit3+0x8904
svpflow2!svpGetVersion+0x23d4e
svpflow2!svpGetVersion+0x1af49
svpflow2!svpGetVersion+0x182b9
svpflow2!svpGetVersion+0x18261

Can you please double check what is happening?

Another issue I have is that SVP does not load in MPC-HC x64 although I have installed al x64 dependencies with the SVP installer, all settings done correctly (ffdshow raw x64 added in exyernal filters). Is there an issue maybe due to the fact that I have Win 10?

@Nintendo Maniac 64
Regarding AMD path we are already poluting this forum, I have plenty of arguments against it but this could be only my personal experience (it was my first HTPC attempt based on Asus E35M1-I Deluxe, passively cooled). Anyway we should debate on this topic in another place. smile

Anyway thanks again for all the hints given!

37

(5 replies, posted in Using SVP)

MAG79 wrote:

Selection option in menu appears if detected 2 or more GPU OpenCL devices. If one of your GPUs don't have OpenCL-driver then it can not be used by SVP, so you don't see selection option.
Usually HD 2500 needed to install official driver from Intel site to get OpenCL compatibilities. Default windows-driver have not OpenCL part for Intel HD Graphics.

About GPU-acceleration in SVP. HD 2500 is good for SD resolution video only. For HD and higher I recommend to use discrete GPU.

Ok, point noted. My hopes just vanished sad .

38

(5 replies, posted in Using SVP)

Chainik wrote:

In multi-GPU systems SVP uses one that is selected in the menu...

You mean the ones listed in SVP 4 menu? I cannot find anything similar in SVP 3.1.7 menu ... or am I not looking right?

39

(5 replies, posted in Using SVP)

Hi,

I have a small dilemma regarding a system where you have 2 GPUs: a dedicated one (let's say in my case a GTX 750 TI) and an integrated one (a HD 2500 in an Ivy Bridge CPU). So here comes the 2 questions:
1. If I use the iGPU DXVA option in the decoder (LAV Video - Intel QuickSync, it shows as available in Win 10) does this mean that SVP will also use it for a G profile (I have 4G) and leave the dGPU (GTX 750 TI) fully at the renderer discretion (madVR) ? For the moment I'm using DXVA Copy-Back in LAV Video which I think make use of the GTX 750 TI and I would like to leave every drop of power available for madVR instead.
2. If 1. is true would a Intel HD 2500 power be sufficient for SVP needs at 4G profile?

Thanks,

Hi, I dropped AMD path long time ago after having some pretty bad experience with an E-350 Zacate as my main HTPC. Drivers were so bad that I could not believe what damage they were doing to image, simply the colors were crap ... not to mention the poor implementation of DXVA, high power consumption for my taste, etc. I've dropped it and went for Pentium G620 with Intel HD Graphics at that moment and ... finally the colors came to life. Never looked back to AMD ever since. Maybe in the meantime things have changed but I will stick to Intel for now on. I've purchased the NUC due to its form factor, at that moment there was no AMD Kabini or something similar with those dimensions. Now, indeed there are better alternatives ...

Anyway for my main HTPC I'm using a GTX 750 TI which at the moment is the best bang for buck in terms of consumption, low profile iterations and sufficient power for HTPC and light gaming. I'm running it together with a Core I5 3470S from a PicoPSU-160XT 192W and OCCT Power stress test put the system at max 138W at the wall measured with a watt meter.

To answer your question about 2C, the Core I3 4010u is only 1.70 GHz sad which is still far from the min. 2.00 GHz recommended, so no profile w/o GPU help is possible.

I've tried to push the limits according to what you suggested and by only looking at the stats in madVR, SVP, ReClock, GPU-Z ... I was fooled in considering it was possible to achieve more but was not thr case. What I suspect in fact is that after you push certain limits on the iGPU HD Graphics 4400 it starts to become less stable. Why am I saying that, I've spotted that once you pass 60% combined load with SVP and madVR things start to get nasty leasing to drpped frames increasing dramatically. Maybe it is due to power limitation or some safety caps implemented by Intel to avoid over heating ... I really don't know. But the point is that GPU load should be max around 60% to avoid jerky playback on these puny devices. For me is a case closed, anyway is not my main HTPC.

Hi again, no it was not possible. Only 1g profile with plenty of trade quality for perf in madVR ... but still visible improvement in image sharpness and colors vs EVR-CP.

Hi,

Just a short update. I have managed to lower the madVR usage to the point that it interacts well with SVP on my poor NUC by following some hints received on madVR thread at Doom: use old path with backbuffers instead of new path with frames presented in advance. This together with Chroma DXVA dropped the GPU usage significantly ...

44

(11 replies, posted in Using SVP)

Hi again,

I came back with another nasty issue. This time between Kodi DSPlayer fullscreen and SVP. I have already asked about it on Kodi forum but the only reply I got was to use my TV to interpolate frames ... meaning probably to not use SVP ... but never mind.

I have tested this on both my 2 HTPCs: the one with Core I5 3470s+GTX 750 TI and the NUC and the behavior is the same ...

What happens: each time I play a 1080p movie in Kodi on my 1080p TV 60Hz I see a strange zoom taking place immediately after SVP starts to interpolate frames up to 59.94 and madVR stats shows that image upscalling is taking place. Normally this should not happen, only Chroma should be upscalled as madVR shows in MPC-HC. But with Kodi, after the zoom happens I see image upscalling with Jinc for a 1080p movie on an 1920x1080 screen (!?) and of course dropped frames start to increase and CPU load is sky rocketing.

To my surprise immediately after I disable SVP, everything went butter smooth with Kodi + active madVR profile leading to 0 dropped frames. It seems that there is a problem when Kodi fullscreen interacts with SVP after the former starts to interpolates frames up to 59.94 (TV resolution is 60 and movies are all blu-ray rips at 23,976).

This behavior only appears with Kodi DSPlayer, in MPC-HC everything works as expected.

45

(25 replies, posted in Using SVP)

@dlr5668

Why don't you use Image Doubling? Something like NNEDI 32 neurons.

Hi, I'm aware of the scaling done in MPC-HC but my goal is still to keep madVR. Trust me, I've watched with EVR-CP + scaling Bicubic in MPC-HC and the colors and sharpness are nowhere near what I get with madVR. I did a print screen of a scene in Gravity from the beginning of the movie with both config and compared the images, it's like watching a different movie.

Regarding the TV, yes it's a poor 26 inch model so nothing to expect here even if it's branded Sony (2011 model by the way).

I've also ripped the Hobbit last part to an mkv (video and audio left untouched) and tested intensively with my current config. At 1g I still get spikes of 95-99% CPU usage with SVP at the beginning of the movie. In madVR I have done all the tweaks possible to increase performance (debanding off, dithering off, image doubling off, image up/down done in DXVA, checked most of the options in trade quality for performance including DXVA for chroma) and GPU load is now in the range 50-60%. What I have also noted is that if I pause the movie for couple of seconds the CPU load stabilizes between 67-75% with spikes around 80-85% and there is a very smooth experience thereafter. Is there any option to even downgrade 1g level in SVP a little bit so that the CPU does not record the spikes mentioned above? I know for sure that 2g is out of discussion at this moment. If I install back SVP 4 what would be the equivalent of 1g and would it be more easily to downgrade a little until i found the sweet spot?

Hi,

You're right but priority goes to stability and then to squeezing the last drop of performance. When I started the thread I thought that I had a pretty smooth playback just by looking at different stats and ... I forgot to actually look at the movie and see the stuttering (my screen was filled with GPU-Z, performance graphs from SVP and ReClock ...). Once I figure the sweet spot for CPU and GPU queue size I will try again your settings for 2g profile. Scaling done by my TV (it does have a XReality engine but not the one from the top range) is quite poor I might say, the images look washed and there is a clear lack of sharpness for my taste. With madVR we are talking something different, is like the colors come to life and the sharpness is there ... I know for instance that DXVA scaling with Intel iGPU is based on / or similar to Lanczos with some form of anti-ringing.
Regarding resolution and refresh rates for my TV: yes it accepts everything up to 1366x768 from 24Hz to 60Hz.

Anyway thanks a lot for your input, I will revert with feedback after I test again your settings for 2g. And maybe this time I'm more lucky downloading your sample files.

Both in fact, no more stuttering but indeed SVP still at 1g. Maybe the max queues are a bit exagerated but I will try to reduce them step-by-step until I find the sweet spot. I still do not get how come this helped in my case. I could though understand that lowering the number of frames presented in advane was really helpfull.

Hi,

MPC-HC automatic resolution changer: tried that some time ago but I was not very successful.
Anyway I think I might have solved my problem. I have just spotted that my "present queue" was showing 5-7/8 instead of 7-8/8 so I decided to drop the frames presented in advance from 8 to 4 in fullscreen mode and from 8 to 3 in windowed mode. Also in the tab trade quality for performance I've checked the first 4 options up to "store custom pixel shader ..." ... and voila my "present queue" was now 2-3/3 and the stutter was almost non percievable. Then I remember an article on Anandtech where they tested the NUC (the Core I5 version) with madVR and used "CPU and GPU queue sizes of 128 and 24". I said why not try, did that and no more stutter visible, madVR shows 1 drop frame every 1.02 days and SVP performance graphs show CPU average at 67% with 1g profile. Indeed the guys at Anandtech also increased the frames presented in advance to 16 ... and this is where I'm a bit lost. They have practically maxed everything.

http://www.anandtech.com/show/7566/inte … c-review/5

But in my case the higher frames presented in advanced seemed to have been the real issue while the CPU and GPU queues only improved an already good situation (1 frame repeat every 3.7 hours --> 1 frame drop every 1.02 days).

Thanks a lot for your help and I will test with more videos and maybe ask a question on madVR forum.

Hi,

I have a very fast connection line 100Mb per sec but who knows ... sad

Blu-Rays: 1920x1080, 23,976fps
DVDs: 720x576, 25,000fps (PAL)
S4: 1920x1080, 29,911fps

In madVR should I play with the CPU/GPU Queue Size and frames presented in advance? For the moment I have standard settings: CPU queue size at 16, GPU queue size at 8 and frames in advance at 8 for both windowed and exclusive. What do you recommend here? I have noticed that my decoder and presenter queues are not always fill (10-15/16 and 5-7/8 if I remember well ...). I do not have a print screen now available but I can do one tonight.