Selur's Little Message Board

Hi

I'm having an issue with the current Hybrid version (2024.05.05.1) but first started experiencing it with the previous version (2024.04.06.1) where encoding with RIFE (using my NVIDIA card) is causing encoding to fail part way through.

The debug output from one clip is here:
https://pastebin.com/ej4rrK2L

The point where the encoding suddenly stops is here in the log (lines 1762-1769):

This seems to happen across all different input videos - it definitely seems to be triggered solely by using RIFE. This seems to occur regardless of the RIFE model chosen (I've tried the 4.14 full, 4.15 lite and 4.16 lite models. The original clip encodes just fine if RIFE is switched off. This error occurs regardless of output codec chosen (have tried with x264, x265, NVEnc AV1). Other RIFE settings are default with a factor of 2 (i.e. doubling FPS).

The issue only seems to appear when using my NVIDIA RTX 4060 (laptop). If I force RIFE to use the internal AMD 780M GPU (otherwise using the same settings), the issue doesn't occur.

The failure point is not consistent, but usually tends to happen after 40-60 seconds of video have been encoded.

The input clip is here (but have tried with multiple clips and experienced the same issue):
https://1fichier.com/?oi4jgshyqwvfdxefmwbj

I have updated the drivers, that has not made a difference. I was not always experiencing this issue in the previous version but something seems to have brought it on. Curious if anyone else has experienced anything similar or has any insight.

Does the Vapoursynth preview work?
Does it workt with <= 4.6 models?

(08.05.2024, 14:03)Selur Wrote: [ -> ]

Code:

y4m [error]: bad frame header length

Does the Vapoursynth preview work?
Does it workt with <= 4.6 models?

Thanks for the quick response Selur.

The Vapoursynth preview window works, and I let it play through two minutes of preview (more than it was able to encode for) and there were no issues.

Just tested with rife-v4.5 (ensemble=False) and it failed again after encoding 50 seconds of the input clip.

send you a link to my current dev version, please try whether that makes a difference

Thanks for that.

Unfortunately, the issue still seems to occur. The log from the dev version is here:

https://pastebin.com/2M5xnAk7

I just encoded the clip without a problem.
Seems strange, that is the first 2000 frames get processed without a problem and then Vapoursynth crashes.
Is the system/gpu overclocked ? Are the temperature on your system okay while encoding?
Any virus scanner running? (try setting up exceptions for your Hybrid, temp and output folder)

Cu Selur

(08.05.2024, 15:06)Selur Wrote: [ -> ]I just encoded the clip without a problem.
Seems strange, that is the first 2000 frames get processed without a problem and then Vapoursynth crashes.
Is the system/gpu overclocked ? Are the temperature on your system okay while encoding?
Any virus scanner running? (try setting up exceptions for your Hybrid, temp and output folder)

Cu Selur

Yep, problem doesn't seem to be with the input - this happens with any video clip where I use RIFE with that card.

The problem only started occurring around 3 days ago - before that I was able to use RIFE on that card without issues. The failure point is not always the same, but it's usually close (usually within a ~30 second window). Could be a hardware issue on my end - I will keep investigating.

No overclocking. Temps seem okay (GPU getting to 55 degrees when crashing). No virus scanner.

What drivers are you using? (I'm using the studio drivers, if you are using the gaming drivers try switching to the studio drivers)

(08.05.2024, 15:37)Selur Wrote: [ -> ]What drivers are you using? (I'm using the studio drivers, if you are using the gaming drivers try switching to the studio drivers)

Just went through uninstalling drivers, then used Display Driver Uninstaller to make sure they were gone, reinstalled the studio drivers, and the problem is still occurring. It definitely seems to be a weird hardware bug on my end but what's causing it is a mystery.

Are you using the Gaming or Studio drivers?