Georg Pelz

I did some testing: FFMS2 + NeoFFT3DFilter: ``` # Imports import vapoursynth as vs # getting Vapoursynth core import ctypes # Loading Support Files Dllref = ctypes.windll.LoadLibrary("i:/Hybrid/64bit/vsfilters/Support/libfftw3f-3.dll") core = vs.core...

Tried that one too :) and it's basically the same speed as the neo version, also can't get it faster than 3.5fps.

But shouldn't they shift all planes? I first assumed that those parameters are meant to shift the focus of 'what is important',...

Yeah, but if all planes are shifted the same way, why is there a shift in the upper right image?

> And each value in the array specifies shifting of one plane. so for YUV src_left = [shift_Y_vertical, shift_U_vertical, shift_V_vertical] src_top = [shift_Y_horizontal, shift_U_horizontal, shift_V_horizontal] and for RGB src_left =...

Okay, thanks for clearing that up, I didn't get that from the description. :)

No problem. Got another question. If I use for example: src_left=[5], src_top=[5] and planes=[1] will the shift be ignored since the shift is for plane 0 or will it be...

Thanks, for explaining. :)

I have 0-knowledge about mvtool and its inner workings, just wanted to point out there is an issue.

not sure, but: the crucial part is probably disabling filler data otherwise the encoder will probably always fill the bit rate up till it hits the max bit rate.