Chainik wrote:

if only you could narrow it down to the exact filters args that give a crash...

I hear you but the best I can do now is that:

  • The error statement is: Avisynth: access violation at 0x0001BC2E in C:\Program Files (x86)SVP 4\plugins\svpflow2.dll, attempting to read from 0x00000000 (ffdshow_filter_avisynth_script, line 43

  • Line 43 where it all comes together - SVSmoothFps(input, super, vectors, smoothfps_params, mt=threads) #LIne 43 - not surprisingly ;^}

Keeping an eye out for the updates smile Thanks!

I think this is outside the scope of this forum but I know there are still a few 'script monkeys' out there wink

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. Note: the error is at line 43 and not line 44 as shown in the clip). MPC-HC plays the video without the script fully executing and MPC-HC crashes when closed. The application configuration is 32-bit MPC-HC-madVR-LAV-ffdshow (32-bit end-to-end). When using the same script/configuration with the earlier svpflow dlls (SVPFlow1 2.0.4.0 7/8/2015 - SVPFlow2 2.0.3.0 10/30/2015) run with out issue - no problems.

I can mix/match the appropriate components for 32 or 64-bit configurations (avisynth+ or avisynth MT 2.60) without problems. It's only when I introduce the new svpflow dll plugins that the MPC-HC crash occurs.

By no means am I suggesting that there is an issue with SVP 4. What I need is information on how to properly configure the Avisynth script (posted below) to support the new svpflow dll plugin files. TIA smile

# *******************************************************************************************************
# **Global SVP w/auto refreash rate (Good for AVS+ 32-bit - with smoothing (SVP script by yan04000985) **
# *******************************************************************************************************
# Check http://www.svp-team.com/wiki/Plugins:_SVPflow for more setting details.
# Check http://www.svp-team.com/wiki/SVP:Profile for more setting details.
#
# Supporting 32-bit dll's
# AviSynth is AviSynth 2.6 (2.6.0.5)
# SVPflow plugins are SVPFlow1 3.0.2.0 1/12/2016 - SVPFlow2 3.0.6.0 1/12/2016
#
SetMemoryMax(2048)
global svp_scheduler=true
global threads=15
SetMTMode(3,threads)
global svp_cache_fwd=threads+2
#
LoadPlugin("C:\Program Files (x86)\SVP 4\plugins\svpflow1.dll")
LoadPlugin("C:\Program Files (x86)\SVP 4\plugins\svpflow2.dll")
#
ffdShow_source()
SetMTMode(2)
#
#Begin SVP script framework - credit to yan04000985
#
video_fps = last.Framerate
Your_screnn_refresh_rate    = "60"            # or your target frame rate
Frames_interpolation_mode   = "3"             # Uniform:0 1m:1 2m:2 adaptive:3
SVP_shader                  = "13"            # 1/2/11/13/21/23
Decrease_grid_step          = "{thsad:250}"   # By two with global refinement {thsad:250}\{thsad:4000}\{thsad:65000},{thsad:65000}\{thsad:65000} To small step 6-8 px
Target_frame_rate           =  0              # 0 = To screen refresh rate , 1 = original video frame rate , 2 = original video frame rate x2 , 3 = original video frame rate x3
Blend_adjacent_frames       = "false"
super_params     = "{pel:2,scale:{up:2,down:4},gpu:1,rc:true}"
analyse_params   = "{block:{overlap:1,w:32,h:32},main:{search:{coarse:{distance:-8,bad:{sad:2000}}}},refine:["+Decrease_grid_step+"]}"
smoothfps_params = Target_frame_rate > 0                                                          ? 
\                  "{rate:{num:"+String(Target_frame_rate)+",den:1,abs:false},algo:"+SVP_shader+",mask:{cover:70,area:70,area_sharp:1.65},scene:{mode:"+Frames_interpolation_mode+",blend:"+Blend_adjacent_frames+"}}"
\                : video_fps == 24000/1001 || video_fps == 25000/1001 || video_fps == 48000/1001 || video_fps == 30000/1001  ? 
\                  "{rate:{num:"+Your_screnn_refresh_rate+"000,den:1001,abs:true},algo:"+SVP_shader+",mask:{cover:70,area:70,area_sharp:1.65},scene:{mode:"+Frames_interpolation_mode+",blend:"+Blend_adjacent_frames+"}}"
\                : "{rate:{num:"+Your_screnn_refresh_rate+",den:1,abs:true},algo:"+SVP_shader+",mask:{cover:70,area:70,area_sharp:1.65},scene:{mode:"+Frames_interpolation_mode+",blend:"+Blend_adjacent_frames+"}}"
input = last
#
super=SVSuper(input, super_params)
vectors=SVAnalyse(super, analyse_params, src=input)
SVSmoothFps(input, super, vectors, smoothfps_params, mt=threads) #LIne 43 - not surprisingly ;^} 
#
SetMTMode(1)
GetMTMode(false) > 0 ? distributor() : last
########### END OF MSMoothFps.avs ###########
#end

