MFDIN TRT Crash

[DeltaDesignRus]

Hello,
When using the Vapoursynth deinterlacer MFDIN with the TRT=True option, Hybrid crashes already at the vspipe stage without outputting a single frame, and the next line in the log shows the encoder error:

x264 [error]: could not open input file `-`

If you disable TRT mode in the Hybrid GUI (TRT=False) or choose any other deinterlacer (e.g., QTGMC), everything works normally. Regardless of whether TRT is enabled or not, the preview always functions correctly but operates very slowly, at approximately 4–5 FPS.
Could the issue be related to launching Torch-TensorRT within MFDIN? Is it possible that the required versions of TensorRT or torch-tensorrt are missing, or that vspipe crashes due to internal plugin errors?

In the archive, I enclose a video clip demonstrating the issue, along with HybridDebugOutput.txt and Report.txt
Archive

I am using an RTX 5080 GPU with driver version 576.28
Hybrid_dev_2025.05.03-203037

[Selur]

Normally, if the preview works, so should the encoding.
Debug output only shows that there is some issue with the script.
(so I'm surprised that the preview works)
Might be that MFBIN outputs some stuff to stdout which it should not.
=> will look into it.

[Selur]

Does adding:

import logging
import sys
logging.StreamHandler(sys.stderr)

in a custom section, fix the problem?

[DeltaDesignRus]

No
   
   

[Selur]

I can reproduce the problem.
Problem seems to be that:

[05/04/2025-20:50:55] [TRT] [W] Functionality provided through tensorrt.plugin module is experimental.

is output to stdout instead of stderr.

=> see https://github.com/vapoursynth/vapoursynth/issues/1120

[Selur]

Replacing the VSPIPE.exe with the one from:
https://github.com/vapoursynth/vapoursyn...2791015549

Fixes the problem.

Cu Selur

[DeltaDesignRus]

I really appreciate it, your fix solved my issue.