Search options (Page 246 of 356)

Mystery
with memory usage between 600-1000MB (similar to 2.5.8)

similar to 2.5.8 "SVP build"

Anything I should pay attention to when testing it?

memory leaks especially after script reloading
MT efficiency (how many threads're required to achieve "SVP index" = 1) (more threads => more memory consumption)
overall stability

The main problem with 2.5.8 MT is that especially when controlling MPC-HC via API, it crashes very regularly

I really have no idea how you make it happen. In a real life it doesn't crash at all unless you start seeking the video.

is there a way for me to programmatically know in which folder SVP was installed?

may be via uninstallation path?

what happens if I always specify to use the GPU and it runs on a computer that doesn't support it?

AVS script will give an error

I tried using this build of AviSynth+ MT for encoding videos with EEDI3+NNEDI3, and am getting about 3-4% lower performance than with the official build.

Not my fault    Building AVS+ is extremely straightforward - like opening the solution and pressing "Build" button.
May be MT branch doesn't incorporate ALL commits to the main one...

with 2.5.8 player crashes for only one reason - on excessive fast forward / rewinds

with 2.6 it crashes randomly mainly because 1.6 GB is almost too much for 32-bit process

what exactly do you want?
you like 2.6 - just use it, but we won't make any special build of this ... thing

may be some day we'll release something based on AVS+ cause this's the only choice now
you can make this day come faster by trying AVS+ yourself and test it for stability / etc

сделать взад так, как было несколько месяцев назад

Mystery
would be better than an unstable & old version of AviSynth 2.5.8 MT

My point in this thread is ALL existing AVS versions are bad and "old and unstable" 2.5.8 "SVP edition" is the best one for linear multi-threaded video processing.
At least for scripts and functions used in SVP.
I can imagine that for some very complex scripts like QTGMC AVS 2.6/+ are much better BUT not for SVP.

may be cause avs 2.6 mt builds have strong memory leaking issues

TCmullet
Can an AviSynth script have memory leaks? 

Depends on avisynth version itself and on any plugin used.
For example Avisynth+ doesn't free cached video frames at exit.

Try to restart SVPtube after changing %PATH% value.

========
Oh, you've just modified path inside the script.
Ok, how that line of code looks now?

Mystery
feel free to use it 

ffdshow has a lot of tools for "first upscale/process/denoise the video"

MAG79
Ну можно же выставить в качестве shell любую программу. Хоть калькулятор