28

(64 replies, posted in Using SVP)

ThomasLiddiard wrote:

Hello,

I first checked the AVS scripts generated by identical settings in both versions. The settings are those used by Fabulist, except artifacts masking was turned off and 16px grid step used for both. The only differences were parameters used for analyse_params:
"distance", -10 in SVP 3 and -8 in SVP 4
"type", default setting of 4 in SVP 3 and 2 in SVP 4
The generated scripts are attached, with modifications (needed for compatibility with Avisynth+) separated by ##### on top and bottom.

Hope this helps!

Re: "type", default setting of 4 in SVP 3 and 2 in SVP 4...  I know where to position it in a script however I can't find a document wherein there is a description of the function. The Plugins: SVPflow 3.1 document makes no mention of it and web searches came up empty.  Perhaps you know where I might find an updated copy covering the new(?) functions in SVP? TIA wink

29

(104 replies, posted in Using SVP)

Well all right! After looking at the events log while attempting to run my x64 configuration with SVP4 (I don't use it per se but it certainly has some great diagnostic features) I discovered the entry warning me that "FFDShow: can't find system-wide installation". Now that may not have anything to do with x64 MPC-HC/madVR/LAV/ffdshow/SVP failing to enable GPU in the ffdshow script but on a hunch I (re)installed ffdshow x64 (rev 4533 sep 29 2014). And what do you know..it works. Now I can enable/disable GPU in both MPC-HC and MPC-BE (x86 and x64).

Note: The initial ffdshow installation was from a rev 4533 generic kit (it included x86 and x64). I simply installed the x64 version over it (before scrubbing it all out and starting over with ffdshow). And I got lucky smile

30

(104 replies, posted in Using SVP)

Yeah, I knew there were problems with AMD/OpenCL but I hoped that the Crimson Hot Fix corrected the issue(s). My impression of the OpenCL oversight by AMD was that it applied to their final 'legacy' adaptors (my HD 7850 isn't listed as a legacy adaptor) but future updates to the Crimson package going forward would fix it for supported adaptors.

Oh well, in anycase the Catalyst 15.7.1 driver works fine but I won't feel right being stuck there - especially when Crimson 16.1 works with GPU acceleration on MPC-BE x86 and x64 as well as MPC-HC x86. I'll keep an eye on this and report back if anything changes. Thanks for taking the time to provide the update smile

31

(104 replies, posted in Using SVP)

Once again I upgraded AMD HD 7850 drivers from Catalyst 15.7.1 to Crimson 16.1 (latest hotfix) and once again the GPU Renderer (GPU:1) can't be initialized via AviSynth script within ffdshow raw video. This applies to my MPC-HC x64/madVR/LAV configuration.

MPC-BE x64 and x86 work just fine along with MPC-HC x86. When using the AMD HD 7850 15.7.1 drivers all work fine. I've played with different 64-bit AviSynth.dll files in C:\Windows\System32 but makes no difference.

I hate to stay stuck at Catalyst 15.7.1 but I'll revert until a solution is found. So, if you have successfully utilized the AMD Crimson drivers (now 16.1) with an SVP x64 configuration via AviSynth script (super_params = "{scale:{up:0},gpu:1,rc:true}") please let me in on it smile

Note: Keep in mind that the problem configuration is strictly MPC-HC x64. MPC-BE x64 is fine. Backing madVR out by switching to EVR-CP makes no difference. Error msg is [code 0x10000)  See Attached screen clip:

32

(104 replies, posted in Using SVP)

Using AviSynth mt (x86) and AviSynth+ (x64) and both seemingly work fine. Note: I don't watch long feature movies - if I can play a short 20 minute video by an independent filmmaker without audio/video problems I'm jazzed smile

That said I just finished watching Little Hurricane perform "Crocodile Tears"  https://www.youtube.com/watch?v=o74iygYCXDw (I have it local on my media drive). I specifically looked for audio issues and the sync was right on with the video using the attached AviSynth script.

The software involved was Windows 7 sp1, MPC-HC (x64) 1.7.10.56 (nightly), madVR v0.90.2, fdshow raw video filter rev4533 (sep 29 2014) with buffers set to 3 back and 10 ahead, LAV Video and Spliter Source 0.67.0.58-git.

The hardware is i7-3770 @ 3.40 GHz, AMD HD 7850 with Catalyst 15.7.1 (had problems with Crimson as I couldn't get GPU:1 to work in the AviSynth script) and Logitech G930 7.1 Wireless headset.

There, I think that should do it...

# *******************************************************************************************
# **Global SVP w/auto refresh rate (Good for AVS+ 64-bit - with smoothing (SVP script by yan04000985) **
# *******************************************************************************************
# Check http://www.svp-team.com/wiki/Plugins:_SVPflow for more setting details.
# Check http://www.svp-team.com/wiki/SVP:Profile for more setting details.
#
# Supporting 64-bit dll's
# AviSynth is AviSynth+0.1 (r1779)
# nnedi3.dll is v0.9.4.20
# SVPflow plugins are SVPFlow1 2.0.4.0 7/8/2015 - SVPFlow2 2.0.3.0 10/30/2015
#
SetMemoryMax(4000)
threads=12 #PC threads*1.5/2
#
LoadPlugin("C:\Program Files (x86)\SVP\Plugins\x64\svpflow1.dll")
LoadPlugin("C:\Program Files (x86)\SVP\Plugins\x64\svpflow2.dll")
PluginPath="C:\Program Files (x86)\SVP\Plugins\x64\"
LoadPlugin(PluginPath+"nnedi3.dll")
#
SetFilterMTMode("DEFAULT_MT_MODE",2)
SetFilterMTMode("ffdShow_source",3)
ffdShow_source()
#
#nnedi3 64-bit
#nnedi3_rpow2(rfactor=2,cshift="Spline36Resize",fwidth=Width()*1,fheight=Height()*1,nsize=0,nns=2,qual=1) #No change in size
#nnedi3_rpow2(rfactor=2,cshift="Spline16Resize",fwidth=Width()*4,fheight=Height()*4,nsize=0,nns=2,qual=2) #No change in size
#
#Begin SVP script framework - credit to yan04000985
#
video_fps = last.Framerate
Your_screnn_refresh_rate    = "60"            # or your target frame rate
Frames_interpolation_mode   = "3"             # Uniform:0 1m:1 2m:2 adaptive:3
SVP_shader                  = "13"            # 1/2/11/13/21/23
Decrease_grid_step          = "{thsad:250}"   # By two with global refinement {thsad:250}\{thsad:4000}\{thsad:65000},{thsad:65000}\{thsad:65000} To small step 6-8 px
Target_frame_rate           =  0              # 0 = To screen refresh rate , 1 = original video frame rate , 2 = original video frame rate x2 , 3 = original video frame rate x3
Blend_adjacent_frames       = "true"
super_params     = "{scale:{up:2,down:4},gpu:1,full:true,rc:true}"
analyse_params   = "{block:{overlap:2,w:32,h:32},main:{levels:3,search:{coarse:{distance:-14,bad:{sad:2000,range:-32},trymany:false,width:1921},distance:-24,sort:true},penalty:{lambda:10.5,plevel:1.6,lsad:3500,pnew:50,pglobal:50,pzero:100,pnbour:40,prev:30}},refine:["+Decrease_grid_step+"],vectors:3}"
smoothfps_params = Target_frame_rate > 0                                                          ?
\                  "{rate:{num:"+String(Target_frame_rate)+",den:1,abs:false},algo:"+SVP_shader+",mask:{cover:70,area:100,area_sharp:1.65},scene:{mode:"+Frames_interpolation_mode+",blend:"+Blend_adjacent_frames+"}}"
\                : video_fps == 24000/1001 || video_fps == 25000/1001 || video_fps == 48000/1001 || video_fps == 30000/1001  ?
\                  "{rate:{num:"+Your_screnn_refresh_rate+"000,den:1001,abs:true},algo:"+SVP_shader+",mask:{cover:70,area:100,area_sharp:1.65},scene:{mode:"+Frames_interpolation_mode+",blend:"+Blend_adjacent_frames+"}}"
\                : "{rate:{num:"+Your_screnn_refresh_rate+",den:1,abs:true},algo:"+SVP_shader+",mask:{cover:70,area:100,area_sharp:1.65},scene:{mode:"+Frames_interpolation_mode+",blend:"+Blend_adjacent_frames+"}}"
input = last
#
super=SVSuper(input, super_params)
vectors=SVAnalyse(super, analyse_params, src=input)
SVSmoothFps(input, super, vectors, smoothfps_params, mt=threads, url="www.svp-team.com")
Prefetch(threads)
########### END OF MSMoothFps.avs ###########
#end

mashingan wrote:

MAG78
Maybe some users here have the same case with me, and they have already installed it. It would be a nice reference if they already did it smile

OT here but related to SVP functionality with Crimson drivers on my AMD 7850. I Uninstalled the latest Crimson drivers pkg and installed the final pre-crimson drivers (15.7.1) and all is fine now (GPU acceleration works from AviSynth script in ffdshow). As you know prior to that I couldn't get AviSynth Script to enable GPU acceleration with MPC-HC x-64 although it did work with MPC-BE (x-86 and x-64) and MPC-HC x-86. I tried *everything* but no success. The only thing left was rolling back the AMD GPU drivers. Couldn't see how that would help but I knew it worked at one time. So why not..that did the trick.

34

(104 replies, posted in Using SVP)

mashingan wrote:

MistahBonzai

1. Since you have an i7, the optimum threads is 19.
I usually use 15 or there abouts but was messing around with the script and copied from the session.

2. Have you ever tried to move the plugins64 to folder which not in MPC-BE folder?
That is next on my adgenda now that I know MPC-HC x64 works for you.

3. In my case, I put the SVP1.dll and SVP2.dll x64 in "C:\Program Files (x86)\SVP\plugins\x64".
See 2 smile

4. What version of MPC-HC do you have? Mine is 1.7.10.40, see the pic.
Same here.

5. p.s.: My MPC-HC (32bit and 64bit) comes from K-Lite and all others necessary codec chain. It works too with MPC-BE (32bit and 64bit) without installation.
All mine are the latest nightly builds from the individual projects. I'm thinking maybe a registry issue (K-Lite may be 'woven together' such that the issue is avoided) but then again MPC-HC x86 is fine.

6. Edit: I've tried your script. Except changing width and height from 16 to 32 and disable nnedi3_rpow2, it works without problem both MPC-HC and MPC-BE
Good deal - I usually use width/height of 32 and overlap of 1 with 1080p. I drop it down to 16/2 on 720p and kick in the nnedi3. Thank you so much for testing everything on your configuration. smile  Now I have a better idea where to look.
.

35

(104 replies, posted in Using SVP)

OK.. I configured the folders and paths to replicate the 3 AVS files approach you utilized. Then verified that it worked with MPC-BE (with and without the GPU via the GPU:1 or 0 switch.  Satisfied that SVP worked as expected I moved on to MPC-HC. And once again I was foiled by the inability to enable GPU in the svp64_1080p.avs script.

Just so we are on the same page I'll post a sample of the single script approach which I use - keep in mind my display is 1080p/60HZ, I load the file in ffdshow raw video filter via AviSynth support and I use only the svpflow 1&2 .dll files from SVP and not the manager or other associated files. My bottom line is MPC-BE works with/without GPU enabled while MPC-HC works only without the GPU acceleration.

Oh yeah, and a big thanks for the script samples as they give me ideas on how to 'if than' my single script into relevant sections based on resolution rather than on the fly edits smile

# *******************************************************************************************************
# **Global SVP w/auto refreash rate (Good for AVS+ 64-bit - with smoothing (SVP script by yan04000985) **
# *******************************************************************************************************
# Check http://www.svp-team.com/wiki/Plugins:_SVPflow for more setting details.
# Check http://www.svp-team.com/wiki/SVP:Profile for more setting details.
#
# Supporting 64-bit dll's
# AviSynth is AviSynth+0.1 (r1779)
# nnedi3.dll is v0.9.4.20
# SVPflow plugins are SVPFlow1 2.0.4.0 7/8/2015 - SVPFlow2 2.0.3.0 10/30/2015
#
SetMemoryMax(4000)
threads=8 #PC threads*1.5/2
#
LoadPlugin("C:\Program Files\MPC-BE x64\plugins64\svpflow1.dll")
LoadPlugin("C:\Program Files\MPC-BE x64\plugins64\svpflow2.dll")
PluginPath="C:\Program Files\MPC-BE x64\plugins64\"
LoadPlugin(PluginPath+"nnedi3.dll")
#
SetFilterMTMode("DEFAULT_MT_MODE",2)
SetFilterMTMode("ffdShow_source",3)
ffdShow_source()
#
#nnedi3 64-bit
nnedi3_rpow2(rfactor=2,cshift="Spline36Resize",fwidth=Width()*1,fheight=Height()*1,nsize=0,nns=2,qual=1) #No change in size
#
#Begin SVP script framework - credit to yan04000985
#
video_fps = last.Framerate
Your_screnn_refresh_rate    = "60"            # or your target frame rate
Frames_interpolation_mode   = "3"             # Uniform:0 1m:1 2m:2 adaptive:3
SVP_shader                  = "13"            # 1/2/11/13/21/23
Decrease_grid_step          = "{thsad:250}"   # By two with global refinement {thsad:250}\{thsad:4000}\{thsad:65000},{thsad:65000}\{thsad:65000} To small step 6-8 px
Target_frame_rate           =  0              # 0 = To screen refresh rate , 1 = original video frame rate , 2 = original video frame rate x2 , 3 = original video frame rate x3
Blend_adjacent_frames       = "false"
super_params     = "{scale:{up:2,down:4},gpu:1,full:true,rc:false}"
analyse_params   = "{block:{overlap:2,w:16,h:16},main:{levels:3,search:{coarse:{distance:-24,bad:{sad:750,range:-32},trymany:false,width:1921},distance:-24,sort:true},penalty:{lambda:10.5,plevel:1.6,lsad:3500,pnew:50,pglobal:50,pzero:100,pnbour:40,prev:30}},refine:["+Decrease_grid_step+"],vectors:3}"
smoothfps_params = Target_frame_rate > 0                                                          ? 
\                  "{rate:{num:"+String(Target_frame_rate)+",den:1,abs:false},algo:"+SVP_shader+",mask:{cover:70,area:100,area_sharp:1.65},scene:{mode:"+Frames_interpolation_mode+",blend:"+Blend_adjacent_frames+"}}"
\                : video_fps == 24000/1001 || video_fps == 25000/1001 || video_fps == 48000/1001 || video_fps == 30000/1001  ? 
\                  "{rate:{num:"+Your_screnn_refresh_rate+"000,den:1001,abs:true},algo:"+SVP_shader+",mask:{cover:70,area:100,area_sharp:1.65},scene:{mode:"+Frames_interpolation_mode+",blend:"+Blend_adjacent_frames+"}}"
\                : "{rate:{num:"+Your_screnn_refresh_rate+",den:1,abs:true},algo:"+SVP_shader+",mask:{cover:70,area:100,area_sharp:1.65},scene:{mode:"+Frames_interpolation_mode+",blend:"+Blend_adjacent_frames+"}}"
input = last
#
super=SVSuper(input, super_params)
vectors=SVAnalyse(super, analyse_params, src=input)
SVSmoothFps(input, super, vectors, smoothfps_params, mt=threads, url="www.svp-team.com")
Prefetch(threads)
#end

36

(104 replies, posted in Using SVP)

I been using SVP within a AviSynth (AVS-MT and AVS+) script wherein I also call nnedi3 along with some other simple filters.  Been doing this for at least a year now with MPC-BE and MPC-HC with the MadVR renderer - 32-bit versions works fine once I match the .dll files.  Once I had access to 64-bit versions of the svpflow1&2 .dll files I couldn't wait to try out 64-bit versions of MPC-HC and -BE. MPC-BE worked fine - I could see the sizeable differences in CPU, and to a lesser extent GPU, utilization when enabling /disabling GPU:0/1 in the AviSynth script. Unfortunately MPC-HC 64-bit kicks the following error with gpu:1 (enabled): "SVSmoothFps: unable to init GPU based renderer [code 0x10000]. The specific line referenced is: "{scale:{up:0},gpu:1,rc:true}". Works fine with gpu:0

I figured it was unique to my configuration (i7-3770, AMD hd-7850 various Radeon drivers - now with 15.11 Crimson, windows 7 latest patches) until I read the previous post by fuck_yeah. If 64-bit MPC-HC/MadVR/ffdshow raw/AviSynth works for you I would luv to see your script. TIA smile

Update 10-01-2016
FIXED IT: AMD drivers for my HD 7850. Uninstalled the latest Crimson drivers pkg and installed the final pre-crimson drivers (15.7.1) and all is fine now (GPU acceleration works from AviSynth script in ffdshow).

37

(104 replies, posted in Using SVP)

fuck_yeah wrote:

InterFrame(Preset="Medium", Tuning="Film", GPU=false, Cores=4)

But it doesn't work with GPU acceleration when using 64 bit programs (so it's disabled)

The same with MPC-HC however GPU acceleration will turn-on with MPC-BE

38

(6 replies, posted in Using SVP)

Then there is "Convert videos to 60fps" by SubJunk:
http://www.spirton.com/convert-videos-to-60fps/

39

(14 replies, posted in Using SVP)

kraag wrote:

Thanks for the extra variables to think about, it helps.

Like a junkie on the streets, I am continuing my search for a fix...

I had almost forgotten how/what was giving me the "Couldn't open ""C:\ProgramData\SVP 3.1\AVS\ffdshow.avs""(ffdshow_filter_avisynth_script, line 4)" and so forth so I fiddled a bit and recreated the error. It occurs with some (maybe all) .flv files.

A bit of background: The reason I was kinda hazy about it was I normally run SVP via AviSynth in the ffdshow raw video filter. I stumbled on the issue when a .flv file cashed MPC-HC hard and kicked me to the crash dump web page. It played fine without the SVP AviSynth script.

Eventually I tried to run the .flv file in the SVP manager and got the ..avisynth_script, line 4 error pop-up along with the message overlay in the player. Some files that hang SVP (with that error) will play via the AviSynth in the ffdshow raw video filter method. It was a p0rn sample I saved strictly for testing purposes you understand wink  It was 29.970/x264 core that I suspected started life as a 23.976 and I was having reclock issues that I thought might be connected to it. I fixed reclock by dumping the database. The file still errored out but I put it on the back burner until I saw your post.

40

(14 replies, posted in Using SVP)

kraag wrote:

Well now, I actually just un-installed a McAfee product [real time scanner] before all this happened. I am running W7 x64 also.

I reindexed windows as someone had suggested in a similar situation (no idea why but some folks said it 'fixed' their issue with registration errors). Just to make sure I ran (reran?) the McAfee product removal tool (MCPR.exe). It completed without incident but still no joy sad

41

(14 replies, posted in Using SVP)

kraag, same exact issue here (ffdshow_filter_avisynth_script, line 4) and so forth... The 2 components (wshom.ocx and wshext.dll) are there but attempts to register them fail with "The module wshext.dll was loaded but the call to DllRegisterServer failed with the error code 0x80040201" Attempts to deregister them (regsvr32 /u wshext.dll) pass without error. While searching forums for the registration error I discovered 2 folks with the same issue. Both were windows 7 64-bit and both had previously uninstalled the factory installed McAfee A/V (as is the case here). Neither had a solution nor did I find others. FYI: sfc /scannow came up clean. I opened cmd as administrator.

42

(10 replies, posted in Using SVP)

Looks like you posted while I was posting a reply (auto logout victim). Anyway I'll post again cuz the little I've read above sounds even more like what I'm dealing with...

I'm experiencing a somewhat similar issue. Don't think it's related, or a least directly, to my playback package (MPC-HC, MadVR, AC3filter, LAV, ffdshow Raw Video and AVS+. I playback as usual but I introduce nnedi3 and SVP via AviSynth Scripts (to offload the GPU). Anyway The issue is occasional dropped single frames and small groups during playback. The dropped frames occur in my 3 minute 720P/24fps test clip upscaled to 1080P/60fps with nnedi3 - which pushes the system close to max capacity (occasional CPU spikes to 80%) - at a rate of maybe 30 frames in the 3 minutes.   When all is good it plays without incident. CPU usage does not indicate problems (stays normal as when playing smoothly) - and my hunch it is CPU path related rather than the GPU. It's also not memory related (16GB with all relevant .exe files patched with the 4GB patch) and occurs with MPC-BE as well.

I searched out all unnecessary (or suspicious) tasks and disabled them and rebooted. All fixed - or so I thought.  Only to have the issue reappear at some point. I figured it had something to do with all the starts and stops along with many AviSynth script modifications I was making. Right now (for the past hour or so) it is running fine. I'm keeping an eye it and recheck every time I introduce a new task (program). As I don't watch entertainment programs/movies and such but mess with the MPC-HC, MadVR, AC3filter, LAV, ffdshow Raw Video and AVS+ configuration for the fun of it it's not some much a problem as it is a challenge.

What I suggest is that you approach the issue similar to what I have done. Eliminate all unnecessary tasks and reboot. Run your test clips. See if it made a difference. No? Then recheck that the .exe files are 4GB patched) with increase threads and/or memory in SVP. I suspect something is interfering with the SVP (or MPCxx) buffers. You gotta locate that 'something'  big_smile

43

(29 replies, posted in Using SVP)

Nice smile  Thanks for the code sample. One thing that gave me pause to think about was when copying and pasting from "ffdshow 64bit with SVPflow" archive the following code for "4K downscaling to FHD" copied from your post here

yan04000985 wrote:

Also 4K downscaling to FHD

.
.
.
width  = width(last)
height = height(last)
Is_4K  = width > 2304 || height > 1296 ? "true" : "false"

         Resize_to_FHD_4K == "true" Is_4K == "true" Is_16lineardw == "true"  ?
.
.
.

Becomes:

.
.
.
width  = width(last)
height = height(last)
"4K_Resize_to_FHD" == "true" && width > 2304 || height > 1296 && 16lineardw == "true" 
.
.
.

in the code packaged in the "ffdshow settings" of "ffdshow 64bit with SVPflow". The "&&" kicks the error "the right operand of && must be boolean". After coping directly from this post everything seems fine. Thanks again smile

44

(21 replies, posted in Using SVP)

I had the same concerns about CPU load when disabling GPU assistance.  I was like 'why would anyone do that?'  Well, I wanted to test the pixel scale options (as I recall) and for whatever reason I had to disable GPU to do so (see attached AviSynth script excerpt I use for clarity). And guess what..CPU utilization went from 49% in a taxing scene to 55% in the same scene.  I liked the results so I left it set to "0".  If I really need CPU I can reset it. I recall noting in a discussion regarding GPU assistance that it didn't really off-load the CPU all that much. YMMV smile

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

Edit: I am apprehensive about posting this (I like to keep a low profile and only post when I'm 'pretty sure' of the facts) but after retesting it 3 times w/wo GPU assistance I note that GPU utilization drops from 33% to ~31/32% when disabling GPU (HD-7850) and the actual peak CPU (i7-3770 @3.40GHz) utilization throughout the 60 second video was ~66% with GPU enabled and ~60% without GPU enabled.  It appears that the load pattern shifts shape a fair bit and the peak moved 5 seconds or so in the video stream when changing to/from GPU enabled.  I don't think absolute numbers are that important here - it's the relative values that tell the story with all else being equal (such as it was). I'm going back to lurking now.

45

(171 replies, posted in Using SVP)

I'm most likely way off base here but I've noticed when exporting the SVP last run script that some SVP parameters are no longer displayed - in particular the overlap value for blocks. I had an issue with frame drops on a file that had played smoothly. Upon investigation I noticed the missing 'overlap' parameter. After inserting overlap:0 into the script (the value I had been utilizing with the 'old' svpfolw dlls) CPU utilization dropped and performance returned to 'normal'.

I have also discovered (it has been mentioned here in passing) that finding the proper value for 'prefetch' is critical for finding the optimal performance sweet spot - it can very from file to file... If you are dropping frames but cpu seems OK (or even less than expected) then increase the prefetch value.  If CPU utilization seems high and bounces around a bit more than expected try lowering the prefetch value. With the old avisynth.dll (AviSynth 2.6 MT) I would set 'threads' to 15 and forget it. Also as the frame sizes are increased the memory setting will likely need to be increased to accommodate the larger frames.  More than 1024 is occasionally required...

46

(171 replies, posted in Using SVP)

Blackfyre Not sure if this is the culprit but I linked you to an incorrect version of generate.js - I have the proper version but in my quest to locate linkable files I linked to a broken one.  Try this corrected version of generate.js http://puu.sh/hwFC3/ac580e75e4.js.  Excuse me for steering you wrong however my experience with the 'new' version is limited to running the SVP script within a larger avisynth script and not within SVP (except for exporting the SVP script) as a standalone application.

47

(171 replies, posted in Using SVP)

dlr5668 wrote:


dont forget to delete old cpu/gpu libs:

http://puu.sh/hwFFQ/df201e0fe3.png

I created the folder svp/plugins/old to store the old cpu/gpu and svpflow libs for those times I want to revert to AviSynth 2.6 MT. The older avisynth.dll will want the old cpu/gpu libs.

48

(171 replies, posted in Using SVP)

I have my test bed (Windows 7 sp1 64-bit, i7-3770 @ 3.4 GHz and AMD H-7850) configured with 2 copies each of MPC-BE/LAV and MPC-HC/LAV.  A 32-bit and 64-bit configuration for MPC-BE and HC.  MPC-BE 32-bit with video set to EVR-CP 32-bit FP, Catmull-ROM spline 4 and D3D Fullscreen/10-bit RGB (my display is 10 bit). MPC-HC 32-bit with video set to madvr. I use LAV in both cases.  I've been tweaking the 64-bit configurations waiting on 64-bit SVP big_smile

Testing consists of performance (speed and quality) rendering of various video files on the 32-bit configurations.  There are times when I need to reconfigure MPC-BE to run the 'old' AviSynth 2.6 MT by SEt and the 'old' svpflow dll's. Then run the exact same test with it in conjunction with the 'new' AVS+ Avisynth and the new svpflow dll's.

As I said in past posts I'm running the SVP script captured after running a video with SVP within the confines of AviSynth - I integrate the scripts and feed it into ffdshow raw video filter. I do so because I mix various AviSynth filters in the script when rendering files. That way I can balance the load between CPU and GPU - like using nnedi3 on the CPU thus freeing up the GPU for more intensive tasks. I hate seeing one loafing along while the other is maxed  wink

49

(171 replies, posted in Using SVP)

Keep in mind that this rather convoluted process for building SVP is only for beta testing and the final self contained SVP app may well contain different versions of these files.

The links have been posted here within the past few weeks but here goes:

This configuration is for the AVS+ version of 32-bit AviSynth.

  • Place the AviSynth+ 0.1 (r1780, i386) dll from above in your MPC-BE/HC top folder with the MPC*.exe file.

    Place the new SVP (svpflow-1.1.14) dll files in your SVP plugins folder(replacing the older svpflow dlls).

    Place the generate.js file from above in your SVP top folder. It's modified for compatibility with the new AviSynth dll.

That should do it. If you need more information I would advise you to read the "New version of SVP?" and the "Running out of memory, even with "4 GB fix"/large address aware" threads in their entirety.

50

(171 replies, posted in Using SVP)

Mag79.. Don't know if this helps in anyway but... I had noticed that the new SVP configuration (svpflow dlls, AVS+ avisynth.dll, and new avisynth script - doing nothing but loading svpflow dlls, configuring SVP and running MSMoothFps.avs) reported (via ctrl+J in MPC-BE) higher peak CPU utilization but didn't drop frames where the old version did. All libraries, folders and MPC-BE settings and such were identical excepting the Avisynth.dll, svpflow dlls and the main avisynth script for ffdshow raw video filter. As I reported in the "Running out of memory..." thread:

What I did discover while comparing AviSynth 2.6 MT to AVS+ rendering the "SONY F55 4K Blue Shanghai Zhen Wang Wei 150mbps.mp4" video was that although the CPU utilization was similar, AVS+ didn't drop frames in the most difficult sections of the video. AviSynth 2.6 MT would drop frames for me when CPU utilization topped 63% while AVS+ would hit 70% in the same section but not drop the frames that AviSynth 2.6 MT did. Perhaps I could eliminate the difference by tweaking threads in AviSynth 2.6 MT... In any case AVS+ coupled with the new SVPflow DLLs works fine as far as I'm concerned.

I retested both configurations just to make sure things were right (they were) and performance was still as reported. In addition I rendered a run of the mill 1080P/24fps file (https://vimeo.com/50855881) and noted 8-12% CPU utilization with the old SVP configuration and 13-17% CPU utilization with the new SVP configuration. GPU utilization hovered around 24% with the old version and 23% with the new one. I failed to capture average jitter readings but the new version just 'feels' smoother.