Selur's Little Message Board

Some "Vaporsynth" filters influenced on FPS and frame count behave unpredictably (at least I couldn't find the links that could case it) . Very often (not always) frame count and FPS doesn't represent entered values for the filters influencing these values ( QTGMC "bob", FrameInterpolation, sRestore). Very often it happens from the very beginning of the new job, sometimes after switching between  Vaporsynth to Avasynth and back to Vaporsynth "Support" in the same job.  Avisynth behaves correctly.



QTGMC screenshot represents  activated de-interlacing filter only, no other filters has been activated. Frame interpolation screenshot shows the same regardless QTGMC parameters.

"Frame interpolation" having no effect when a frame rate below the current frame rate is selected is correct, since it will/can only be used when going to higher frame rates.
The Vapoursynth + QTGMC + Bob thing is a bug (rewrote the code a few days ago).
-> will fix.

-> think I fixed it, will send you a link to a dev verison in a few minutes.

Cu Selur

(26.10.2020, 07:04)Selur Wrote: [ -> ]"Frame interpolation" having no effect when a frame rate below the current frame rate is selected is correct, since it will/can only be used when going to higher frame rates.
The Vapoursynth + QTGMC + Bob thing is a bug (rewrote the code a few days ago).
-> will fix.

-> think I fixed it, will send you a link to a dev verison in a few minutes.

Cu Selur

Can I also send a dev version, otherwise I have some errors when using this filter?

I'll send you a link