28.09.2021, 01:04
(27.09.2021, 20:41)Selur Wrote: ... (as developer I would use Vapoursynth since it's Python with additional libraries ...)Ah! Thank you. I've never used AviSynth* but know and use Vapoursynth.
I'm developing a purely 'mechanical' approach to transcoding -- apparently, I'm a pioneer -- as opposed to 'cosmetics' like yadif. For example, for 30fps[24pps]: Detelecine to 24fps[24pps] + mv interpolation to 120fps[120pps], as opposed to 2x30fps[24pps] + yadif + bob to 120fps[120pps]. I'm having great success making incredible looking 120fps HEVC targets that are 1/8 the size of 24fps AVC sources. Because SVP is skewed to speed over quality, and because InterFrame (without your overrides) doesn't help and has vague parameters, I'm trying to use Super(), Analyse(), and SmoothFps() directly. Currently, I'm working on improving my understanding of the attributes in jsonSuper, jsonAnalyse, and jsonSmoothFps.
Here's an example of the sort of stuff I've posted to Doom9, Vapoursynth: https://forum.doom9.org/showthread.php?p...ost1953251
I tried to reproduce it here, but not even code tags preserve plain text.
Aside: Do you know of a way to force this board to use plain monospaced text? This so-called "rich text" makes it impossible to show what I want to show and it drives me crazy.
Quote:... FrameRateConverter (https://forum.doom9.org/showthread.php?t=174793) might be interessting.Apparently, no one uses the motion vectors stored in the source frames. Do you know why?
Atm. it's still based on MVTools, but in the next coming versions it will also add support for RIFE for interpolation, which should help a lot.
(The thread itself is interresting to see what folks identify as problems during interpolation etc.)