Script file: C:\Users\Lorenzo\Desktop\AVSMeter268\mtmode2.avs
Log file created with: AVSMeter 2.6.8 (x86) It then proceeds to scan and closes when it reaches frame 100. I hope I did it right right clicked and opened the script with AVSMeter. I’ve also noticed that if I set the value even higher, like 48, it crashes instantly whilst 32 still allows me to scan trough a few frames before it crashes. I’ve installed several versions of avisynth and virtualdub, including 64 bit versions- and tried different Setmemorymax() values. MFlowFPS(super, backward_vectors, forward_vectors, num=500, den=5) MFlowBlur(super, backward_vectors, forward_vectors, blur=100) ImageSource("D:\Movie Making\Return to Castle Wolfenstein - Movie Edition - Old DemoViewer\demoViewer\screenshots\shot%.4d.tga",0,4833,500)īackward_vectors = MAnalyse(super, isb = true, blksize=32, truemotion=true)įorward_vectors = MAnalyse(super, isb = false, blksize=32, truemotion=true)
LoadPlugin("C:\Program Files (x86)\AviSynth\plugins\mvtools2.dll") However, when I attempt to change the blksize to 32 or higher (a value of 16 or below works fine), virtualdub (or WMP) crashes. What seems to work in getting rid of most of these artifacts is upping the value of blksize. I’m trying to create motion blur for my gaming footage by using MVTools- and I am quite satisfied with the result, but it unfortunately still shows some artifacts. I was wonder if anyone could perhaps help me out by finding a solution to an issue I’m facing with MVTools.įirstly, my level of understanding of avisynth is basically a little bit more than that of a beginner, so please bear with me!
0 kommentar(er)
