And what do you expect if average frame rendering time in madVR is 15 ms and max time is 25 ms?
You are not logged in. Please login or register.
SmoothVideo Project → Posts by Chainik
And what do you expect if average frame rendering time in madVR is 15 ms and max time is 25 ms?
svptube-dl.wsf
// Folder to put downloaded files in.
// Default value is Downloads folder.
// NOTE: JavaScript transforms backslashes in strings.
// To include a \ in a file path, enter it twice, i.e. \\.
var downloadPath="";default path is "%HOMEDRIVE%%HOMEPATH%\Downloads"
MistahBonzai
That way I can override down scaling the video within SVP and pass it along to the GPU full size (3840x2160/60fps).
I don't get it. There's a built in option in SVP to manage downscaling.
What exactly are you arguing with?
There's at least one scenario when SetMemoryMax is mandatory.
There're no scenarios where SetMemoryMax can break something (unless it defines some inappropriate value).
So what? ![]()
Nintendo Maniac 64
Yup, setting 6 threads or less on my dual-core Pentium G3258 works well; by comparison setting 7 threads or more causes the flickering/shimmering effect that I saw with "Auto".
I'm guessing this is a known bug?
It can be a know bug for the AVS plus, not for SVP libs.
SetMemoryMax() is a almost-mandatory part of AVS memory management subsystem.
I really don't get why someone would remove this call?
Нифига. Для этого есть "Disable SVP".
А отключение в профиле - хотя бы для "забивания" слишком высоких разрешений / частот для данной системы.
Два почти одинаковых (с т.з. домохозяйки) пункта в главном меню нам не надо.
James D
setmemorymax is not a "MT function" and it should exist in every script.
Mystery
I'm trying with the latest DLL version. One 720p video was running at 30-50% CPU, and with the new version, it tops the CPU at 99% and lags. There's definitely something wrong there.
This just can't be.
Please share both video file and AVS script generated by SVP.
Fresh SVP 3.1.6 installation + "hotfix" patch.
4K musik video from YouTube, h.264 @24 fps
MPC-HC, EVR video renderer
Latest Avisynth 2.6 MT
"old" libs: 88% CPU load average
"new" libs: 69% CPU load average
No dropped frames in both cases.
For whatever reason any OSD message displayed by SVP drops performance by 2-3 times ![]()
So turn them off (SVP -> Settings -> Show OSD messages)
Looks like ffdshow issue, 2K (1440p) videos aren't affected.
I'll gladly supply system config details and script samples.
yes, please
And for the record - it's up to 38% faster. Which means from zero to 38%.
where is my favorite "facepalm" picture?
http://forum.doom9.org/showthread.php?t=164554
Version 1.1.12 (03/04/15) .... "up to 20% faster"
Version 1.1.14 (04/24/15) .... "up to 15% faster"
1.0 * 1.2 * 1.15 = 1.38
another one - I suggest to set 'setmemorymax' to some value in 1500-2000 for 4K
pressing too hard on Avisynth memory dispatcher is not a good idea ![]()
do I really need to reply this? ![]()
Nintendo Maniac 64
just how much more performance will this new version of SVP have?
reading doom9 forums can give some clues ![]()
MistahBonzai
EVR-CP is not good for 4k@60. Plain EVR works much better.
set "motion vectors precision" to "two pixels" and "decrease grid step" to "disabled"and you'll save a lot of memory
also decreasing number of threads can help
although my CPU's certainly got a lot of overhead left
do you really have 4K screen? otherwise you're dealing with 4K source downsized to your screen ![]()
SupRo
матрица там честные 120 герц, зачем она тогда?
надо ж ттх заранее читать
Kodiack
There're always extensive and intensive ways for improving something.
x64 is an extensive way and optimizing things to make 4K working on 32-bit is intensive way.
I prefer 2nd one ![]()
Still I admit that 8K video definitely will need x64 ![]()
Kodiack
Is there any way that I can use SVP with 4K
try latest Avisynth 2.6 MT build - http://forum.doom9.org/showthread.php?t=148782
also upcoming SVP update will have better compatibility with 4K
James D
dlr5668
done
SmoothVideo Project → Posts by Chainik
Powered by PunBB, supported by Informer Technologies, Inc.