Search options (Page 251 of 360)

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 любую программу. Хоть калькулятор 

https://github.com/AviSynth/AviSynthPlus/issues/49

if you search the forum you'll find that almost all crashes are because of AVS 2.6
and don't forget AVS development is in fact dead

AVS+ is great in terms of memory consumption and MT efficiency BUT is buggy and dead too

so the sad truth is Vapoursynth is the only hope

but it isn't integrated into ffdshow...

Почему не выделено жирным что это касается только BR только в PowerDVD? 

SVP makes as much frames per second as you wish.
Then video renderer (madVR, EVR, ...) sends this to the display device. Here's a conversion from 24 / 48 / 60 / 120 / XXX fps to the actual screen refresh rate.
Projector only accepts 60 fps on input (actually it's limited by HDMI).
If renderer gets 72 fps on input and should make 60 fps output it will simply drop 12 frames.
And finally projector itself can make 120 fps from 60 fps input with some kind o FI.

24 fps source -> [SVP xN] -> 24*N fps -> [video renderer] -> 60 fps -> [HDMI] -> [projector x2] -> 120 fps on the screen

So true 120 fps now possible only with selected 120 hz PC monitors (DVI connection). I don't know if there're any TVs / projectors with DP (Display Port) input