Encoder of interlaced on Turing (RTX) like Cinegy did

[ValeZAA]

Is it possible? Like in here: https://forums.developer.nvidia.com/t/cinegy-unlocks-nvidia-h-264-interlace-encoding-on-nvidia-turing-ampere-and-ada-gpus/317601

Also can you somehow help with interlaced long references in D3D11 decoder in mpv for interlaced multiple frames of reference for intel adaptive and adaptive compensated deiterlace engine, I would understand if you say no, reference linux driver implementation was recently fixed on linux by Inte mpv-player/mpv#15197 (comment), but all the issues on windows remain, see mpv-player/mpv#15197

[averne]

The post you linked is unclear but it sounds like they are using CUDA to accelerate the encoding, contrary to NVENC which uses dedicated ASIC cores.
At the moment I have not researched NVENC in depth so I'm unable to provide a definitive answer as to whether the removal of interlaced encoding is purely a software limitation, or driven by a hardware revision.

As for the second question it is pretty off-topic with regards to my work, since desktop Nvidia cards do not include a dedicated video post-processor engine. As far as I know, motion adaptive deinterlacing there is performed in CUDA.
Tegra chips do include a hardware engine capable of doing this (VIC), but the advanced (motion compensated) modes work with field-based data rather than frame-based like FFmpeg outputs, so it cannot be used without major hacks.

[ValeZAA]

but the advanced (motion compensated) modes work with field-based data rather than frame-based like FFmpeg outputs

AFAIK, FFmpeg has no issues with field nvidia's adaptive deinterlacer (moreover, ffmpeg and Nvidia support uploading data to CUDA and deinterlacing fields), here the problem was that nvidia broke adaptive deint in the driver recently, neither does ffmpeg have issues with Intel deinterlacer on windows or linux, on linux it just uses Intel driver that was recently fixed by Intel, it just works.

The question is about Intel and mpv though on Windows, as that uses DXVA and that is broken, as you can read in that issue, as it needs multiple reference fields, which no one knows how to implement in WinAPI, besides apparently PowerDVD.

Intel deinterlacer is superior to Nvidia, and really only QTGMC is better, but it is not real time.

[averne]

I'm not sure why you contacted me about an issue on Intel/Windows, considering I'm mostly focusing on Nvidia/Linux.

In any case, the DXVA spec is not very clear on this, but seems to implies only 1 future and 1 past frames are required (see https://learn.microsoft.com/en-us/windows/win32/medfound/dxva-video-processing#input-sample-order).
This matches what the Tegra hardware video processor thing I mentionned above expects for motion adaptive algorithms (ie. modes 3 and 4 in the picture below).

[ValeZAA]

More complex than that, Nvidia may be also affected:

Adaptive and Motion Compensation
These are the really interesting ones. I don't think you can really make an explicit choice between them, but to get one of those, you need to do the same like for Bob, but additionally, you need to provide the number of future and past reference frames that is indicated by the processor (see screenshots). Once you don't provide those frames, it automatically falls back to Bob

Bug is here somewhere https://github.com/mpv-player/mpv/blob/a2106396bc6cb3a4768158fdfffcbd2e336c261c/video/filter/vf_d3d11vpp.c#L274

[averne]

The rate conversion thing is specified when creating the video processor instance: https://learn.microsoft.com/en-us/windows/win32/api/d3d11/nf-d3d11-id3d11videodevice-createvideoprocessor. The fallback to Bob might just be a failsafe, in case the past/future frames required to calculate motion maps are not present.
And by the way, the number of past/future frames you need to supply is indicated by the driver when querying rate caps:
https://learn.microsoft.com/en-us/windows/win32/api/d3d11/ns-d3d11-d3d11_video_processor_rate_conversion_caps#members

[ValeZAA]

Okay, Intel issues and windows, I will just use PowerDVD/kodi and switch display to 50 fps. It crashes all the time though. I have some issues for nvdec directly though for your opinion.