FrameRateConverter (Official)

[kedautinh12]

I think xclean avisynth version still don't finish

[MysteryX]

Oh and I spent a full week to get GPU passthrough to work for my Windows Virtual Machine... this is what I had to go through...

yes xClean Avisynth is what needs to be finished. Also a comparison video I want to produce. Got a long list of things to do...

[real.finder]

Originally Posted by Selur

Any news on RIFE incorporation into FrameRateConverter?

don't know if it possible or not but I think most mvtools problems come from bad motion vectors that MAnalyze do, so I wonder if MAnalyze can be updated to use some ideas from RIFE (neural network) to make perfect solution not only for FrameRateConverter but for any thing use MAnalyze like Motion Compensated and Temporal Denoising (like SMDegrain)

[johnmeyer]

Originally Posted by real.finder

don't know if it possible or not but I think most mvtools problems come from bad motion vectors that MAnalyze do, so I wonder if MAnalyze can be updated to use some ideas from RIFE (neural network) to make perfect solution not only for FrameRateConverter but for any thing use MAnalyze like Motion Compensated and Temporal Denoising (like SMDegrain)

Probably not. I say that because I've been watching a lot of "restored" old USA TV shows that were shot on film (e.g., "Perry Mason"). Many of them have been "improved" to show at 60 fps instead of how they were shot (24 fps). Since I've done so much of this work, I instantly see all the artifacts and, even when using professional motion estimation tools, all the artifacts you see when using MVTools are there: broken vertical objects, warping at edges when a foreground objects moves across the screen, and "broken legs" when people walk across the frame at a certain distance from the camera. I also see it on establishing shots when the camera pans up across a tall building that has lots of small windows.

[real.finder]

Originally Posted by johnmeyer

Probably not. I say that because I've been watching a lot of "restored" old USA TV shows that were shot on film (e.g., "Perry Mason"). Many of them have been "improved" to show at 60 fps instead of how they were shot (24 fps). Since I've done so much of this work, I instantly see all the artifacts and, even when using professional motion estimation tools, all the artifacts you see when using MVTools are there: broken vertical objects, warping at edges when a foreground objects moves across the screen, and "broken legs" when people walk across the frame at a certain distance from the camera. I also see it on establishing shots when the camera pans up across a tall building that has lots of small windows.

yes I know it will not be perfect improved

with "perfect solution" I mean as "RIFE incorporation into FrameRateConverter" plus improve mvtools in general

[zambelli]

Any plans for 10-bit YUV support?

[takla]

Originally Posted by johnmeyer

Probably not. I say that because I've been watching a lot of "restored" old USA TV shows that were shot on film (e.g., "Perry Mason"). Many of them have been "improved" to show at 60 fps instead of how they were shot (24 fps). Since I've done so much of this work, I instantly see all the artifacts and, even when using professional motion estimation tools, all the artifacts you see when using MVTools are there: broken vertical objects, warping at edges when a foreground objects moves across the screen, and "broken legs" when people walk across the frame at a certain distance from the camera. I also see it on establishing shots when the camera pans up across a tall building that has lots of small windows.

Interpolating 60 fps from 24 fps is just moronic.

[Selur]

Any updates on Vapoursynth&RIFE support? (adding support for RIFE-v4 model and the new skip&skip_threshold might be a good idea)

[Selur]

Any news?

[MysteryX]

Updates? Released a few software for Windows/Linux/MacOS

https://sourceforge.net/projects/converter432hz/
https://sourceforge.net/projects/player432hz/
https://sourceforge.net/projects/yangdownloader/
https://sourceforge.net/projects/powerliminals-player/
plus xClean script

Haven't got back to FrameRateConverter yet.

[Selur]

Haven't got back to FrameRateConverter yet.

fingers crossed this will change soon, really like the idea of FrameRateConverter using RIFE properly

[kedautinh12]

Yeah, RIFE support avs and vs now. Maybe need new ver of FrameRateConverter using RIFE

[MysteryX]

if RIFE supports AVS, it should be easy to do.

It's porting it to VapourSynth that is more complicated; particularly that the MvTools2 masks are completely different under VapourSynth!

I'm now on Linux and not currently setup for Avisynth development, but if someone wants to do it...

Just edit the frame blending clip like this: run RIFE once or twice before frame blending and voilà!

Could have a parameter "rife" set to -1 for automatic, 0 to disable, 1 or more to manually specify how many passes of doubling frames. We still need frame-blending to reach the exact desired framerate.

[kedautinh12]

Originally Posted by Selur

fingers crossed this will change soon, really like the idea of FrameRateConverter using RIFE properly

Dogway add RIFE to FrameRateConverter now
https://github.com/Dogway/Avisynth-S...verterMIX.avsi

[MysteryX]

How is RIFE working out?

[Dogway]

I did some tests and found that DCT=1, DCTRe=4 and CalcDiff=true (so 'Slowest' preset with DCTRe=4) made improvements for blending and some distortions.
Only tested on one shot but compared to no-RIFE is simply at another level. RIFEAnime stays at 'Slow' preset. Maybe you can check if implementation is correct.

[johnmeyer]

DCT=1 sometimes (not always) makes improvements in motion estimation artifacts, but at a 5x speed penalty! It is definitely worth testing on each video before proceeding.

[Dogway]

I think RIFE is also very slow so maybe it can be thought as a 'Placebo' preset, despite not being placebo at all.
I will try to run it through some popular clips like the one with the fence or the famous one @zorr used for zopti.

[takla]

Script error: the named argument "str" to StripeMask had the wrong type
FrameRateConverter.avsi, line 219

And
with Dogways FrameRateConverterMIX.avsi I get

Evaluate: operands of "%" must be integers
ExTools.avsi, line 7509