kibumm
Left is SVP, Right is Bluesky.
Occurring Artifacts in Bluesky are so clear.
looks like just very aggressive scene change detection plus "blend on scene change"
You are not logged in. Please login or register.
SmoothVideo Project → Posts by Chainik
kibumm
Left is SVP, Right is Bluesky.
Occurring Artifacts in Bluesky are so clear.
looks like just very aggressive scene change detection plus "blend on scene change"
About AFM Mode
Mode 0: Default setting and behavior depends on the GPU/APU
Mode 1: Created 2 original frames and 3 interpolate frames when converted 24p to 60p
Mode 2: Created 1 original frame and 4 interpolate frames when converted 24p to 60p
So "mode 1" maps to "1m" in SVP and "mode 2" maps to "uniform".
kibumm
so, if we forget about CPU usage, which one is better? ![]()
is AMD FMV limited to some video/codec types, source and resulting frame rates, etc?
please share your experience ![]()
Странный вопрос для этой ветки.
Предполагается что каждый юзер линуха, в принципе умеющий запустить в нем mpc-hc, сам знает все ответы ![]()
some anti virus software installed?
may be interesting - http://superuser.com/questions/842203/h … gressively
I didn't tried this
h.265 - никак
только с geforce gtx 960
one more time - mpc-hc IS patched
always
YT 1080p requires TWO different streams to be loaded and played simultaneously.
PotPlayer can't do this (at least via command line) while MPC-HC can.
End of story.
.exe file only
ffdshow is using avisynth
video player is using ffdshow
![]()
"4gb patch" is a must in any case.
perhaps this should be written with big and bold red letters on every Wiki page
Mystery
what performance difference on 15 threads? ... I would love to see that as well.
the same
BTW I was able to build AVS 2.6 + MT + our own patches, and it almost working BUT they've changed something in caching algorithm so it eats memory really fast and crashes.
And I really don't like to dig into this ... crap one more time ![]()
So I'd prefer to stick with "official" build if it's possible.
Write: File 'C:\ProgramData\SVP 3.1\Logs\avsFPS.txt' cannot be opened
will be fixed in the upcoming version
James D
Options in installer: SVP AS2.5 Ready or 2.6 Ready
try to guess how many users will know the right answer ![]()
Mystery
I'd be curious as to how the previous 2.6 MT compares in performance.
SEt's MT patch was last changed in early 2011...
number of threads required, which doesn't change the number of threads that actually get created
Right. This's why I'm starting to think we could switch to SEt's 2.6 MT.
It's totally OK on systems with 8 GB memory.
BUT it can create problems on 4 GB memory AND make SVP almost unusable on less than 4 GB memory.
Just for the record, how many computation threads are needed for the maximum performance.
Graph shows how frames-per-second depend on number of MT threads.
AVS script is SVP-generated for frame doubling (x2) with GPU acceleration.
CPU is AMD FX-8350 (4 cores 8 threads, just like Core i7).
And every thread need its memory and increases inner AVS cache.
похоже на ютюбе способ кодирования utf-8 поменяли
было типа такого - "\u041e\u0431\u0443\u0447\u0430\u044e\u0449" (т.е. каждая буква закодирована в ascii-строку) , а стало просто нормальным (русским) utf-8 текстом
перекачай 1.2.5 c сервера, заменил
nemoW
Is it hard to make "2.6MT SVP's edition"?
may be this's the only option right now
James D
So is it memory leak or a "feature"?
a feature
it just wasting memory for excessive caching

Main issue with original AVS - it eats too much memory.
I can easily push memory usage beyond 2 GB on 1080p video and it's just one click away from 32-bit process crashing.
Another issue - memory consumption is almost not adjustable in original AVS MT. In both "2.5.8 SVP's edition" and AVS+ memory consumption linearly depends on number of thread in use, BUT original AVS always eats its 2+ GB.
For example:
15 threads (default value for 8-thread CPUs): AVS 2.6 - 2300 MB, AVS 2.5 "SVP" - 1845 MB, AVS+ - 2000 MB.
10 threads: AVS 2.6 - 2000 MB, AVS 2.5 "SVP" - 1310 MB, AVS+ - 1580 MB.
AVS 2.6 will always crash a player unless it's not "4GB patched".
Videos larger than FullHD will not work with AVS 2.6.
Why ask here? UMS has its own support.
Сделай что-нибудь, что бы это не выглядело как запись трансляции телемегазина ![]()
SmoothVideo Project → Posts by Chainik
Powered by PunBB, supported by Informer Technologies, Inc.