![]() |
|
[BUG] QTGMC Deinterlace with MFDIN = crash - Printable Version +- Selur's Little Message Board (https://forum.selur.net) +-- Forum: Hybrid - Support (https://forum.selur.net/forum-1.html) +--- Forum: Problems & Questions (https://forum.selur.net/forum-3.html) +--- Thread: [BUG] QTGMC Deinterlace with MFDIN = crash (/thread-4439.html) Pages:
1
2
|
QTGMC Deinterlace with MFDIN = crash - tailland - 06.07.2026 2026.07.05 Reproduce: Load MP4 Scenario1: - VS/Deint/qtgmc - Preset Custom with EdiExt MFDIN(old) - Queue and Start: CRASH [attachment=3683] Scenario2: - VS/Deint/qtgmc - Preset Custom with EdiExt MFDIN(old)-TRT - Queue and Start: CRASH [attachment=3684] additional phenomenon: vspipe keeps vram full and keeping gpu load high despite queue having crashed RE: QTGMC Deinterlace with MFDIN = crash - Selur - 07.07.2026 Does the Vapoursynth Preview work? I guess you are running out of vram. With 16GB vram on hd content I get: Requested amount of GPU memory (1592786944 bytes) could not be allocated. There may not be enough free memory for allocation to succeed.
UNSUPPORTED_STATE: Skipping tactic 49 due to insufficient memory on requested size of 1592786944 detected for tactic 0x1b099f7ac29a2a6a.Cu Selur RE: QTGMC Deinterlace with MFDIN = crash - tailland - 07.07.2026 no, preview doesn't work either. (it's a bit strange since i used it successfully in the past.) RE: QTGMC Deinterlace with MFDIN = crash - Selur - 07.07.2026 Are you sure you used it on HD content? (works fine on SD content here) RE: QTGMC Deinterlace with MFDIN = crash - tailland - 07.07.2026 hm iirc i used it on 576p and 720p, not above RE: QTGMC Deinterlace with MFDIN = crash - Selur - 07.07.2026 in your sample you used it on 1440x1080, so that is probably the problem. I suspect that it will still work fine for you on SD content. Cu Selur RE: QTGMC Deinterlace with MFDIN = crash - tailland - 10.07.2026 576p source file: https://my.hidrive.com/lnk/d0Yzo4Q0O resolution doesn't matter :ß this used to be functional in the past. now the job crashes, but the gpu starts working at 90%+ RE: QTGMC Deinterlace with MFDIN = crash - Selur - 11.07.2026 Invalid magic number for yuv4mpeg.Sidenote: Why are you overwriting the scanorder to BFF ? Looking at the clip it seems to be TFF encoded progressively. Seems like the crash happens due to the output of: [07/11/2026-08:02:04] [TRT] [W] Functionality provided through tensorrt.plugin module is experimental.Hybrid does try to fix this by using: # Force logging to std:err
logging.StreamHandler(sys.stderr)![]() seems like the issue was fixed once, see: https://forum.selur.net/thread-4089.html and https://github.com/vapoursynth/vapoursynth/issues/1120#issuecomment-2791015549, but seemingly was removed in newer Vapoursynth versions. Seems like one would need to use named pipes instead of normal pipe to workaround this. ![]() => this will take a while to look into, since I'm ill atm. this won't happen this weekend. Cu Selur RE: QTGMC Deinterlace with MFDIN = crash - Selur - 11.07.2026 Had a quick go at it: https://www.mediafire.com/file/1xjresbid6y1oh4/Hybrid.7z/file (Hybrid.exe only) Try whether this works or not. (use latest dev, replace Hybrid.exe with the one above) In theory, this should always use named pipes if vspipe is used and thus hopefully circumvent the problem. (going to sleep again now, but I hope this works) Cu Selur RE: QTGMC Deinterlace with MFDIN = crash - Selur - 11.07.2026 Uploaded a new dev, but the usage of named pipes does not work with NVEncC/QSVEncC/VCEEnC/SVT-AV1/SVT-Hevc, so I disabled it for now and thus these encoders will still crash when using MFDIN. Cu Selur |