Re: New version of SVP?
deleted (crashes sometimes, need more tests)
You are not logged in. Please login or register.
SmoothVideo Project → Using SVP → New version of SVP?
deleted (crashes sometimes, need more tests)
Chainik
you may want to set internal ffdshow buffers to some larger values (20 frames for example) for AVS+ to work correctly
Maybe but I don't know how on ffdshow RAW filter. When double clicking ffdshow icon and go to Avisynth it resets any number next time I launch player.
Anyway, I guess with AVS+ I experience those crash on seek. You could ask what was made in AVS 2.58> 2.6 that that bug was gone so the same commit would be in the AVS+.
I build avs+ with max optimization, intel x15 compiler, last sources. https://mega.co.nz/#!ggQzHIQC!8y473pi-Y … E8zGInvmTc
1. Replace js in svp folder
2. Copy avs+ dll to player folder
3. Update svpflow files http://www.svp-team.com/files/gpl/svpflow-1.1.13.zip
4. Restart svp
Try it guys. Works fine on my end (15 threads). No crashes with seek.
Your version takes 1.4MB instead of 1.1MB and it crashes on my computer (Intel i7 quadcore CPU)
The AVS version posted previous works. Memory usage about 1GB.
Yeah, it just crashes.
James D
Yeah, it just crashes.
too many optimization options. It runs fine on my i5. I will build with standart /Ox one
Standard SVP install has been working trouble free. With your changes I get instant crash on my i7-3770 (quad core - 3.4GHz) , HD 7850 and win7 64 bit. With MPC-BE(x86) and HC(x86) with 4GB patch. SVP 3.1.6.1052 with 4GB patch. Appears to be AviSynth.dll related. Was already up to date with svpflow*.dll. Looking forward to a vanilla AviSynth.dll build.
James D
dlr5668
The issue about ffdshow buffers is fixed in the latest AVS+ commit on github.
In fact that commit is extremely essential for SVP but it wasn't "officially" released yet.
Chainik
In fact that commit is extremely essential for SVP but it wasn't "officially" released yet.
this one https://github.com/AviSynth/AviSynthPlu … b155534cb3 ?
I have this fix in "my" build
btw uploaded avs+ with less agressive optimize settings https://mega.co.nz/#!YgpG0aSL!7mksBRpYA … gE4nYXV7qo Should work now. Too bad I have only one PC and cant test it properly
http://puu.sh/hiEBc/c32ba21cca.png
http://puu.sh/hiEDB/d66da32f3b.png
dlr5668
this one
yep
Chainik
The issue about ffdshow buffers is fixed in the latest AVS+ commit on github. In fact that commit is extremely essential for SVP but it wasn't "officially" released yet.
I bet I already have it for 2 days because it's called ffdshowfix and v. 1780
https://cloud.pados.hu/index.php/s/0e0d … 11731699b6
FWIW: Using the latest instructions for x86 and the r1825 AviSynth.dll provided by dlr5668 I still get an immediate crash with MPC-HC (x86) however substituting the r1780 AviSynth.dll provided by James D (ffdshow-fix) works (after throwing an invalid script error). CPU usage drops 8-10% (from ~50% to ~42% with 1080p/24fps file) with my set-up. I haven't exercised MPC-HC much (no seeking) but at least I have I know I have a valid path(s). Of Course it's 32bit while 64bit is where my head is at
Edit: Performance appears to be the same - I usually run SVP via my own scripts in ffdshow raw video via AviSynth support and was comparing apples to oranges. So the AVS+ AviSynth.dll yields about the same performance as the 'old' 2.6MT AviSynth.dll - unless it's latching onto another overlooked AviSynth.dll.
MistahBonzai
r1825 AviSynth.dll provided by dlr566
did u test this version too https://mega.co.nz/#!YgpG0aSL!7mksBRpYA … gE4nYXV7qo ?
MistahBonzai
r1825 AviSynth.dll provided by dlr566
did u test this version too https://mega.co.nz/#!YgpG0aSL!7mksBRpYA … gE4nYXV7qo ?
Yup, that's the one I just tested prior to the latest (r1780) from James D. Perhaps the difference between or CPUs is an issue. When choosing a DLL I go for the vanilla Win7 build as I've run into issues (not unlike this one) with using ones optimized for processor specific support routines.
BTW: What's a good utility for verifying the AviSynth.dll being used? I most likely already have it but I got so many 'tools' I've lost track...
MistahBonzai
BTW: What's a good utility for verifying the AviSynth.dll being used? I most likely already have it but I got so many 'tools' I've lost track...
copy right one to player folder. It will have maximum priority
copy right one to player folder. It will have maximum priority
Yup, that's what I've been doing (per your instructions). By habit I use the appropriate 'system' folders to keep track of them but in this case I used the player folder (with the _player.exe) and left the previous ones in the 'system' folders. From experience I offer that overlooked AviSynth.dll files can leave ya chasing your tail.
Well all right! time for 64-bit
MistahBonzai
What's a good utility for verifying the AviSynth.dll being used?
upcoming SVP release
- you don't need it
- current build of AVS+ x64 have some vital issues with ffdshow x64
Chainik
upcoming SVP release
it should be done 03/04
http://puu.sh/hjV9B/8fbfe7a3ef.jpg 63% average load new libs+avs vs 100% with original setup (all dropped frames are from testing seek crash)
dlr5668
all dropped frames are from testing seek crash
Should be no seek crash with Avisynth 2.6, but seek crash exists with AVS+
No choppy playback with AVS+ but choppy playback exists on some types of video, possibly due to auto threads count, on Avisynth 2.6.
Avisynth 2.5 is old and have crashes on seek too.
And ffdshow never been updated since? September last year? I guess only if clsid improves ffdshow and AVS devs merge all bugfixes we will get fully stable SVP.
13th April 2015, 12:35 #15278 | Link
clsid
Registered User
Join Date: Feb 2005
Posts: 4,310
ffdshow is already dead. There are no active developers and there haasn't been any serious development in years.
Of course, it will always remain available in its current form.
__________________
[ ffdshow SVN builds ]
So uh... just how much more performance will this new version of SVP have? The only daily reason I have my CPU overclocked is for SVP, so I've been stability-testing some lower-overclock settings during this recent wave of cold air in the NorthEastern US and summer hasn't hit yet, but I am unsure just how much I can lower my clockrate without also lowering my SVP settings...
Currently I run my Pentium G3258 at 3.9GHz @ +0.007v and that gives me ~90% CPU utilization in SVP for a typical intensive use-case of mine, and so far I've fully stability-tested 3.8GHz @ -0.026v, 3.7GHz @ -0.049v, and 3.6GHz @ -0.063v.
Nintendo Maniac 64
just how much more performance will this new version of SVP have?
reading doom9 forums can give some clues
You said that LAVfilter optimizations don't count. (besides, I'm already using trunk LAV builds)
Or are you implying that there's an actual SVP thread on Doom9...?
do I really need to reply this?
SmoothVideo Project → Using SVP → New version of SVP?
Powered by PunBB, supported by Informer Technologies, Inc.