Inverse telecine is different than de-interlace!! 24fps sources that have been previously telecine’d to 59.94 Interlaced) need to have ITVC applied, to recover the original discrete progressive frames, before other processing such as sharpening and upscaling. For those of us working with archival footage that the repositories have previously telecine’d, or for the Panasonic DV cameras that used to record 23.976p in a 59.94 NTSC “wrapper”, it’s a critical function, and other software to do this is cumbersome and/or very limited in its abililties.
Bonus: add in some custom settings that exceed other available software, including recovering material that was telecine’d from 16FPS or 18FPS film (such as 8mm, super 8, and silent-era 16mm and 35mm film).
With the CLI, it is still possible to perform telecine using FFMPEG’s built-in filter.
The GUI should also be able to select the telecine filter in the same way.
A sample of telecine using FFMPEG’s built-in filter in the CLI is described below.
Thanks for your reply. For those of us who are “ordinary” users, this is complete Greek. I haven’t regularly used command line tools since MS-DOS 4.0 and Novel Netware. I certainly am not up to speed on the syntax for chaining command-line ffmpeg filters alongside Video AI.
If I understand you correctly, inverse telecine is not currently available in the GUI but can be invoked (at least to some degree) with a CLI, via ffmpeg.
This definitely illustrates the need to put this capability in the Video AI GUI, to make it accessible to video professionals who are not command line ninjas (most of us). And again, the best-case scenario would be to be able to select and/or detect less-common pulldown patterns, particularly from footage that originated at frame rates other than 24P.
Yes, the reason I gave the CLI sample was also to prove that what is feasible in the CLI can be achieved relatively easily in the GUI.
TVAI 3.x relies on FFMPEG.
Functions that do not exist in FFMPEG need to be created from scratch, which increases development costs, but functions that do exist can be added simply by adding commands to the GUI side that are passed to FFMPEG.