TensorRT-RTX is a specialization of TensorRT for NVIDIA RTX GPUs, which compiles engines faster with comparable performance with TensorRT.
Atm. only 32bit support works. (fp16 will probably come in the future)
Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Selur, I know I had already finished things on my end, but I'm having a problem, no matter which filter I use, I'm getting this error before the render finishes, check attacked file.
Side note: you might want to clear your temp-folder (I would also recommend moving it to a dedicated folder outside the main Windows folders, and add an exception for it to your antivirus solution.)
Since it's the helper that crashes, it's likely a problem with the Vapoursynth handling, but since Vapoursynth is working the first 19590 frames of the clip without problems it might be that:
a. the input has an issue (corrupt headers or similar) => try scrolling through the Vapourynth Preview starting Frame 19590
b. you are running out of RAM/space
c. some error occurs through overclocking or heat problems of gpu/cpu/memory
d. something is interfering with the filtering or file access (virusscanners, tunign tools or similar are usually the cause for this)
Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
I've always used it with Windows Defender turned off. As for overclocking, I actually had an undervolt on the CPU, OC on the RAM, and OC on the GPU — I disabled everything, cleared the temp folder, and the same issue keeps happening. Regarding the frames, I tried limiting it to just 1 out of 7 chapters, which is about 5 minutes of video and doesn't even reach frame 19590. I also changed the input to a different video — same result. Anyway, I have no idea what could be causing this, it's never happened before. I also don't think it's a RAM issue — I have 32GB of 3600MHz RAM. I'll leave my specs here in case it helps:
Edit: It seems to be an issue with the MC Temporal Denoise filter. I removed each filter one by one with various input sources, and it's the only one that causes a crash. I uninstalled the Hybrid dev version and installed the standard Hybrid, but the same thing happened.
Undervolting can cause instabilities similar to overclocking.
So, I would recommend trying whether it works if nothing is over- or underclocked.
Quote:Edit: It seems to be an issue with the MC Temporal Denoise filter. I removed each filter one by one with various input sources, and it's the only one that causes a crash. I uninstalled the Hybrid dev version and installed the standard Hybrid, but the same thing happened.
Strange MCTemporalDenoise works fine here. (Ryzen 9 7950X, 64GB RAM, Geforce RTX 4080)
Maybe try using NVIDIA Studio drivers (reboot after install).
I always use those, since the gaming drivers frequently caused problems.